- Level
- confirmed
- Worst impact
- Major outage
- Components
- Web UI, API Writes, API Queries, Tasks
- Down Index
- 43of 100
What to do
Check whether you use InfluxDB Cloud Web UI, API Writes, API Queries, Tasks. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 3h 15m it lasted.
Anything that failed between 2025-06-12 18:37 UTC and 2025-06-12 21:53 UTC may need a replay.Subscribe to InfluxDB Cloud's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=influxdata works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from InfluxDB Cloud 9
- investigating
We are currently investigating query availability in GCP regions.
provider
- investigating
We are continuing to investigate this issue.
provider
- investigating
We are continuing to investigate this issue.
provider
- identified
Google Cloud Platform is experiencing a major incident. More details on this incident can be found at https://status.cloud.google.com/
provider
- 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/
provider
- identified
Services are beginning to recover as underlying infrastructure becomes available.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
All GCP services have been recovered.
provider
- 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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-2ecdf58527
Is InfluxDB Cloud still down?
No, this incident was resolved 2025-06-12 21:53 UTC. For InfluxDB Cloud's live state, see https://down.guide/influxdata.
How long did it last?
3h 15m, from 2025-06-12 18:37 UTC to 2025-06-12 21:53 UTC, by the times InfluxDB Cloud posted.
What was affected?
InfluxDB Cloud named Web UI, API Writes, API Queries, Tasks.
What caused it?
InfluxDB Cloud hasn't published a root cause. If it does, it shows here.
Where does this come from?
InfluxDB Cloud's official status page, https://status.influxdata.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.