We will be undergoing scheduled maintenance in order to upgrade our database. Assembled will remain available, but you may briefly be unable to save changes for up to ~5 minutes during this window.. Posted on
May 18, 2026 - 17:37 UTC
Resolved -
This incident has been resolved. A database operation degraded performance, which caused pages across the product to become unresponsive. We’re reviewing our database operation safeguards and monitoring to reduce the likelihood of similar issues in the future.
[6:53 AM PT ] Our voice agent is still unavailable as the system recovers, but we are successfully able to transfer callers to a live agent upon error.
[7:08 AM PT] The voice agent is healthy and available.
May 15, 13:53 UTC
Identified -
The issue has been identified and a fix is being implemented.
May 15, 13:48 UTC
Investigating -
We are currently investigating this issue.
Our voice agent is unavailable and we are currently unable to transfer calls successfully to a live agent upon error.
May 15, 13:44 UTC
Resolved -
This incident has been resolved. A database operation degraded performance, which caused pages across the product to become unresponsive. We’re reviewing our database operation safeguards and monitoring to reduce the likelihood of similar issues in the future.
May 12, 18:23 UTC
Monitoring -
A fix has been implemented and we are monitoring the results.
May 12, 18:07 UTC
Investigating -
We are currently investigating this issue.
May 12, 18:03 UTC
Resolved -
Between 6:30pm ET on May 6th and 7am ET on May 7th, some customers saw missing or zero values in reporting surfaces (including support volume and queue/exclusion views) for data values that appeared after 6:30pm ET on 5/6/2026 due to delayed replication in one of our data-processing tasks.
Data ingestion itself continued normally and no conversation data was lost, the issue was isolated to metric freshness/display.
We restored the task, backfilled dependent metrics, and service is now operating normally, with additional monitoring improvements underway to prevent recurrence.
May 7, 11:15 UTC