InfluxData incident

Query Performance Degradation in Azure West Europe

Major Resolved View vendor source →

InfluxData experienced a major incident on September 29, 2026 affecting API Queries, lasting 3d 12h. The incident has been resolved; the full update timeline is below.

Started
Sep 29, 2026, 05:28 AM UTC
Resolved
Oct 02, 2026, 06:17 PM UTC
Duration
3d 12h
Detected by Pingoru
Sep 29, 2026, 05:28 AM UTC

Affected components

API Queries

Update timeline

  1. investigating Sep 29, 2026, 05:28 AM UTC

    We are currently investigating an issue affecting query performance in Azure West Europe.

  2. investigating Sep 29, 2026, 06:38 AM UTC

    We are continuing to investigate this issue and will provide further updates as soon as available.

  3. identified Sep 29, 2026, 09:09 AM UTC

    The issue has been identified and a fix is being implemented.

  4. identified Sep 29, 2026, 11:34 AM UTC

    We are continuing to work on a fix for this issue.

  5. identified Sep 29, 2026, 03:25 PM UTC

    We are continuing work to remediate immediate query performance degradation, and investigating actions for a permanent fix.

  6. monitoring Sep 29, 2026, 04:39 PM UTC

    Query performance has returned to normal levels. Planned stabilisation work is still ongoing, and we are monitoring closely.

  7. monitoring Sep 29, 2026, 06:33 PM UTC

    Query performance remains stable, and we continue to monitor closely. Additional mitigation and stabilization work is ongoing.

  8. monitoring Sep 29, 2026, 11:31 PM UTC

    Query performance remains stable, and we continue to monitor closely as traffic increases. We will continue to assess performance and provide updates.

  9. monitoring Sep 30, 2026, 07:34 AM UTC

    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.

  10. identified Sep 30, 2026, 07:53 AM UTC

    We have identified the issue and the team is actively working on implementing a fix.

  11. investigating Sep 30, 2026, 08:50 AM UTC

    We are still having issues in the region, the engineering team is working on it.

  12. investigating Sep 30, 2026, 10:49 AM UTC

    We are continuing to investigate this issue.

  13. investigating Sep 30, 2026, 12:08 PM UTC

    We are continuing to investigate this issue.

  14. investigating Sep 30, 2026, 01:44 PM UTC

    We have made several recent changes to improve query performance and we continue to monitor the region closely.

  15. monitoring Sep 30, 2026, 02:24 PM UTC

    Performance has returned to normal levels following an update. We will continue to monitor.

  16. monitoring Sep 30, 2026, 05:16 PM UTC

    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.

  17. monitoring Oct 01, 2026, 08:13 AM UTC

    The cluster remains stable, and we are continuing to monitor it.

  18. resolved Oct 02, 2026, 06:17 PM UTC

    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.