- Level
- confirmed
- Worst impact
- Degraded
- Components
- Messaging Services
- Down Index
- 21of 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 4h 8m it lasted.
Anything that failed between 2026-07-23 02:29 UTC and 2026-07-23 06:37 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 Validity Period setting within Messaging Services not being applied. 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 issue with Validity Period setting within Messaging Services, and it was determined that the impact was limited to a small set of customers. 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-80da3cb20c
Is Twilio still down?
No, this incident was resolved 2026-07-23 06:37 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
4h 8m, from 2026-07-23 02:29 UTC to 2026-07-23 06:37 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.