- Level
- confirmed
- Worst impact
- Degraded
- Components
- Realtime Transcriptions, Realtime Transcriptions US1
- Down Index
- 20of 100
What to do
Check whether you use Twilio Realtime Transcriptions, Realtime Transcriptions US1. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 47m it lasted.
Anything that failed between 2026-04-21 16:53 UTC and 2026-04-21 20:39 UTC may need a replay.Subscribe to Twilio's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=twilio works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Twilio 6
- investigating
Due to a third-party provider outage, customers may be experiencing degraded live transcription services for Voice and Video. Customers may not be able to transcribe their calls at this time. We will provide another update in 1 hour or as soon as more information becomes available.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
Due to a third-party provider outage, customers may be experiencing degraded live transcription services for Voice and Video. Customers may not be able to transcribe their calls at this time. We will provide another update in 2 hours or as soon as more information becomes available.
provider
- monitoring
We have observed a recovery in live transcription services for Voice and Video. We will provide another update in 2 hours or as soon as more information becomes available.
provider
- resolved
We have observed recovery in live transcription services for Voice and Video. This issue is not resolved.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-7147f128d5
Is Twilio still down?
No, this incident was resolved 2026-04-21 20:39 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
3h 47m, from 2026-04-21 16:53 UTC to 2026-04-21 20:39 UTC, by the times Twilio posted.
What was affected?
Twilio named Realtime Transcriptions, Realtime Transcriptions US1.
What caused it?
Twilio hasn't published a root cause. If it does, it shows here.
Where does this come from?
Twilio's official status page, https://status.twilio.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.