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…”
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.
What changed
Struck in red is what InfluxData (InfluxDB Cloud) removed; blue is what they added. Muted text is unchanged context.
BeforeAfter
AddedTitle#1
Before: not present
After: GCP Availability
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: postmortem
AddedStart time#4
Before: not present
After: 2025-06-12 18:37 UTC
AddedResolved time#5
Before: not present
After: 2025-06-12 21:53 UTC
AddedAffected components#6
Before: not present
After: API Queries, API Writes, Cloud Serverless: GCP - API Queries, Cloud Serverless: GCP - API Writes, Cloud Serverless: GCP - Tasks, Cloud Serverless: GCP - Web UI, Tasks, Web UI
AddedUpdateinvestigating#7
Before: not present
After: We are currently investigating query availability in GCP regions.
AddedUpdateinvestigating#8
Before: not present
After: We are continuing to investigate this issue.
AddedUpdateinvestigating#9
Before: not present
After: We are continuing to investigate this issue.
AddedUpdateidentified#10
Before: not present
After: Google Cloud Platform is experiencing a major incident. More details on this incident can be found at https://status.cloud.google.com/
AddedUpdateidentified#11
Before: not present
After: 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/
AddedUpdateidentified#12
Before: not present
After: Services are beginning to recover as underlying infrastructure becomes available.
AddedUpdatemonitoring#13
Before: not present
After: A fix has been implemented and we are monitoring the results.
AddedUpdateresolved#14
Before: not present
After: All GCP services have been recovered.
AddedUpdatepostmortem#15
Before: not present
After: **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.