- Level
- confirmed
- Worst impact
- Degraded
- Components
- RCS Messaging
- Down Index
- 14of 100
What to do
Check whether you use Twilio RCS Messaging. 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 11m it lasted.
Anything that failed between 2026-08-24 18:37 UTC and 2026-08-24 18:48 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
We are investigating an issue with outbound messaging for RCS and WhatsApp. Users may experience elevated HTTP 500 status codes and errors sending outbound messages. We will provide another update in 1 hour or as soon as more information becomes available.
provider
- resolved
We have investigated and resolved an issue with Messaging. From 11:10AM PDT to 11:15AM PDT on Monday, 8/24/26, customers may have experienced errors sending outbound WhatsApp and RCS messages. The issue has been resolved and all impacted services are operating normally.
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-6e556d4544
Is Twilio still down?
No, this incident was resolved 2026-08-24 18:48 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
11m, from 2026-08-24 18:37 UTC to 2026-08-24 18:48 UTC, by the times Twilio posted.
What was affected?
Twilio named RCS Messaging.
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.