Provider
InfluxDB CloudIncident detail
GCP Availability
Timeline window
to
Get alerted the next time InfluxDB Cloud breaks
Free email alerts for the handful of vendors you cannot afford to miss. No card, live in about a minute. Paid plans add Slack, Teams, Discord, and webhook delivery across your whole stack, plus higher API quotas.
Timeline
Incident updates
Every update on the official status source, oldest to newest, exactly as it appeared there.
Investigating
We are currently investigating query availability in GCP regions.
Investigating
We are continuing to investigate this issue.
Investigating
We are continuing to investigate this issue.
Identified
Google Cloud Platform is experiencing a major incident. More details on this incident can be found at https://status.cloud.google.com/
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/
Identified
Services are beginning to recover as underlying infrastructure becomes available.
Monitoring
A fix has been implemented and we are monitoring the results.
Resolved
All GCP services have been recovered.
Resolved
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 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.
Keep exploring
More from InfluxDB Cloud
Neighboring incidents on InfluxDB Cloud's timeline and the rest of their record on OutageDeck.