Some data from February 9 2026 and earlier is unavailable in query responses

Major Impact Identified Ongoing February 10, 2026

Incident Lifecycle

Investigating Identified Identified Identified Identified Identified Identified Identified Identified Identified Identified Identified Identified Identified Identified Identified Identified Identified Identified
Affected Components
Web UI API Queries

Incident Timeline

Identified
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 service availability of the cluster. After we have resolved this issue, we will be revisiting our backup/restore strategy to improve the performance of cluster-wide restorations.  For this particular restoration, w...
Feb 20, 2026 at 11:41 PM UTC
Identified
Our team continues to actively work to restore data for all affected users.
Feb 19, 2026 at 5:07 PM UTC
Identified
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.
Feb 18, 2026 at 4:18 PM UTC
Identified
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 until data restoration is complete. We sincerely apologize for the continued impact.
Feb 14, 2026 at 12:08 AM UTC
Identified
Our team continues to actively work to restore data for all affected users.
Feb 13, 2026 at 1:43 AM UTC
Identified
Our team continues to actively work to restore data for all affected users.
Feb 12, 2026 at 10:49 AM UTC
Identified
Our team continues to actively work to restore data for all affected users.
Feb 12, 2026 at 7:46 AM UTC
Identified
Our team continues to actively work to restore data for all affected users.
Feb 12, 2026 at 1:29 AM UTC
Identified
Our team continues to actively work to restore data for all affected users.
Feb 11, 2026 at 6:57 PM UTC
Identified
Our team continues to actively work to restore data for all affected users.
Feb 11, 2026 at 4:36 PM UTC
Identified
Our team is actively working to restore data for affected users.
Feb 11, 2026 at 10:11 AM UTC
Identified
Our team has identified the issue and is actively working to restore data for affected users.
Feb 11, 2026 at 7:32 AM UTC
Identified
Our team has identified the issue and is actively working to restore data for affected users.
Feb 11, 2026 at 4:46 AM UTC
Identified
Our team has identified the issue and is actively working to restore data for affected users.
Feb 11, 2026 at 1:37 AM UTC
Identified
We are continuing to work on the fix for this issue.
Feb 10, 2026 at 10:54 PM UTC
Identified
We are continuing to work on the fix for this issue.
Feb 10, 2026 at 9:40 PM UTC
Identified
We are continuing to work on the fix for this issue.
Feb 10, 2026 at 7:21 PM UTC
Identified
The issue has been identified and a fix is being implemented.
Feb 10, 2026 at 6:12 PM UTC
Investigating
We are investigating an issue related to queries. Some recent data is not showing up on query responses
Feb 10, 2026 at 5:37 PM UTC
Was your business affected by this InfluxData outage?
Set up instant alerts for InfluxData — be the first to know about outages via email, Slack, Teams, or Discord.