Couchbase: Ongoing issues with GCP may impact functionality
Google Cloud outage, Jun 12, 2025 · 101 vendors, 107 incidents
Couchbase’s incident blames Google Cloud as the cause. (hop 1, posted +1 h 40 min vs the first vendor naming Google Cloud)
“…Ongoing issues with GCP may impact functionality This incident has been resolved as updated in GCP status: https://status.cloud.google.com/. Rate of errors have dropped to normal levels, we are closel…”
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["Couchbase (this incident)<br/>posted +1 h 40 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: Couchbase Capella - Couchbase Capella OperationalCouchbase Capella OperationalCouchbase Capella AnalyticsCouchbase Capella - Couchbase Capella ColumnarCouchbase Capella App ServicesCouchbase Capella - Couchbase Capella App ServicesGCP - Google Cloud Platform Google Compute EngineGoogle Cloud Platform Google Compute Engine
Timeline of updates
- investigating
We’re currently observing an elevated rate of errors originating from GCP. Existing cluster health remains stable and unaffected. However, backups and new cluster deployments on GCP may experience delays or failures.
- monitoring
Rate of errors have dropped to normal levels, we are closely monitoring the ongoing Capella operations. For latest updates from GCP: https://status.cloud.google.com/.
- resolved
This incident has been resolved as updated in GCP status: https://status.cloud.google.com/.
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).