- Level
- confirmed
- Worst impact
- Degraded
- Components
- WhatsApp Messaging
- Down Index
- 15of 100
What to do
Check whether you use Twilio WhatsApp 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 25m it lasted.
Anything that failed between 2026-10-02 17:21 UTC and 2026-10-02 17:46 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 Messaging event processing for Comms API. Customers may experience delays in event updates for RCS, WhatsApp Business API, and Apple Messages for Business. We will provide another update in 15 minutes or as soon as more information becomes available.
provider
- resolved
The customer experience for impact is that Bulk Messaging API callers would receive an incorrect/improper 400 error response for Send Messages requests when supplying the address of Senders that were registered during the impact window. We have resolved this incident.
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-3289f13ecb
Is Twilio still down?
No, this incident was resolved 2026-10-02 17:46 UTC. For Twilio's live state, see https://down.guide/twilio.
How long did it last?
25m, from 2026-10-02 17:21 UTC to 2026-10-02 17:46 UTC, by the times Twilio posted.
What was affected?
Twilio named WhatsApp 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.