- Level
- confirmed
- Worst impact
- Degraded
- Components
- Verify
What to do
Check whether you use Twilio Verify. 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 1h 15m it lasted.
Anything that failed between 2026-09-30 15:16 UTC and 2026-09-30 16:31 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 experiencing delivery failures from Verify to China. Our engineers are working to resolve the issue. We expect to provide another update in 1 hour or as soon as more information becomes available.
provider
- investigating
We continue to experience delivery failures from Verify to China. Our engineers are working to resolve the issue. We expect to provide another update in 2 hours or as soon as more information becomes available.
provider
- resolved
We have completed our investigation and determined that this event did not result in any customer impact. All systems are operating normally.
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-9918c17eb1
Is Twilio still down?
No, this incident was resolved 2026-09-30 16:31 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
1h 15m, from 2026-09-30 15:16 UTC to 2026-09-30 16:31 UTC, by the times Twilio posted.
What was affected?
Twilio named Verify.
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.