- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 14of 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 12m it lasted.
Anything that failed between 2026-09-08 17:27 UTC and 2026-09-08 17:39 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
- monitoring
Our engineers are currently investigating the customer impact of a retroactive issue with Messaging. We will follow up and provide customer impact details within 2 hours.
provider
- resolved
Twilio Messaging Services was degraded for 46 days between July 21 2026 3:28 PM and Sept 4 2026 6:00 PM Pacific Time . During this period of time, customers that sent messages with media url that contained a comma and added the messaging service sid parameter in their messages will have their messages messages incorrectly rejected with http 400 and Twilio error code 21620 .
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-b7fccb2391
Is Twilio still down?
No, this incident was resolved 2026-09-08 17:39 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
12m, from 2026-09-08 17:27 UTC to 2026-09-08 17:39 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.