Vendor reports: partial outageResolved · vendor status “resolved”Official status API

Degraded writes in AWS us-east-1 Serverless Cluster

Reported by InfluxDB Cloud · Databases · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
Nov 5, 2025, 18:17 UTC
Vendor's clock
Resolved
Nov 5, 2025, 21:54 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
3 h 37 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • InfluxDB Cloud reports partial outage: "Degraded writes in AWS us-east-1 Serverless Cluster".[E1, E2]
  • The vendor marked it resolved at 2025-11-05 21:54 UTC.[E3, E7]

Affected products and regions

  • Regions: us-east-1 (read from the title, so inferred).[E5]
  • Components: API Writes.[E6]

What is unknown

  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2025-11-05 21:54 UTC · summary s1, evidence fb96f147f0d3874d

Evidence (7)
  1. E1InfluxDB Cloud reports partial outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Degraded writes in AWS us-east-1 Serverless Cluster". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2025-11-05 18:17 UTC. (vendor) source (opens in a new tab)
  5. E5Regions written in the title (inferred): us-east-1. (Statuswall) source (opens in a new tab)
  6. E6Components the vendor attached: API Writes. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2025-11-05 21:54 UTC. (vendor) source (opens in a new tab)

Affected scope

us-east-1

Components: API Writes

Read from region codes written in the incident title, so treat it as inferred.

Potential relevance

InfluxDB Cloud is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Nov 5, 2025, 18:17 UTCVendor-reported startVendor time
  2. Nov 5, 2025, 21:54 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.