- Level
- confirmed
- Worst impact
- Degraded
- Components
- Other
What to do
Check whether you use Twilio Other. 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 52m it lasted.
Anything that failed between 2026-09-22 19:23 UTC and 2026-09-22 20:14 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 3
- investigating
We are investigating an issue with Messaging webhooks. Users may experience delays of up to 10 minutes receiving message status webhooks. We will provide another update in 1 hour or as soon as more information becomes available.
provider
- monitoring
We have resolved the issue causing delayed Messaging webhooks for message status updates. Delivery status callbacks are processing as expected. We are continuing to monitor.
provider
- resolved
Messaging webhooks have returned to normal processing times in US1.
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-5538084f9b
Is Twilio still down?
No, this incident was resolved 2026-09-22 20:14 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
52m, from 2026-09-22 19:23 UTC to 2026-09-22 20:14 UTC, by the times Twilio posted.
What was affected?
Twilio named Other.
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.