InfluxData

Affected: API Queries

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-09-29 05:28 UTC

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

2. investigating 2026-09-29 06:38 UTC

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

3. identified 2026-09-29 09:09 UTC

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

4. identified 2026-09-29 11:34 UTC

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

5. identified 2026-09-29 15:25 UTC

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

6. monitoring 2026-09-29 16:39 UTC

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

7. monitoring 2026-09-29 18:33 UTC

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

8. monitoring 2026-09-29 23:31 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 2026-09-30 07:34 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...

10. identified 2026-09-30 07:53 UTC

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

11. investigating 2026-09-30 08:50 UTC

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

12. investigating 2026-09-30 10:49 UTC

    We are continuing to investigate this issue.

13. investigating 2026-09-30 12:08 UTC

    We are continuing to investigate this issue.

14. investigating 2026-09-30 13:44 UTC

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

15. monitoring 2026-09-30 14:24 UTC

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

16. monitoring 2026-09-30 17:16 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...

17. monitoring 2026-10-01 08:13 UTC

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

18. resolved 2026-10-02 18:17 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...

19. postmortem 2026-10-06 19:00 UTC

    # 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...

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-09-28 08:33 UTC

   We are currently investigating this issue.

2. identified 2026-09-28 09:54 UTC

   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

3. identified 2026-09-28 11:45 UTC

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

4. identified 2026-09-28 13:10 UTC

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

5. identified 2026-09-28 15:08 UTC

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

6. monitoring 2026-09-28 18:01 UTC

   A fix has been implemented and we are monitoring the results.

7. resolved 2026-09-28 20:19 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-09-16 10:08 UTC

   We are currently investigating this issue.

2. identified 2026-09-16 11:26 UTC

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

3. monitoring 2026-09-16 12:56 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-09-16 16:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Auth0 User Authentication

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-09-11 16:32 UTC

   The SSO Login Service is currently experiencing downtime and the team is currently looking into it

2. monitoring 2026-09-11 16:37 UTC

   The engineering team has resolved the issue and is continuing to monitor the health of the SSO Login Service

3. resolved 2026-09-11 19:26 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. identified 2026-09-11 08:45 UTC

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

2. monitoring 2026-09-11 09:27 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-09-11 09:46 UTC

   This incident has been resolved.

4. postmortem 2026-09-28 13:14 UTC

   # **Root Cause Analysis: Query Latency on September 11, 2026** Region: Azure West Europe Cluster: prod01-eu-west-1 ‌ ‌ **Incident report: query latency in Azure West Europe, September 11, 2026** On the morning of September 11, some customers in Azure West Europe saw slower than...

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. identified 2026-09-07 10:11 UTC

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

2. identified 2026-09-07 11:13 UTC

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

3. identified 2026-09-07 13:11 UTC

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

4. identified 2026-09-07 14:52 UTC

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

5. monitoring 2026-09-07 15:37 UTC

   A fix has been implemented and we are monitoring the results.

6. resolved 2026-09-07 16:03 UTC

   This incident has been resolved.

7. postmortem 2026-09-28 13:11 UTC

   # **Root Cause Analysis: Query Latency on September 7, 2026** Region: Azure West Europe Cluster: prod01-eu-west-1 ## **Summary and impact** On September 7, 2026, some customers in Azure West Europe experienced increased query latency. Query success rates and write operations...

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. identified 2026-08-25 13:49 UTC

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

2. monitoring 2026-08-25 14:29 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-08-25 15:41 UTC

   This incident has been resolved.

4. postmortem 2026-09-28 13:00 UTC

   # **Root Cause Analysis: Query Latency on August 25, 2026** Region: Azure West Europe Cluster: prod01-eu-west-1 ## **Summary and impact** On August 25, 2026, some customers in Azure West Europe experienced increased query latency and query timeouts. Additional query capacity...

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-05-27 15:51 UTC

   We are currently investigating this issue.

2. monitoring 2026-05-27 16:00 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-05-27 16:58 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-03-17 19:18 UTC

   We are currently investigating intermittent query failures affecting queries in AWS eu-central-1.

2. monitoring 2026-03-17 20:38 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2026-03-17 22:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Writes, API Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS, Azure.

Started during Azure: Azure OpenAI – GPT-5.2 availability degradation in 7 regions.

1. investigating 2026-03-10 17:26 UTC

   We are currently investigating this issue.

2. identified 2026-03-10 18:40 UTC

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

3. monitoring 2026-03-10 19:38 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2026-03-10 20:24 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Writes

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-03-06 03:05 UTC

   We are currently investigating elevated ingest failure rates affecting Cloud Serverless in the EU-Central region.

2. resolved 2026-03-06 04:34 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Management API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-18 23:23 UTC

   This is to notify that there is an outage of the Cloud Dedicated Management API and Admin UI, but writes/queries are not affected. Our platform team is continuing to investigate the issue.

2. monitoring 2026-02-18 23:49 UTC

   The issue has been identified and the fix has been implemented. Cloud Dedicated Management API and Admin UI should be accessible now.

3. resolved 2026-02-19 00:10 UTC

   Cloud Dedicated Management API and Admin UI access issue has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Management API

Failure mode: Orchestration, control plane, service discovery or load balancing failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2026-02-16 16:48 UTC

   This is to notify that there is an outage of the Cloud Dedicated Management API and Admin UI, but writes/queries are not affected. Our platform team is working to resolve this issue.

2. investigating 2026-02-16 18:12 UTC

   This is to notify that there is an outage of the Cloud Dedicated Management API and Admin UI, but writes/queries are not affected. Our platform team is continuing to investigate the issue.

3. identified 2026-02-16 19:58 UTC

   The issue has been identified and the fix has been implemented. Cloud Dedicated Management API and Admin UI should be accessible now.

4. identified 2026-02-16 19:58 UTC

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

5. monitoring 2026-02-16 20:49 UTC

   Cloud Dedicated Management API and Admin UI are accessible now. We are continuing to monitor.

6. resolved 2026-02-17 17:11 UTC

   Cloud Dedicated Management API and Admin UI access issue has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2026-02-12 11:26 UTC

   We are aware of the query errors in Azure West Europe and we are currently investigating it.

2. monitoring 2026-02-12 12:08 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2026-02-12 14:36 UTC

   We are continuing to monitor and fix any sub issues related to the incident.

4. resolved 2026-02-12 16:31 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Web UI, API Queries

Failure mode: A code release introduced the failure. Root cause: A bug in the vendor's own code. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-02-10 17:37 UTC

   We are investigating an issue related to queries. Some recent data is not showing up on query responses

2. identified 2026-02-10 18:12 UTC

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

3. identified 2026-02-10 19:21 UTC

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

4. identified 2026-02-10 21:40 UTC

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

5. identified 2026-02-10 22:54 UTC

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

6. identified 2026-02-11 01:37 UTC

   Our team has identified the issue and is actively working to restore data for affected users.

7. identified 2026-02-11 04:46 UTC

   Our team has identified the issue and is actively working to restore data for affected users.

8. identified 2026-02-11 07:32 UTC

   Our team has identified the issue and is actively working to restore data for affected users.

9. identified 2026-02-11 10:11 UTC

   Our team is actively working to restore data for affected users.

10. identified 2026-02-11 16:36 UTC

    Our team continues to actively work to restore data for all affected users.

11. identified 2026-02-11 18:57 UTC

    Our team continues to actively work to restore data for all affected users.

12. identified 2026-02-12 01:29 UTC

    Our team continues to actively work to restore data for all affected users.

13. identified 2026-02-12 07:46 UTC

    Our team continues to actively work to restore data for all affected users.

14. identified 2026-02-12 10:49 UTC

    Our team continues to actively work to restore data for all affected users.

15. identified 2026-02-13 01:43 UTC

    Our team continues to actively work to restore data for all affected users.

16. identified 2026-02-14 00:08 UTC

    Our team has been working around the clock to restore data availability for all affected users. Work will continue through the weekend with no interruption. We do not yet have a resolution timeline to share, but we are committed to providing updates as soon as they are available...

17. identified 2026-02-18 16:18 UTC

    We apologize for the ongoing disruption to prod101-us-east-1. We are continuing to restore data from our backups. During the restore, there may occasionally be heightened TTBR.

18. identified 2026-02-19 17:07 UTC

    Our team continues to actively work to restore data for all affected users.

19. identified 2026-02-20 23:41 UTC

    We apologize for the length of time that it has taken to restore customer data that was inadvertently deleted. The data is all available in our backups, but it is taking us an unacceptably long time to restore it. as we have had to balance the restoration of historical data with...

20. identified 2026-02-26 19:10 UTC

    We sincerely apologize for the length of this incident. Restoration of data from February 2 onwards is now substantially complete, and the second phase of restoration, covering data prior to February 2, is underway, and has already been completed for many of our customers. While...

21. resolved 2026-03-10 01:19 UTC

    This incident has been resolved

22. postmortem 2026-03-10 01:20 UTC

    ## Summary A software change was introduced that was intended to improve data compaction for very large partitions. The change had a bug that, under certain circumstances, caused some data to be dropped during the compaction process. When compaction completed, the new compacted...

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Web UI

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-01-26 22:45 UTC

   We are experiencing intermittent UI login errors on AWS US-East-1. Queries and writes are not affected. We are addressing the issue.

2. investigating 2026-01-26 22:48 UTC

   We are continuing to investigate this issue.

3. resolved 2026-01-26 22:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. monitoring 2026-01-23 03:19 UTC

   Our team identified some query failures affecting our US-EAST-1 region for InfluxCloud 2.0 (Serverless/IOx). A fix has been implemented but our team is monitoring closely in case any further issues resurface.

2. investigating 2026-01-23 03:32 UTC

   We are continuing to investigate a recurrence of query failures and errors. Our team is working toward a permanent resolution, and we will share further details as they become available.

3. identified 2026-01-23 04:39 UTC

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

4. monitoring 2026-01-23 06:09 UTC

   Our team continues to actively monitor for any issues.

5. resolved 2026-01-23 07:42 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Web UI

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-01-21 16:08 UTC

   We are currently investigating an Authentication issue that may impact access to database resources

2. resolved 2026-01-21 16:48 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-01-20 12:31 UTC

   We are aware of higher than normal query failures in the eu-central-1 region of AWS and are investigating the issue.

2. monitoring 2026-01-20 13:32 UTC

   Queries are back to normal levels in eu-central-1 and we are monitoring the cluster.

3. monitoring 2026-01-20 13:33 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-01-20 16:41 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Web UI, Other

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-01-15 17:18 UTC

   We are currently investigating intermittent authentication issues (read/write token authentication is not affected)

2. monitoring 2026-01-15 22:12 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2026-01-16 00:49 UTC

   A fix has been implemented and we are monitoring the results. Please let us know via the support portal if you see any issues logging in to your cloud account.

4. resolved 2026-01-16 16:21 UTC

   This incident has been resolved.

5. postmortem 2026-01-16 23:06 UTC

   **Summary** On January 15, 2026, user login for Cloud 2 was failing intermittently in the eu-central AWS cluster. The impact was that for some users, they could not login via the web UI. For others, they were able to login but then could not see their resources \(buckets,...

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2026-01-15 17:15 UTC

   We have implemented a fix and are monitoring the cluster.

2. resolved 2026-01-15 19:29 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2026-01-12 11:32 UTC

   A fix has been implemented and we are monitoring the results.

2. resolved 2026-01-12 12:10 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Web UI, API Writes, API Queries, Tasks

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-01-09 10:41 UTC

   We are currently investigating this issue.

2. investigating 2026-01-09 12:48 UTC

   We are continuing to investigate this issue.

3. investigating 2026-01-09 14:10 UTC

   We are continuing to investigate the issue

4. investigating 2026-01-09 15:43 UTC

   We are continuing to investigate this issue.

5. investigating 2026-01-09 17:16 UTC

   Tasks are running as expected but Task Run Reporting is still affected. The investigation continues into this and all other service issues.

6. investigating 2026-01-09 18:59 UTC

   We have resolved the issue with regard to task execution, and tasks are running correctly. We are still working on a related issue, where the task execution state is not showing correctly in the UI or APIs. This does not impact the tasks themselves

7. investigating 2026-01-09 22:21 UTC

   Task execution is working correctly. We are still fixing a UI/API display issue, which does not affect task behavior.

8. identified 2026-01-09 23:52 UTC

   We’ve identified the root cause and are implementing a remediation. Tasks remain operational, and reporting functionality is in the process of recovering.

9. monitoring 2026-01-10 02:43 UTC

   We are monitoring the recovery of task visibility in the region and will update here on any change of status.

10. monitoring 2026-01-10 10:19 UTC

    Task visibility has been restored to the region and we are continuing to monitor.

11. resolved 2026-01-13 15:55 UTC

    This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2026-01-08 13:24 UTC

   We are currently investigating a high number of query errors reported in eu-central-1.

2. monitoring 2026-01-08 13:34 UTC

   A fix has been implemented and we are monitoring the results.

3. monitoring 2026-01-08 16:39 UTC

   We are continuing to monitor for any further issues.

4. resolved 2026-01-08 18:18 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries, API Queries, Tasks, Tasks

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2026-01-06 21:27 UTC

   We are currently investigating an increase in query times in the US-EAST-1 and EU-CENTRAL-1 clusters.

2. investigating 2026-01-06 22:37 UTC

   We are currently investigating an increase in query times in the US-EAST-1 and EU-CENTRAL-1 clusters. Investigation is ongoing, and we will provide updates as more information becomes available.

3. identified 2026-01-06 22:45 UTC

   The root cause of the incident has been identified, and we are monitoring the clusters as they continue to recover.

4. identified 2026-01-07 00:16 UTC

   The impacted clusters continue to recover, and we are actively monitoring them.

5. identified 2026-01-07 01:25 UTC

   The root cause of the incident has been identified, and we are monitoring the clusters as they continue to recover.

6. monitoring 2026-01-07 02:17 UTC

   A fix has been implemented and we are monitoring the results.

7. monitoring 2026-01-07 04:34 UTC

   The underlying issue has been resolved, and our team is continuing to monitor the situation to ensure stability.

8. resolved 2026-01-07 05:16 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Reads

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-12-09 16:19 UTC

   we are investigating reports of a higher rate of query errors than normal in multiple Cloud Dedicated clusters

2. monitoring 2025-12-09 17:36 UTC

   Query performance is back to normal, but the team is continuing to investigate the issue

3. investigating 2025-12-09 20:15 UTC

   We are continuing to investigate this issue.

4. investigating 2025-12-09 20:18 UTC

   We are continuing to investigate this issue.

5. resolved 2025-12-09 22:11 UTC

   Query error rates have returned to normal levels

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-12-09 09:49 UTC

   We are currently investigating this issue.

2. investigating 2025-12-09 10:53 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-12-09 10:53 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-12-09 11:37 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Web UI, Web UI, API Queries, API Queries, Tasks, Tasks

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-11-20 21:03 UTC

   We are investigating an issue in the Serverless UI that is preventing measurements from being displayed in the dropdown list, or queried.

2. investigating 2025-11-20 21:33 UTC

   We are continuing to investigate this issue.

3. investigating 2025-11-20 21:37 UTC

   We are continuing to investigate this issue.

4. identified 2025-11-20 21:38 UTC

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

5. resolved 2025-11-20 21:39 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Web UI, Management API

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-11-20 08:52 UTC

   We have been made aware of issues with Google OAuth client, we are working with provider to solve the issue.

2. investigating 2025-11-20 08:54 UTC

   We are continuing to investigate this issue.

3. identified 2025-11-20 09:33 UTC

   We have tested extensively and found that Cloud dedicated clusters are still functional but we are aware of issues being able to perform certain admin api calls via influxctl

4. identified 2025-11-20 09:36 UTC

   We have tested extensively and found that Cloud dedicated clusters and Cloud 2 cluster are still functional, we can log in using credentials not via Goggle OAUTH. We are aware of issues being where certain admin api calls via influxctl are not able to be performed

5. identified 2025-11-20 10:14 UTC

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

6. monitoring 2025-11-20 12:50 UTC

   A fix has been implemented and we are monitoring the results.

7. resolved 2025-11-20 14:07 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries, Tasks

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-11-18 19:48 UTC

   We are investigating increased query errors within the region

2. investigating 2025-11-18 20:11 UTC

   We are continuing to investigate this issue.

3. identified 2025-11-18 21:30 UTC

   The issue has been identified. We are adding capacity to the cluster, to help clear the backlog more quickly

4. monitoring 2025-11-18 23:57 UTC

   A fix has been implemented and we are monitoring the results.

5. resolved 2025-11-19 01:47 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Web UI, API Queries

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS, Azure, Google Cloud.

1. investigating 2025-11-11 02:46 UTC

   Investigating fix.

2. identified 2025-11-11 03:20 UTC

   A fix has been implemented. We are monitoring whether read performance has improved.

3. identified 2025-11-11 05:49 UTC

   We are still seeing stability issues. Investigating other approaches.

4. identified 2025-11-11 06:15 UTC

   We are still working on the resolution. Access to the InfluxDB Cloud UI and API will result in internal errors.

5. identified 2025-11-11 10:35 UTC

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

6. identified 2025-11-11 14:36 UTC

   We are still working on the resolution.

7. identified 2025-11-11 14:45 UTC

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

8. identified 2025-11-11 15:13 UTC

   We have identified the issue and continuing to work on a fix, we are working on applying a fix.

9. identified 2025-11-11 16:03 UTC

   We have identified the issue and continuing to work on a fix.

10. identified 2025-11-11 17:19 UTC

    We have identified the issue and continuing to work on a fix.

11. identified 2025-11-11 19:02 UTC

    We have implemented a fix that is resulting in steady system recovery.

12. identified 2025-11-11 19:25 UTC

    Recovery is continuing to progress.

13. identified 2025-11-11 21:01 UTC

    Recovery is continuing, with setbacks.

14. identified 2025-11-11 22:56 UTC

    We apologize for the length of time that it is taking to bring this cluster back into service. The team is working diligently to restore normal operation.

15. identified 2025-11-11 22:57 UTC

    We apologize for the length of time that it is taking to bring this cluster back into service. The team is working diligently to restore normal operation

16. monitoring 2025-11-12 01:13 UTC

    We have increased the cluster capacity, and it’s currently recovering. However, due to a large backlog of data, the TTBR remains elevated for now. Our team continues to monitor this issue closely.

17. monitoring 2025-11-12 02:46 UTC

    The cluster has been scaled up, and system performance has returned to normal. Writes and queries are now processing as expected, and TTBR has stabilized. We sincerely apologize for the disruption to service over the past 24 hours and will share a detailed root cause analysis...

18. resolved 2025-11-12 04:17 UTC

    This incident has been resolved.

19. postmortem 2025-11-14 18:33 UTC

    RCA for Cloud 2 prod01-us-east-1 outage on Nov 11, 2025 # Summary The incident began during a planned migration of storage pods to a newer, more performant node class in Azure. The root cause was insufficient capacity in the new Azure node pool. When additional capacity could...

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries, Tasks

Failure mode: A configuration change caused the failure. Root cause: A human mistake during operations. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-11-10 21:04 UTC

   We are investigating increased query errors within the region

2. investigating 2025-11-10 22:17 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-11-10 22:48 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-11-10 23:52 UTC

   This incident has been resolved.

5. postmortem 2025-11-25 23:19 UTC

   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...

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Writes

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-11-05 18:17 UTC

   Writes may be degraded in us-east-1, and we're investigating

2. investigating 2025-11-05 19:01 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-11-05 19:53 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-11-05 21:54 UTC

   The incident has been resolved, and operations are back to normal

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-28 09:49 UTC

   We are seeing degraded performance in the us-east-1 region for queries. The team in continuing to investigate and will keep you updated

2. investigating 2025-10-28 10:05 UTC

   We are continuing to investigate this issue.

3. investigating 2025-10-28 10:46 UTC

   We are continuing to investigate this issue.

4. monitoring 2025-10-28 13:04 UTC

   A fix has been applied and error rates are on decline. We will continue to monitor the issue.

5. monitoring 2025-10-28 14:37 UTC

   Services continue to be healthy. We are continuing to monitor for any further issues.

6. resolved 2025-10-28 16:06 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Writes, API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-28 09:23 UTC

   We are still seeing Degraded performance in the region and some queries are failing. We are continuing to investigate and will post further updates.

2. investigating 2025-10-28 09:27 UTC

   We are continuing to investigate this issue.

3. investigating 2025-10-28 10:03 UTC

   We are working on the issue, we can see writes are starting to fail.

4. investigating 2025-10-28 10:44 UTC

   Writes in this cluster has been restored, we are working on further to restore the read issues.

5. investigating 2025-10-28 13:05 UTC

   A fix has been applied and error rates are on decline. We will continue to monitor the issue.

6. investigating 2025-10-28 14:41 UTC

   Services continue to look healthy. We are continuing to monitor for further issues.

7. resolved 2025-10-28 16:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Writes, API Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-28 02:04 UTC

   We are currently investigating performance degradation and high error rates for queries in EU-Central region.

2. investigating 2025-10-28 03:07 UTC

   We are continuing to investigate this issue.

3. investigating 2025-10-28 03:53 UTC

   We are continuing to investigate this issue. Currently, some queries may succeed but writes are now being affected and may fail.

4. resolved 2025-10-28 04:57 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Writes, API Queries

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2025-10-20 18:45 UTC

   While service has been restored, we do see some intermittent latency issues in AWS us-east-1, due to the continuing AWS outage.

2. resolved 2025-10-21 00:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Writes, API Queries

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. monitoring 2025-10-20 10:44 UTC

   We are experiencing intermittent issues with API access in AWS us-east-1 due to upstream provider availability.

2. monitoring 2025-10-20 11:55 UTC

   We are continuing to monitor for any further issues.

3. monitoring 2025-10-20 14:49 UTC

   We are experiencing intermittent issues with API access in AWS us-east-1 due to upstream provider availability.

4. resolved 2025-10-20 15:27 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries, Tasks

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-17 17:20 UTC

   We are investigating an issue causing an increase in TTBR for some IOx queries in AWS us-east-1.

2. monitoring 2025-10-17 17:46 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-10-17 18:56 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries, Tasks

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-15 18:53 UTC

   We are investigating an issue with writes and an increased error rate for SQL queries in the EU-Central-1.

2. investigating 2025-10-15 19:43 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-10-15 20:37 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-10-15 22:05 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-10-03 15:11 UTC

   We are currently seeing issues affecting database queries in the eu-central-1 region of AWS.

2. investigating 2025-10-03 17:14 UTC

   We are continuing to investigate this issue.

3. resolved 2025-10-03 17:15 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-09-24 16:00 UTC

   We are investigating an issue which may cause intermittent 504 responses to some queries.

2. monitoring 2025-09-24 17:10 UTC

   Increased error rates have cleared. We are continuing to monitor.

3. monitoring 2025-09-24 18:10 UTC

   We are continuing to monitor for any further issues.

4. resolved 2025-09-24 19:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Other, Other, Other, Other, Other, Other, Other

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-09-17 23:00 UTC

   We are investigating the issue.

2. investigating 2025-09-17 23:04 UTC

   We are investigating the issue.

3. monitoring 2025-09-18 00:06 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-09-18 01:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Auth0 User Authentication

Failure mode: Login, tokens, certificates or credentials failed. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. identified 2025-09-04 22:30 UTC

   We are currently experiencing issues with the Quartz Signup page. Users may see errors or the page stuck loading. Our engineering team has identified the cause and is working on a fix.

2. resolved 2025-09-04 22:33 UTC

   A fix has been implemented and service to the Quartz Signup page should now be restored.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: The text does not say enough to tell. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

1. investigating 2025-08-01 00:19 UTC

   We are currently investigating this issue.

2. identified 2025-08-01 00:48 UTC

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

3. monitoring 2025-08-01 01:09 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-08-01 01:51 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Writes, API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-07-31 09:53 UTC

   We have identified some FlightSQL errors in Serverless AWS eu-central-1 region for certain customers. Our team has taken some remedial action and is continuing to investigate this. We will provide more updates soon.

2. monitoring 2025-07-31 11:03 UTC

   A fix has been implemented and we are monitoring the results.

3. resolved 2025-07-31 14:02 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Management API

Failure mode: A code release introduced the failure. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

1. investigating 2025-07-10 18:42 UTC

   The Cloud dedicated table management API is currently unavailable impacting the ability to list tables

2. identified 2025-07-10 19:35 UTC

   We believe we have identified the cause of the problem and are implementing a fix to revert. This incident has been updated to reflect that only the ListTables endpoint is impacted.

3. identified 2025-07-10 20:27 UTC

   We have identified a fix and are testing it internally

4. identified 2025-07-10 21:47 UTC

   We have identified a fix and are pushing it out to affected customer clusters

5. monitoring 2025-07-10 22:11 UTC

   We have finished deploying a fix to all affected customer clusters.

6. resolved 2025-07-10 23:21 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries

Failure mode: A zone, region or data center became unavailable. Root cause: The vendor does not say why it happened. Tagged by claude-haiku-5-5 with low confidence (taxonomy v0.2).

Names an upstream provider: AWS.

1. investigating 2025-06-30 10:10 UTC

   We are currently investigating this issue.

2. investigating 2025-06-30 11:11 UTC

   We are continuing to investigate this issue.

3. monitoring 2025-06-30 11:16 UTC

   A fix has been implemented and we are monitoring the results.

4. resolved 2025-06-30 12:53 UTC

   This incident has been resolved.

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: API Queries, Tasks

Failure mode: Exhausted memory, disk, CPU, queues, connection pools or quotas. Root cause: Not enough capacity for the load. Tagged by claude-haiku-5-5 with medium confidence (taxonomy v0.2).

Names an upstream provider: Azure.

1. investigating 2025-06-13 16:13 UTC

   We have observed an elevated query error rate and are investigating.

2. identified 2025-06-13 17:06 UTC

   The issue has been identified and a fix is being put into place.

3. monitoring 2025-06-13 17:39 UTC

   A fix has been implemented and deployed. We are monitoring at this time.

4. monitoring 2025-06-13 19:09 UTC

   We are continuing to closely monitor the health of the query API

5. monitoring 2025-06-13 20:36 UTC

   We are continuing to monitor this region for any further degradation

6. resolved 2025-06-13 22:14 UTC

   This incident has been resolved.

7. 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...

Excerpts are shortened. Read the full incident on InfluxData's status page.

Affected: Web UI, API Writes, API Queries, Tasks

Failure mode: A provider or third-party service this vendor depends on failed. Root cause: A failure at a provider or vendor they depend on. Tagged by claude-haiku-5-5 with high confidence (taxonomy v0.2).

Names an upstream provider: Google Cloud.

1. investigating 2025-06-12 18:37 UTC

   We are currently investigating query availability in GCP regions.

2. investigating 2025-06-12 18:43 UTC

   We are continuing to investigate this issue.

3. investigating 2025-06-12 19:18 UTC

   We are continuing to investigate this issue.

4. identified 2025-06-12 19:26 UTC

   Google Cloud Platform is experiencing a major incident. More details on this incident can be found at https://status.cloud.google.com/

5. identified 2025-06-12 20:19 UTC

   Our team is awaiting recovery of the underlying GCP infrastructure and is prepared to bring all services online upon recovery. More incident related information can be found at https://status.cloud.google.com/

6. identified 2025-06-12 20:49 UTC

   Services are beginning to recover as underlying infrastructure becomes available.

7. monitoring 2025-06-12 20:50 UTC

   A fix has been implemented and we are monitoring the results.

8. resolved 2025-06-12 21:53 UTC

   All GCP services have been recovered.

9. postmortem 2025-06-20 22:33 UTC

   **RCA - Service Outage on June 12, 2025** ‌ **Summary** On June 12, 2025, at 17:51 UTC, Google Cloud Platform \(GCP\) experienced a global outage that disrupted a wide range of cloud services, including core infrastructure on which InfluxDB Cloud relies. As a result, all...

Excerpts are shortened. Read the full incident on InfluxData's status page.