InfluxData (InfluxDB Cloud)

First posted only after it was over

0% 0 of the 50 incidents we have in full detailbetterworse

The first update already said resolved. Typical vendor: 6%.

InfluxData (InfluxDB Cloud): lower than most vendors.

Time to resolve

4 h 33 min median; 9 in 10 within 24 h 33 minbetterworse

From the vendor’s own start and resolve times, last 365 days. Typical vendor: 2 h.

InfluxData (InfluxDB Cloud): higher than most vendors.

Major or critical incidents

1.3 a month 16 in the last 365 daysbetterworse

Impact as the vendor labels it. Typical vendor: 1.2 a month.

InfluxData (InfluxDB Cloud): around the middle.

Rewrites caught

None so far

Counts, not a rate: 10-minute tracking began Oct 17, so there are too few events to compare yet.

InfluxData (InfluxDB Cloud) depends on

Runs in (named in its incidents): AWS eu-central-1 (37), AWS us-east-1 (30), AWS us-west-2 (19), Microsoft Azure west europe (8), AWS us-central-1 (3), AWS eu-west-1 (3), Google Cloud us-central1 (3).

Outage events: AWS us-east-1, Oct 20, 2025, Google Cloud, Jun 12, 2025, Microsoft Azure, Jan 25, 2023, AWS us-east-1, Dec 22, 2021 (timing), AWS, Dec 15, 2021, Auth0, Apr 20, 2021 (timing), Microsoft Azure, Apr 1, 2021.

Strong: same company, or blamed in two separate outages. Likely: blamed once, or named as hosting and failing together. Weak: listed as a subprocessor, integration-only, or failing together repeatedly without being named.

Full InfluxData (InfluxDB Cloud) change history

No pricing, trust or legal pages tracked for InfluxData (InfluxDB Cloud).

Each change links to its diff: the changed passages with a few words of context, never a full copy of the page.

InfluxData (InfluxDB Cloud) incidents, last 90 daysJSONMarkdown