- Level
- confirmed
- Worst impact
- Degraded
- Components
- Conversations
- Down Index
- 27of 100
Summary
Twilio says Notification Delivery Logs in the Console were unavailable and that new records were not appearing for affected services. Twilio reports the issue is mitigated, logs are returning to normal, and it is monitoring system performance.
Written by anthropic/claude-haiku-5.5 from Twilio's own updates.
What to do
Check whether you use Twilio Conversations. 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 7m it lasted.
Anything that failed between 2026-11-06 06:07 UTC and 2026-11-06 06:14 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
- monitoring
Our engineers have mitigated the issue and are monitoring system performance. Notification delivery logs in Console are returning to normal, and new records are appearing again for affected services. We will provide another update in 2 hours or as soon as more information becomes available.
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-7042a11ddb
Is Twilio still down?
No, this incident was resolved 2026-11-06 06:14 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
7m, from 2026-11-06 06:07 UTC to 2026-11-06 06:14 UTC, by the times Twilio posted.
What was affected?
Twilio named Conversations.
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.