Scribe is now fully functioning with the error rates for transcription and joining calls back to normal. For ongoing calls where Scribe failed to join initially, Scribe can be added manually.

Please see: https://incident.io/changelog/click-to-add-scribe

We have migrated Scribe to another AWS region, and are now seeing it join calls successfully in Zoom and Google Meet. For ongoing calls where Scribe failed to join initially, Scribe can be added manually.

Please see: https://incident.io/changelog/click-to-add-scribe

Due to the ongoing AWS service outage, we're continuing to see Scribe fail to join new incident calls. AWS has identified a root cause and is working on mitigations.We'll continue to monitor closely and are in close contact with our upstream transcription provider.

We're continuing to see Scribe fail to join new incident calls. We're currently working with our upstream transcription provider to mitigate the impact by migrating to a different AWS region, and will continue to provide regular updates here.

We're continuing to see Scribe fail to join new incident calls. We'll continue to monitor closely, are in close contact with our upstream transcription provider and will continue to provide regular updates here.

We're continuing to see Scribe fail to join new incident calls. Existing Scribe calls appear to be unaffected.

We'll continue to monitor closely and are in close contact with our upstream transcription provider.

Our upstream transcription provider has notified us that they're observing instability with AWS while AWS recover from the incident earlier today. Scribe may fail to join some calls and we're seeing increased error rates.

We'll continue to monitor closely. Next update at 13:45 UTC

Scribe is now fully functioning with the error rates for transcription and joining calls back to normal. For ongoing calls where Scribe failed to join initially, Scribe can be added manually. Please see:

https://incident.io/changelog/click-to-add-scribe

Our transcription provider is reporting platform recovery and we're seeing Scribe joining calls again.

We anticipate full recovery imminently, and will continue to monitor throughout.

We're still seeing issues transcribing via Scribe and are continuing to monitor the upstream AWS outage and explore mitigation options. Apologies again for the disruption.

We've identified the source of the issues with Scribe joining incident channels as being related to an issue in AWS, currently affecting several upstream providers.

Our team are continuing to explore interim mitigation options. For now, Scribe remains unavailable.

More details on the AWS outage here: https://health.aws.amazon.com/health/status

We'll provide updates every 30m going forward.