Is InfluxDB Cloud Down?

# RCA # Query Performance Degradation in Azure West Europe, September 27 to October 1, 2026 ## Summary From the evening of September 27 to the morning of September 30 \(UTC\), customers in the Azure West Europe region experienced slow queries and timeouts. Writes were accepted throughout, but on some partitions, new data was not immediately queryable. Earlier incidents on this cluster \(September 7, 11, 15 and 16\) produced the same symptom with different triggers and have their own RCAs. We believe the condition described herein was the root cause of all prior incidents. ## Cause All data in the cluster is stored on redundant pods across many physical nodes. These pods read time-series data through memory-mapped files. The host’s operating system keeps the most frequently accessed parts of those files in a page cache built from memory not consumed by the pods themselves. In this region, each pod holds about 365 GB of data. The cache on a host could not hold the data its pods were querying, so reads that would normally come from cache became page faults served from disk. Each pod read about 90 MB/s from disk, thus a host with ten pods reached roughly 990 MB/s, which is near the throughput ceiling on each host. Memory consumption looked normal on every metric we monitor. The storage process itself uses little memory, and the cache takes the remainder, so a shortage would not appear as memory pressure or shortfall. At the throughput ceiling, index lookups on the write path were delayed by disk reads, causing writes to fall behind and pods to fail their replication-lag health check. Pods in this region spent 8.9% of the day past the lag threshold, against 0.09% in a comparable region. At peak, both replicas of the busiest partitions fell behind together, creating access delays which were most acutely visible through the query path. Slow disk caused health and readiness checks to time out, so healthy pods were removed from rotation and restarted. Each restart took 30 to 85 minutes to recover, during which the pod's partner carried the load alone, with the rebuild adding even more disk load. A file-reference safeguard was also causing 50\+ pod restarts a day where a normal rate would be 0. ## Remediation While early changes helped, and resolved many trouble indicators, they did not solve the root cause. We doubled query-layer capacity, restarted pods, raised the readiness timeouts, raised cleanup timeouts to avoid safeguard restarts, and doubled recovery concurrency after a restart. We ruled out a controller lock, a per-disk limit, and a single tenant's load. The root cause fix was to raise each storage pod's resource request so that each host holds fewer pods. Each pod now has twice as much memory for page cache and disk throughput. Within 1 hour of this change, query abandonment fell from 31% to 0.1%. Page faults and disk reads dropped sharply. During the next morning's peak, abandonment was 0.06%, within normal limits. ## Timeline \(UTC\) Sep 27 22:58 - Query queue depth alert fires; incident opened. Query-layer capacity increased over the next hours without lasting effect Sep 28 07:00 - Degradation at morning peak; storage pods fall behind on writes and fail health checks; stuck pods restarted one at a time Sep 28 11:33 - Restart loop identified: slow disk causes health checks to trigger restart; each restart takes 30 to 85 minutes to recover Sep 28 13:45 - Lost file-reference cleanup identified as a second source of forced restarts Sep 29 08:58 - Readiness probe timeout raised and rolled out fleet-wide Sep 29 11:10 - Throughput appears to recover; degradation returns, with 36% of queries abandoned Sep 29 16:20 - Queue clears after recovery-concurrency and probe changes Sep 30 00:25 - Cleanup timeout raised to 24 hours; forced restarts stop Sep 30 07:00 - Degradation at peak; abandonment about 55% Sep 30 11:59 - Analysis shows cache capacity per pod is too small and disk reads are at the host ceiling Sep 30 12:43 - Rollout begins to spread pods across more nodes Sep 30 13:21 - Query performance returns to normal; abandonment down to 0.1% within the hour Sep 30 14:20 - Page faults and disk reads confirmed sharply lower after rollout Oct 1 07:00 to 09:00 - Morning peak with 0.06% abandonment versus 40% to 55% the day before Oct 1 09:48 - Incident declared resolved internally ## Future mitigation We added warning alerts for page-fault rate, cache coverage, disk reads on storage volumes, and query abandonment. Each alert is designed so that cache pressure appears before causing external visibility. Runbooks now suggest major page faults as a leading indicator of storage performance degradation, with details on “relief valves” available to tune. We are continuing to track down the storage-engine reference leak and moving the disk check out of the health path. Neither leak nor check is a risk factor for triggering this type of incident; they are conditions observed during diagnosis and remediation that warrant investigation. --- [2026-10-02T18:17:38.987Z] (resolved) We appreciate the continued patience while we worked through this incident. We have been monitoring the previous fixes for the last 24 hours and all changes have responded well during sustained traffic. The region is stable and we are resolving this incident. An RCA is in progress and will be added to our status page as soon as its available. --- [2026-10-01T08:13:30.571Z] (monitoring) The cluster remains stable, and we are continuing to monitor it. --- [2026-09-30T17:16:46.712Z] (monitoring) We have increased isolation in the storage layer for the impacted region to provide greater amounts of resilience and to allow for faster recovery. We are continuing to investigate heightened memory consumption and page faults within the storage layer. Query success rates and response durations have returned to normal levels. We will continue work to increase the resiliency of this region over the next 24 hours and will carefully monitor for any increase in query latency. --- [2026-09-30T14:24:27.641Z] (monitoring) Performance has returned to normal levels following an update. We will continue to monitor. --- [2026-09-30T13:44:45.487Z] (investigating) We have made several recent changes to improve query performance and we continue to monitor the region closely. --- [2026-09-30T12:08:49.315Z] (investigating) We are continuing to investigate this issue. --- [2026-09-30T10:49:34.213Z] (investigating) We are continuing to investigate this issue. --- [2026-09-30T08:50:06.120Z] (investigating) We are still having issues in the region, the engineering team is working on it. --- [2026-09-30T07:53:39.157Z] (identified) We have identified the issue and the team is actively working on implementing a fix. --- [2026-09-30T07:34:55.022Z] (monitoring) We are working on resolving the ongoing intermittent query performance. During peak usage periods, large or complex queries may run slower than normal. Writes and data durability are not affected at this time. We have deployed several improvements overnight and further changes are in progress. --- [2026-09-29T23:31:39.791Z] (monitoring) Query performance remains stable, and we continue to monitor closely as traffic increases. We will continue to assess performance and provide updates. --- [2026-09-29T18:33:55.579Z] (monitoring) Query performance remains stable, and we continue to monitor closely. Additional mitigation and stabilization work is ongoing. --- [2026-09-29T16:39:16.891Z] (monitoring) Query performance has returned to normal levels. Planned stabilisation work is still ongoing, and we are monitoring closely. --- [2026-09-29T15:25:18.270Z] (identified) We are continuing work to remediate immediate query performance degradation, and investigating actions for a permanent fix. --- [2026-09-29T11:34:16.264Z] (identified) We are continuing to work on a fix for this issue. --- [2026-09-29T09:09:03.331Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-09-29T06:38:24.885Z] (investigating) We are continuing to investigate this issue and will provide further updates as soon as available. --- [2026-09-29T05:28:12.501Z] (investigating) We are currently investigating an issue affecting query performance in Azure West Europe.

This incident has been resolved. --- [2026-09-28T18:01:24.078Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-09-28T15:08:38.481Z] (identified) We are continuing to work on a fix for this issue. --- [2026-09-28T13:10:13.328Z] (identified) We are continuing to work on a fix for this issue. --- [2026-09-28T11:45:06.078Z] (identified) We are continuing to work on a fix for this issue. --- [2026-09-28T09:54:38.250Z] (identified) Some queries may be slower than normal and recently written data may take longer to appear in results. Data ingestion and durability are not affected. We have identified the cause and mitigation is underway --- [2026-09-28T08:33:14.107Z] (investigating) We are currently investigating this issue.

This incident has been resolved. --- [2026-09-16T12:56:48.326Z] (monitoring) A fix has been implemented and we are monitoring the results. --- [2026-09-16T11:26:47.067Z] (identified) The issue has been identified and a fix is being implemented. --- [2026-09-16T10:08:27.413Z] (investigating) We are currently investigating this issue.