Rewindex

ChangesInfluxData (InfluxDB Cloud)504 gateway errors in us-east-1

InfluxData (InfluxDB Cloud): Critical incident: 504 gateway errors in us-east-1

Major incidentcritical (vendor)Changed Detected stspg.io (opens in new tab)
Summary

Summary pending. The diff below shows exactly what changed.

Incident page: the full timeline of updates

What changed

Struck in red is what InfluxData (InfluxDB Cloud) removed; blue is what they added. Muted text is unchanged context.

AddedTitle#1
Before: not present
After: 504 gateway errors in us-east-1
AddedImpact#2
Before: not present
After: critical
AddedStatus#3
Before: not present
After: resolved
AddedStart time#4
Before: not present
After: 2025-10-28 09:49 UTC
AddedResolved time#5
Before: not present
After: 2025-10-28 16:06 UTC
AddedAffected components#6
Before: not present
After: API Queries, Cloud Serverless: AWS, US-East-1 - API Queries
AddedUpdateinvestigating#7
Before: not present
After: We are seeing degraded performance in the us-east-1 region for queries. The team in continuing to investigate and will keep you updated
AddedUpdateinvestigating#8
Before: not present
After: We are continuing to investigate this issue.
AddedUpdateinvestigating#9
Before: not present
After: We are continuing to investigate this issue.
AddedUpdatemonitoring#10
Before: not present
After: A fix has been applied and error rates are on decline. We will continue to monitor the issue.
AddedUpdatemonitoring#11
Before: not present
After: Services continue to be healthy. We are continuing to monitor for any further issues.
AddedUpdateresolved#12
Before: not present
After: This incident has been resolved.

First version of this incident archived by Rewindex. View the live incident (opens in new tab).

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

Rewindex captured this after the last checkpoint; the next run (00:41 UTC) commits it.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

History of this incident

Tuesday, October 28, 2025

1 incident change

All InfluxData (InfluxDB Cloud) changesInfluxData (InfluxDB Cloud) profileMarkdownJSON