CompaniesLightning AIIncidents
Lightning AI: Major Outage: All Workloads Impacted
Google Cloud outage, Jun 12, 2025 · 101 vendors, 107 incidents
Lightning AI’s incident blames Google Cloud as the cause. (hop 1, posted +32 min vs the first vendor naming Google Cloud)
“…ved. We are currently experiencing a major outage due to an outage on our cloud provider (GCP). All existing workloads are currently impacted and may be unresponsive or degraded. Additionally, new wor…”
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["Lightning AI (this incident)<br/>posted +32 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
- identified
We are currently experiencing a major outage due to an outage on our cloud provider (GCP). All existing workloads are currently impacted and may be unresponsive or degraded. Additionally, new workloads cannot be created at this time. Our team is actively monitoring the situation and working with GCP to resolve the issue as quickly as possible. We will continue to provide updates as we learn more.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
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 stspg.io (opens in new tab).
Lightning AI profileRecent Lightning AI incidentsMarkdownJSON