Assembled Incident History

Increased load in API requests affected our APIs and Voice services, leading to increased latency. For voice, we temporarily diverted traffic to live agents as we investigated and resolved.

We've returned to normal levels of latency and error rates across all services.

We've returned to normal levels of latency and error rates across all services.

We are seeing improvement in latency across all services so as a result, we have turned our voice agent back on. It is not accepting calls. We are continuing to monitor for stability.

We're still seeing unexpected load on our database, causing elevated latency and error rates. The team is continuing to investigate.

Our original fix did not have the intended effect. We've merged another fix and are again monitoring results to see if latency across all services recovers.

We've identified the root cause and merged a potential fix. We are monitoring for improvement.

We have discovered that the elevated voice latency is due to increased latency from our database, which affects our web application and APIS.

We are investigating elevated latency with our voice agent so while this occurs we are re routing calls to live agents.

All APIs and the Assembled web application are fully functional.

We've identified the root cause and are working on a potential fix, monitoring the results to see if this will reduce pressure on our database and restore latency and error rates to normal baselines.

We are experiencing a slight increase in latency and timeout-related errors on our web application and APIs. We are actively investigating the issue.

Data affected during the period has been successfully retried.

A fix has been implemented and we're monitoring our asynchronous services to ensure all data during the affected period is handled succesfully.

We have identified the root cause and are deploying the fix. Services are fully functional, any services that handle incoming data to Assembled (e.g. webhooks) were temporarily blocked from handling that data.

This incident has been resolved.

A fix has been implemented and we are monitoring the results.

We are currently investigating an interruption affecting the realtime agent analysis page. Our team is actively working on a fix and expects resolution within the next 30–60 minutes. We'll post another update shortly. Thank you for your patience.