InfluxData incident

Outage in AWS eu-central-1 - visibility to tasks

Minor Resolved View vendor source →

InfluxData experienced a minor incident on January 9, 2026 affecting Web UI and API Writes and 1 more component, lasting 4d 5h. The incident has been resolved; the full update timeline is below.

Started
Jan 09, 2026, 10:41 AM UTC
Resolved
Jan 13, 2026, 03:55 PM UTC
Duration
4d 5h
Detected by Pingoru
Jan 09, 2026, 10:41 AM UTC

Affected components

Web UIAPI WritesAPI QueriesTasks

Update timeline

  1. investigating Jan 09, 2026, 10:41 AM UTC

    We are currently investigating this issue.

  2. investigating Jan 09, 2026, 12:48 PM UTC

    We are continuing to investigate this issue.

  3. investigating Jan 09, 2026, 02:10 PM UTC

    We are continuing to investigate the issue

  4. investigating Jan 09, 2026, 03:43 PM UTC

    We are continuing to investigate this issue.

  5. investigating Jan 09, 2026, 05:16 PM 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 Jan 09, 2026, 06:59 PM 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 Jan 09, 2026, 10:21 PM UTC

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

  8. identified Jan 09, 2026, 11:52 PM 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 Jan 10, 2026, 02:43 AM UTC

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

  10. monitoring Jan 10, 2026, 10:19 AM UTC

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

  11. resolved Jan 13, 2026, 03:55 PM UTC

    This incident has been resolved.