- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API Queries, Tasks
- Regions
- eu
- Down Index
- 35of 100
What to do
Check whether you use InfluxDB Cloud API Queries, Tasks in eu. 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 6h it lasted.
Anything that failed between 2025-06-13 16:13 UTC and 2025-06-13 22:14 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 7
- investigating
We have observed an elevated query error rate and are investigating.
provider
- identified
The issue has been identified and a fix is being put into place.
provider
- monitoring
A fix has been implemented and deployed. We are monitoring at this time.
provider
- monitoring
We are continuing to closely monitor the health of the query API
provider
- monitoring
We are continuing to monitor this region for any further degradation
provider
- resolved
This incident has been resolved.
provider
- postmortem
In a multi-tenant environment, such as Cloud 2, there can be unpredictable changes in workload, as different customers on the shared platform may increase or decrease their activity on the cluster with no advance notice. While we try to shelter customers from one another, via rate limits and some partitioning, there is no way to fully protect customers from the impact of a "noisy neighbor". We maintain excess capacity in the cluster to provide some amount of headroom for increased workloads, and we also have rate limits to ensure that one customer does not overwhelm the cluster \(via writes, deletes or queries\), but the rate limits are not very fine-grained, and at times, a single customer can stress the cluster. When that occurs, the team is automatically notified, and we add additional resources to accommodate the extra workload. It can sometimes take time for the extra capacity to be fully deployed, leading to temporary performance problems. This is what occurred in the Azure eu-west cluster on June 13th. We were notified that query performance was degraded and the team increased the storage pods to provide extra capacity. Once the storage pods limits were fully applied, the query TTBR recovered. We apologize for the inconvenience.
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-6905cdcd23
Is InfluxDB Cloud still down?
No, this incident was resolved 2025-06-13 22:14 UTC. For InfluxDB Cloud's live state, see https://down.guide/influxdata.
How long did it last?
6h, from 2025-06-13 16:13 UTC to 2025-06-13 22:14 UTC, by the times InfluxDB Cloud posted.
What was affected?
InfluxDB Cloud named API Queries, Tasks in eu.
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.