- Level
- confirmed
- Worst impact
- Degraded
- Components
- Conference US1
- Down Index
- 17of 100
What to do
Check whether you use Twilio Conference 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 47m it lasted.
Anything that failed between 2026-07-10 21:24 UTC and 2026-07-10 22:11 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 2
- investigating
Our monitoring systems have detected a potential issue with dual channel conference recordings. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
provider
- resolved
Twilio dual channel conference recording was degraded for 3 minutes between 9:59 AM and 10:02 AM Pacific Time on 07/10/2026. Dual channel conference recordings received during this time may be stuck 'in progress'. The issue has now been 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-1162884a28
Is Twilio still down?
No, this incident was resolved 2026-07-10 22:11 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
47m, from 2026-07-10 21:24 UTC to 2026-07-10 22:11 UTC, by the times Twilio posted.
What was affected?
Twilio named Conference 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.