LlamaIndex: Platform Outage
Google Cloud outage, Jun 12, 2025 · 101 vendors, 107 incidents
LlamaIndex’s incident started in the same window without naming Google Cloud (timing only, not evidence of a link). (timing only, posted +17 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["LlamaIndex (this incident)<br/>posted +17 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.
Affected components: LlamaCloud - LlamaCloud UILlamaParse UILlamaCloud - LlamaCloud Public APILlamaParse APILlamaCloud (EU) - LlamaParseLlamaCloud (EU) - LlamaCloud (EU) UILlamaParse UILlamaCloud - LlamaParseLlamaCloud (EU) - LlamaCloud APILlamaParse APILlamaCloud - LlamaCloud DocsLlamaParse Docs
Timeline of updates
- investigating
All services are currently unavailable due to an upstream auth provider outage. We are actively working to resolve the issues.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
- Jun 12, 2025Major incident: Platform Outage
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. That proves this record existed by then and has not been changed since, by anyone, Rewindex included.
How the archive is checked, and what it cannot prove.
First version captured 17:03 UTC
In the 2026-10-19 checkpoint, timestamped by FreeTSA and DigiCert on Oct 20, 00:41 UTC. Record hash
9824aae4ba38d3dd…
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).