- Level
- confirmed
- Worst impact
- Degraded
- Components
- SMS
- Down Index
- 23of 100
What to do
Check whether you use Twilio SMS. 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 1d 15h it lasted.
Anything that failed between 2026-11-03 02:14 UTC and 2026-11-04 18:09 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 9
- investigating
We are investigating delays in messages presented, while no messages are lost. We expect to provide another update in 1 hour or as soon as more information becomes available
provider
- identified
Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 1 hour or as soon as more information becomes available
provider
- identified
Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 2 hour or as soon as more information becomes available
provider
- identified
Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 4 hour or as soon as more information becomes available.
provider
- identified
Our engineering team has identified and mitigated the issue causing delays in messages which were presented, while no messages were lost we continue to investigate the root cause. We expect to provide another update in 8 hours or as soon as more information becomes available.
provider
- identified
The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 8 hours or as soon as new information is available.
provider
- identified
The message delays were caused by an issue with a single host and affected only a portion of SMS traffic for approximately one hour. Service was restored and has been stable since with no data loss. We have applied a preventive measure to avoid a recurrence and are validating a permanent fix. We will share our next update in 16 hours or as soon as new information is available.
provider
- monitoring
Messaging is operating normally. We will continue to monitor for system stability. We'll provide another update in 2 hours or as soon as more information becomes available.
provider
- resolved
We are no longer experiencing the issue causing delays in messages. This incident 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-394efd75a3
Is Twilio still down?
No, this incident was resolved 2026-11-04 18:09 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
1d 15h, from 2026-11-03 02:14 UTC to 2026-11-04 18:09 UTC, by the times Twilio posted.
What was affected?
Twilio named SMS.
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.