- Level
- confirmed
- Worst impact
- Degraded
- Components
- Messaging Services
- Down Index
- 8of 100
What to do
Check whether you use Twilio Messaging Services. 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 0m it lasted.
Anything that failed between 2026-09-09 17:47 UTC and 2026-09-09 17:47 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 1
- resolved
Our engineers have investigated and resolved an issue with Messaging Services. From 10:28AM PDT on Tuesday, 7/21/26 to 6:00PM PDT on Friday, 9/4/26, customers may have experienced HTTP 400 responses with Twilio error code 21620 when sending messages through Messaging Services if the media URL parameter contained a comma. The issue has been resolved and all impacted services 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-1342f069c3
Is Twilio still down?
No, this incident was resolved 2026-09-09 17:47 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
0m, from 2026-09-09 17:47 UTC to 2026-09-09 17:47 UTC, by the times Twilio posted.
What was affected?
Twilio named Messaging Services.
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.