Twilio: Conversations Classic Failure
GitHub outage, Jul 24, 2026 · 9 vendors, 12 incidents
Twilio’s incident started in the same window without naming GitHub (timing only, not evidence of a link). (timing only, posted +31 min vs GitHub’s own post)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["GitHub<br/>posted 16:17 UTC"]:::root
h1["Within an hour<br/>2 vendors, 2 blamed GitHub<br/>Bolt.new, CircleCI"]:::blames
root --> h1
h4["1 to 4 hours later<br/>1 vendor, 1 blamed GitHub<br/>Bolt.new"]:::blames
root --> h4
me["Twilio (this incident)<br/>posted +31 min"]:::me
root -.->|"same window"| 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 issue with being unable to create configurations has been resolved and Twilio Conversations Classic 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).