- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 13of 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 10m it lasted.
Anything that failed between 2026-08-17 21:57 UTC and 2026-08-17 22:07 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 Programmable messaging API returned 503s to customers. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
provider
- resolved
Between 13:25 PST and 13:27 PST, customers may have received an elevated rate of HTTP 503s when sending messages via the Programmable Messaging API. The issue has 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-23ae20e65e
Is Twilio still down?
No, this incident was resolved 2026-08-17 22:07 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
10m, from 2026-08-17 21:57 UTC to 2026-08-17 22:07 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.