Orb: Elevated errors across API endpoints
Google Cloud outage, Jun 12, 2025 · 101 vendors, 107 incidents
Orb’s incident blames Google Cloud as the cause. (hop 1, posted +1 h 28 min vs the first vendor naming Google Cloud)
“…:13. This is due to an influx of traffic, believed to be downstream effects from a global GCP outage. We executed immediate mitigations, have observed recovery, and will continue to monitor errors. Th…”
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["Orb (this incident)<br/>posted +1 h 28 min"]:::me
h4 --- 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: AnalyticsAPI - AnalyticsAPI - ReadsReadsAPI - WritesWrites
Timeline of updates
- monitoring
API read and analytic endpoints experienced high rates of API failures between 18:52 - 19:13. This is due to an influx of traffic, believed to be downstream effects from a global GCP outage. We executed immediate mitigations, have observed recovery, and will continue to monitor errors.
- monitoring
We are continuing to monitor for any further issues.
- resolved
This incident has been resolved.
Changes Rewindex caught on this incident
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).