Resolved after 1 hour 31 minutes, on March 24, 2026.
We continue to use the failover region, and Scribe performance has returned to expected levels.
Update timeline
- identified Mar 24, 2026, 03:31 PM UTC
We have identified increased error rates with an upstream call transcription provider. This is affecting Scribe for all customers. Our team are investigating and we will update with more information shortly as we learn more.
- monitoring Mar 24, 2026, 03:33 PM UTC
The issues were isolated to one region and we have performed a failover to a secondary region, restoring Scribe for all customers. You may need to ask Scribe to rejoin your call. We'll continue to monitor the situation and are working closely with the upstream provider while they resolve the issue.
- monitoring Mar 24, 2026, 04:18 PM UTC
Our failover region is continuing to work as expected, and Scribe functionality has been restored. You may need to ask Scribe to rejoin your calls. We'll continue to monitor the situation and are working closely with the upstream provider while they resolve the issue.
- resolved Mar 24, 2026, 05:02 PM UTC
We continue to use the failover region, and Scribe performance has returned to expected levels.
Your product runs on more than incident.io
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services