GCP Availability

What to do

• Check whether you use InfluxDB Cloud Web UI, API Writes, API Queries, Tasks. Check your stack

  Drop a package.json, lockfile, Terraform or a list of domains at down.guide 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.

Root cause

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.

Updates from InfluxDB Cloud 9

1. investigatingJun 12, 2025, 6:37 PM UTC

   We are currently investigating query availability in GCP regions.

   provider

2. investigatingJun 12, 2025, 6:43 PM UTC

   We are continuing to investigate this issue.

   provider

3. investigatingJun 12, 2025, 7:18 PM UTC

   We are continuing to investigate this issue.

   provider

4. identifiedJun 12, 2025, 7:26 PM UTC

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

   provider

5. identifiedJun 12, 2025, 8:19 PM UTC

   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

6. identifiedJun 12, 2025, 8:49 PM UTC

   Services are beginning to recover as underlying infrastructure becomes available.

   provider

7. monitoringJun 12, 2025, 8:50 PM UTC

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

   provider

8. resolvedJun 12, 2025, 9:53 PM UTC

   All GCP services have been recovered.

   provider

9. postmortemJun 20, 2025, 10:33 PM UTC

   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

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.