RudderStack: Cloudflare and GCP outage causing delayed deliveries to affected cloud destinations
Google Cloud outage, Jun 12, 2025 · 101 vendors, 107 incidents
RudderStack’s incident is a second hop: it blames Cloudflare, which was affected by Google Cloud. (hop 2, posted +2 h 32 min vs the first vendor naming Google Cloud)
“…Cloudflare and GCP outage causing delayed deliveries to affected cloud destinations This incident has been resolved. Cloudflare and GCP have reported recovery and we are actively monitoring to ensure…”
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["RudderStack (this incident)<br/>posted +2 h 32 min"]:::me
p2 -->|"blamed Cloudflare"| 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: Data Processing Pipeline - Data Processing Pipeline (US)Data Processing Pipeline (US)Data Processing Pipeline - Data Processing Pipeline (EU)Data Processing Pipeline (EU)
Timeline of updates
- monitoring
Cloudflare and GCP have reported recovery and we are actively monitoring to ensure all events are retried and delivered to affected destinations. No data loss has been observed
- resolved
This incident has been resolved.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).