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

Outage of Cloud Dedicated Management API and Admin UI

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

Official source (opens in a new tab)
Vendor start
Feb 18, 2026, 23:23 UTC
Vendor's clock
Resolved
Feb 19, 2026, 00:10 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
47 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 major outage: "Outage of Cloud Dedicated Management API and Admin UI".[E1, E2]
  • The vendor marked it resolved at 2026-02-19 00:10 UTC.[E3, E7]

Affected products and regions

  • Components: Management API.[E6]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-02-19 00:10 UTC · summary s1, evidence fe8a01639808cc3c

Evidence (7)
  1. E1InfluxDB Cloud reports major outage. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Outage of Cloud Dedicated Management API and Admin UI". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-02-18 23:23 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6Components the vendor attached: Management API. (vendor) source (opens in a new tab)
  7. E7Vendor-reported resolution: 2026-02-19 00:10 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: Management API

The vendor's feed gives no region for this incident. It is not assumed to be global.

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. Feb 18, 2026, 23:23 UTCVendor-reported startVendor time
  2. Feb 19, 2026, 00:10 UTCVendor-reported resolutionVendor time

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