Rewindex

CompaniesInfluxData (InfluxDB Cloud)Incidents

InfluxData (InfluxDB Cloud): GCP Availability

CriticalStatus: postmortemStarted Resolved (3.3 h)9 updatesstspg.io (opens in new tab)
Part of an outage event

Google Cloud outage, Jun 12, 2025 · 101 vendors, 107 incidents

InfluxData (InfluxDB Cloud)’s incident blames Google Cloud as the cause. (hop 1, posted +43 min vs the first vendor naming Google Cloud)

“…GCP Availability **RCA - Service Outage on June 12, 2025** ‌ **Summary** On June 12, 2025, at 17:51 UTC, Google Cloud Platform \(GCP\) experienced a global outage that disrupted a wide range of cloud…”

Swipe sideways to see the whole diagram.

blamed Firebaseblamed Anthropicblamed CloudflareGoogle Cloudown incident not archivedWithin an hour29 vendors, 28 blamed Google CloudPinecone, Northflank, imgix +261 to 4 hours later12 vendors, 11 blamed Google CloudSmartsheet, Daily, Confluent +9Later1 vendor, 1 blamed Google CloudZillizFirebaseown incident not archivedCodeium, Windsurf+13 minAnthropicposted +28 min, did not name GoogleCloudGitHub, GitHub Copilot+24 minCloudflareown incident not archivedDoppler, Jupyter (Anaconda), Socket+4+35 min to +3 h 41 minInfluxData (InfluxDB Cloud) (thisincident)posted +43 min
blamed Firebaseblamed Anthropicblamed CloudflareGoogle Cloudown incident not archivedWithin an hour29 vendors, 28 blamed GoogleCloudPinecone, Northflank, imgix +261 to 4 hours later12 vendors, 11 blamed GoogleCloudSmartsheet, Daily, Confluent +9Later1 vendor, 1 blamed GoogleCloudZillizFirebaseown incident not archivedCodeium, Windsurf+13 minAnthropicposted +28 min, did not nameGoogle CloudGitHub, GitHub Copilot+24 minCloudflareown incident not archivedDoppler, Jupyter (Anaconda),Socket +4+35 min to +3 h 41 minInfluxData (InfluxDB Cloud) (thisincident)posted +43 min
InfluxData (InfluxDB Cloud) is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
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["InfluxData (InfluxDB Cloud) (this incident)<br/>posted +43 min"]:::me
  h1 --- me

Full 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: API QueriesCloud Serverless: GCP - API QueriesCloud Serverless: GCP - Web UIWeb UIAPI WritesCloud Serverless: GCP - API WritesCloud Serverless: GCP - TasksTasks

Timeline of updates

  1. investigating

    We are currently investigating query availability in GCP regions.

  2. investigating

    We are continuing to investigate this issue.

  3. investigating

    We are continuing to investigate this issue.

  4. identified

    Google Cloud Platform is experiencing a major incident. More details on this incident can be found at https://status.cloud.google.com/

  5. identified

    Our team is awaiting recovery of the underlying GCP infrastructure and is prepared to bring all services online upon recovery. More incident related information can be found at https://status.cloud.google.com/

  6. identified

    Services are beginning to recover as underlying infrastructure becomes available.

  7. monitoring

    A fix has been implemented and we are monitoring the results.

  8. resolved

    All GCP services have been recovered.

  9. postmortem

    **RCA - Service Outage on June 12, 2025** ‌ **Summary** On June 12, 2025, at 17:51 UTC, Google Cloud Platform \(GCP\) experienced a global outage that disrupted a wide range of cloud services, including core infrastructure on which InfluxDB Cloud relies. As a result, all InfluxDB Cloud services hosted on GCP became temporarily unavailable.  ‌ While most services recovered automatically once Google services were restored, manual intervention was required to fully resume Flux task processing. ‌ **Customer Impact** Writes and queries to InfluxDB Cloud began to fail across GCP-hosted regions on June 12, at 17:51 UTC and remained unavailable until InfluxData’s cluster became operational on June 12, at 20:30 UTC. Google announced full service restoration on June 13, at 01:18 UTC. ‌ We received a report of Flux tasks not processing on June 12, 23:20 UTC. Flux task processing was restored on June 12, at approximately 23:50 UTC.  ‌ **Cause of the Incident** See [details](https://status.cloud.google.com/incidents/ow5i3PPK96RduMcb1SsW) on the GCP incident timeframe and root cause analysis. Flux task processing was impacted due to service recovery issues. ‌ **Investigation and Recovery** We actively monitored GCP service restoration via email and its status page. For InfluxDB Cloud services, the majority of services were restored without manual intervention. However, manual intervention was needed to restore Flux task processing. This intervention effectively restarted impacted services, resulting in the full restoration of Flux task processing.

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).

InfluxData (InfluxDB Cloud) profileRecent InfluxData (InfluxDB Cloud) incidentsMarkdownJSON