# InfluxData (InfluxDB Cloud): Elevated Query Error Rate

- Impact (vendor’s label): major
- Status: postmortem
- Started: 2025-06-13 16:13 UTC · Resolved: 2025-06-13 22:14 UTC · Duration: 6.0 h
- Updates: 7 · Affected components: API Queries, Cloud Serverless: Azure, W. Europe - API Queries, Cloud Serverless: Azure, W. Europe - Tasks, Tasks
- [Vendor status page: https://stspg.io/dr1qcyz96q2c](https://stspg.io/dr1qcyz96q2c)
- [Company: InfluxData (InfluxDB Cloud)](https://rewindex.com/company/influxdata.md)

## Timeline of updates

- **investigating** 2025-06-13 16:13 UTC: We have observed an elevated query error rate and are investigating.
- **identified** 2025-06-13 17:06 UTC: The issue has been identified and a fix is being put into place.
- **monitoring** 2025-06-13 17:39 UTC: A fix has been implemented and deployed. We are monitoring at this time.
- **monitoring** 2025-06-13 19:09 UTC: We are continuing to closely monitor the health of the query API
- **monitoring** 2025-06-13 20:36 UTC: We are continuing to monitor this region for any further degradation
- **resolved** 2025-06-13 22:14 UTC: This incident has been resolved.
- **postmortem** 2025-07-17 20:26 UTC: 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.

## Rewindex changes for this incident

- 2025-06-13 16:13 UTC: [Major incident: Elevated Query Error Rate](https://rewindex.com/change/i651c4facad2e47.md)


---
Canonical: https://rewindex.com/company/influxdata/incidents/6td078k435km · Markdown: https://rewindex.com/company/influxdata/incidents/6td078k435km.md · JSON: https://rewindex.com/api/v1/companies/influxdata/incidents/6td078k435km · Generated 2026-10-19T23:15:18.772Z