CompaniesInfluxData (InfluxDB Cloud)Incidents
InfluxData (InfluxDB Cloud): Transient API unavailability in GCP US-Central Region
Timeline of updates
- resolved
Starting at 1:51 UTC we began a node drain operation to move workloads over to another node pool. This operation resulted in an unhealthy load balancer backend with no failover. During 1:51 UTC and 1:52 UTC connections to us-central1-1.gcp.cloud2.influxdata.com would have received a timeout. We immediately forced nodes back into the load balancer and services were returning to operational status at 1:53 UTC. Services were fully restored at 1:57 UTC for the us-central1-1 endpoint.
From InfluxData (InfluxDB Cloud)’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.influxdata.com (opens in new tab).
Cite this
Status incident (vendor impact label: none) posted by InfluxData (InfluxDB Cloud), started 2021-04-27 14:47 UTC, resolved after 0 min, 1 update(s).
- Title
- Transient API unavailability in GCP US-Central Region
- Vendor
- InfluxData (InfluxDB Cloud)
- Date
- URL
- https://rewindex.com/company/influxdata/incidents/9j60hq5x71pm
InfluxData (InfluxDB Cloud) profileRecent InfluxData (InfluxDB Cloud) incidentsAll outages on April 27, 2021InfluxData (InfluxDB Cloud) in April 2021MarkdownJSON