- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 8of 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 0m it lasted.
Anything that failed between 2026-08-12 14:14 UTC and 2026-08-12 14:00 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
Twilio Flex authentication was degraded for approximately 180 minutes (3 hours) between 11:27 AM and 2:27 PM Pacific Time on 08/11/2026. During this period of time, customers may have experienced failed or interrupted single sign-on (SSO) login attempts when authenticating into Flex. The issue has now 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-5c7e7de1b2
Is Twilio still down?
No, this incident was resolved 2026-08-12 14:00 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
0m, from 2026-08-12 14:14 UTC to 2026-08-12 14:00 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.