InfluxData had 47 outages in the last 2 years totaling 867h 3m of downtime — averaging 1.9 incidents per month.
There were 47 InfluxData outages since April 27, 2025 totaling 867h 3m of downtime. Each is summarised below — incident details, duration, and resolution information.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
The issue has been identified and a fix is being implemented.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating intermittent query failures affecting queries in AWS eu-central-1.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating this issue.
The issue has been identified and a fix is being implemented.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating elevated ingest failure rates affecting Cloud Serverless in the EU-Central region.
This incident has been resolved.
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.
The issue has been identified and the fix has been implemented. Cloud Dedicated Management API and Admin UI should be accessible now.
Cloud Dedicated Management API and Admin UI access issue has been resolved.
We are aware of the query errors in Azure West Europe and we are currently investigating it.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor and fix any sub issues related to the incident.
This incident has been resolved.
We are experiencing intermittent UI login errors on AWS US-East-1. Queries and writes are not affected. We are addressing the issue.
We are continuing to investigate this issue.
This incident has been resolved.
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.
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.
The issue has been identified and a fix is being implemented.
Our team continues to actively monitor for any issues.
This incident has been resolved.
We are currently investigating an Authentication issue that may impact access to database resources
This incident has been resolved.
We are aware of higher than normal query failures in the eu-central-1 region of AWS and are investigating the issue.
Queries are back to normal levels in eu-central-1 and we are monitoring the cluster.
We are continuing to monitor for any further issues.
This incident has been resolved.
We have implemented a fix and are monitoring the cluster.
This incident has been resolved.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are currently investigating a high number of query errors reported in eu-central-1.
A fix has been implemented and we are monitoring the results.
We are continuing to monitor for any further issues.
This incident has been resolved.
We are currently investigating an increase in query times in the US-EAST-1 and EU-CENTRAL-1 clusters.
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.
The root cause of the incident has been identified, and we are monitoring the clusters as they continue to recover.
The impacted clusters continue to recover, and we are actively monitoring them.
The root cause of the incident has been identified, and we are monitoring the clusters as they continue to recover.
A fix has been implemented and we are monitoring the results.
The underlying issue has been resolved, and our team is continuing to monitor the situation to ensure stability.
This incident has been resolved.
we are investigating reports of a higher rate of query errors than normal in multiple Cloud Dedicated clusters
Query performance is back to normal, but the team is continuing to investigate the issue
We are continuing to investigate this issue.
We are continuing to investigate this issue.
Query error rates have returned to normal levels
We are currently investigating this issue.
We are continuing to investigate this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating an issue in the Serverless UI that is preventing measurements from being displayed in the dropdown list, or queried.
We are continuing to investigate this issue.
We are continuing to investigate this issue.
The issue has been identified and a fix is being implemented.
This incident has been resolved.
We have been made aware of issues with Google OAuth client, we are working with provider to solve the issue.
We are continuing to investigate this issue.
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
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
We are continuing to work on a fix for this issue.
A fix has been implemented and we are monitoring the results.
This incident has been resolved.
We are investigating increased query errors within the region
We are continuing to investigate this issue.
The issue has been identified. We are adding capacity to the cluster, to help clear the backlog more quickly
A fix has been implemented and we are monitoring the results.
This incident has been resolved.