- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API Queries, Tasks
- Regions
- us, us-central-1, us-central1
- Down Index
- 42of 100
What to do
Check whether you use InfluxDB Cloud API Queries, Tasks in us, us-central-1, us-central1. 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 2h 48m it lasted.
Anything that failed between 2025-11-10 21:04 UTC and 2025-11-10 23:52 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 5
- investigating
We are investigating increased query errors within the region
provider
- investigating
We are continuing to investigate this issue.
provider
- monitoring
A fix has been implemented and we are monitoring the results.
provider
- resolved
This incident has been resolved.
provider
- postmortem
RCA for Cloud 2 prod01-us-central-1 query outage on Nov 10, 2025 # Summary The SRE team has been working on a long-term project to review and rebalance the storage workloads, to provide better separation of workloads within nodepools, which will improve performance, reliability and ease of maintenance. The Cloud 2 service is designed with a set of primary and secondary storage pods. During normal deployments, whenever a primary pod is restarted, the secondary pod takes over, so that the service is not interrupted. The change that was made in this cluster was a change to the primary and the secondary pods. When the configuration change was made in prod01-us-central-1, it caused some of the primary storage pods and their corresponding secondary pods to be restarted at the same time. While the pods were unavailable, queries failed. Once the pods restarted, the query error rate went back to normal levels and the cluster recovered. # Timeline **Time \(UTC\) What happened** **8:45pm** The engineer-on-call was paged due to a high rate of query errors in the cluster. Upon investigation, the primary and secondary pods for the same storage slice are unavailable. **8:50pm** Engineer-on-call identified that the problem was due to a misconfiguration that caused the primary and secondary pods to be restarted at the same time. **9:00pm** The system will recover by itself when the pods restart with the new configuration, so no intervention is required. **9:20pm** Queriers start recovering, and error rate is returning to pre-incident level. Some lingering errors in nginx. **10:00pm** Query backlog is fully cleared. The cluster has fully recovered. # Future Mitigations **1. Reviewing procedures relating to storage pod reconfigurations** Going forward we will ensure that configuration changes for primary pods and secondary pods are never applied at the same time.
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-73f7d8467c
Is InfluxDB Cloud still down?
No, this incident was resolved 2025-11-10 23:52 UTC. For InfluxDB Cloud's live state, see https://down.guide/influxdata.
How long did it last?
2h 48m, from 2025-11-10 21:04 UTC to 2025-11-10 23:52 UTC, by the times InfluxDB Cloud posted.
What was affected?
InfluxDB Cloud named API Queries, Tasks in us, us-central-1, us-central1.
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.