- Level
- confirmed
- Worst impact
- Degraded
- Regions
- us
- Down Index
- 20of 100
What to do
Check whether you use Twilio in us. 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 37m it lasted.
Anything that failed between 2026-07-09 21:30 UTC and 2026-07-09 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 an increase in 30003 and 30005 errors when sending outbound SMS to some carriers in the US. Our engineers have been alerted and are investigating. We will provide an update when we have more details.
provider
- resolved
We have fully investigated the increase in errors when sending outbound SMS 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-32d91c1ed7
Is Twilio still down?
No, this incident was resolved 2026-07-09 22:07 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
37m, from 2026-07-09 21:30 UTC to 2026-07-09 22:07 UTC, by the times Twilio posted.
What was affected?
Twilio named in us.
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.