- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 21of 100
What to do
Check whether your product depends on Twilio. 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 4h 13m it lasted.
Anything that failed between 2026-07-30 14:41 UTC and 2026-07-30 18:54 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 5
- investigating
We are currently investigating an issue with stuck events regarding Bulk Export API. We expect to provide another update in 1 hour or as soon as more information becomes available
provider
- investigating
We are contiuning to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are contiuning to investigate this issue.
provider
- resolved
We have fully investigated the Bulk Export API issue triggered by our automated alert, and it was determined that there is no noticeable customer impact. All systems are operational.
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-a08c01d643
Is Twilio still down?
No, this incident was resolved 2026-07-30 18:54 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
4h 13m, from 2026-07-30 14:41 UTC to 2026-07-30 18:54 UTC, by the times Twilio posted.
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.