Update timeline
- identified Mar 24, 2026, 03:31 PM UTC
Status: Identified 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
Status: Monitoring 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
Status: Monitoring 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
Status: Resolved We continue to use the failover region, and Scribe performance has returned to expected levels.
Looking to track incident.io downtime and outages?
Pingoru polls incident.io's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when incident.io reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track incident.io alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required