# Zilliz: GCP outage impacting clusters in gcp-us-east4, gcp-us-central1, gcp-us-asia-southeast1 regions

- Impact (vendor’s label): major
- Status: resolved
- Started: 2025-06-13 06:11 UTC · Resolved: 2025-06-12 20:00 UTC · Duration: -611 min
- Updates: 1
- [Vendor status page: https://stspg.io/bsrpvqht33zc](https://stspg.io/bsrpvqht33zc)
- [Company: Zilliz](https://rewindex.com/company/zilliz.md)

## Part of an outage event

- [Google Cloud outage, Jun 12, 2025: 101 vendors, 107 incidents](https://rewindex.com/events/2025-06-12-google-cloud)
- This incident blames Google Cloud as the cause. (hop 1, posted +12 h 16 min vs the first vendor naming Google Cloud)
- Evidence: “…GCP outage impacting clusters in gcp-us-east4, gcp-us-central1, gcp-us-asia-southeast1 regions GCP experienced an outage which impacted our ability to access GCS object storage and GCR image repositor…”

```mermaid
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["Zilliz (this incident)<br/>posted +12 h 16 min"]:::me
  later --- me
```

_Detected automatically from incidents that started together and named the same provider; a link means one incident named another vendor, not a confirmed cause._

## Timeline of updates

- **resolved** 2025-06-12 20:00 UTC: GCP experienced an outage which impacted our ability to access GCS object storage and GCR image repository services. This resulted in some Zilliz Cloud clusters to be unavailable in the GCP regions of gcp-us-east4, gcp-us-central1, and gcp-us-asia-southeast1. Cluster creation and edit operations were also impacted in those regions. As of now, GCP services have fully recovered, and our services have fully recovered as well.

## Rewindex changes for this incident

- 2025-06-13 06:11 UTC: [Major incident: GCP outage impacting clusters in gcp-us-east4, gcp-us-central1, gcp-us-asia-southeast1 regions](https://rewindex.com/change/i5114caa0421771.md)


---
Canonical: https://rewindex.com/company/zilliz/incidents/j19950y7g2r0 · Markdown: https://rewindex.com/company/zilliz/incidents/j19950y7g2r0.md · JSON: https://rewindex.com/api/v1/companies/zilliz/incidents/j19950y7g2r0 · Generated 2026-10-19T21:10:43.697Z