Twilio: SMS Delivery Delays to Cingular Wireless (AT&T) in the US
Google Cloud outage, Jun 12, 2025 · 101 vendors, 107 incidents
Twilio’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted −34 min vs the first vendor naming Google Cloud)
Swipe sideways to see the whole diagram.
Mermaid source
flowchart LR
root["Google Cloud<br/>own incident not archived"]:::inferred
h1["Within an hour<br/>29 vendors, 28 blamed Google Cloud<br/>Pinecone, Northflank, imgix +26"]:::blames
root --> h1
h4["1 to 4 hours later<br/>12 vendors, 11 blamed Google Cloud<br/>Smartsheet, Daily, Confluent +9"]:::blames
root --> h4
later["Later<br/>1 vendor, 1 blamed Google Cloud<br/>Zilliz"]:::blames
root --> later
p0["Firebase<br/>own incident not archived"]:::inferred
root -.-> p0
k0["Codeium, Windsurf<br/>+13 min"]:::hop2
p0 -->|"blamed Firebase"| k0
p1["Anthropic<br/>posted +28 min, did not name Google Cloud"]:::timing
root -.-> p1
k1["GitHub, GitHub Copilot<br/>+24 min"]:::hop2
p1 -->|"blamed Anthropic"| k1
p2["Cloudflare<br/>own incident not archived"]:::inferred
root -.-> p2
k2["Doppler, Jupyter (Anaconda), Socket +4<br/>+35 min to +3 h 41 min"]:::hop2
p2 -->|"blamed Cloudflare"| k2
me["Twilio (this incident)<br/>posted −34 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
We are no longer experiencing SMS delivery delays when sending messages to Cingular Wireless (AT&T) in the US. This incident has been resolved.
From Twilio’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Impact, status and times are the vendor’s own, as last archived. View on status.twilio.com (opens in new tab).