Twilio: Delivery Delays and Failures from WhatsApp, Verify, Conversations, and Messenger Platform
Meta outage, Jun 12, 2026 · 14 vendors, 14 incidents
Twilio’s incident names Meta (location or integration). (hop 1, posted +0 min vs the first vendor naming Meta)
“…Delivery Delays and Failures from WhatsApp, Verify, Conversations, and Messenger Platform The delivery delays and failures when sending messages from WhatsApp, Verify, Conversations, and Messenger pla…”
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Meta<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>8 vendors, 7 blamed Meta<br/>Twilio, Sprout Social, Vonage, Hootsuite +4"]:::blames
root --> h1
h4["1 to 4 hours later<br/>4 vendors, 3 blamed Meta<br/>BigCommerce, Braze, Iterable, Plivo"]:::blames
root --> h4
me["Twilio (this incident)<br/>posted +0 min"]:::me
h1 --- meFull event: timeline, evidence and all vendors →
Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.
Timeline of updates
- resolved
The delivery delays and failures when sending messages from WhatsApp, Verify, Conversations, and Messenger platform have been resolved and is operating normally at this time.
From Twilio’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).