Rewindex

CompaniesInfluxData (InfluxDB Cloud)Incidents

InfluxData (InfluxDB Cloud): Azure networking issues Multiple regions affected

MajorStatus: resolvedStarted Resolved (2.3 h)1 updatestatus.influxdata.com (opens in new tab)
Part of an outage event

Azure outage, Jan 25, 2023 · 14 vendors, 14 incidents

InfluxData (InfluxDB Cloud)’s incident blames Azure as the cause. (hop 1, posted +2 h 31 min vs the first vendor naming Azure)

“…Azure networking issues Multiple regions affected Incident has been resolved for any more info please check out https://status.azure.com/en-gb/status…”

Swipe sideways to see the whole diagram.

Azureown incident not archivedWithin an hour1 vendor, 1 blamed AzureMongoDB Atlas1 to 4 hours later3 vendors, 2 blamed AzureGrafana Cloud, Retool, InfluxData (InfluxDB Cloud)InfluxData (InfluxDB Cloud) (this incident)posted +2 h 31 min
Azureown incident not archivedWithin an hour1 vendor, 1 blamed AzureMongoDB Atlas1 to 4 hours later3 vendors, 2 blamed AzureGrafana Cloud, Retool,InfluxData (InfluxDB Cloud)InfluxData (InfluxDB Cloud) (thisincident)posted +2 h 31 min
InfluxData (InfluxDB Cloud) is outlined in red. Groups show up to a few vendors each; the event page lists every incident.
Mermaid source
flowchart LR
  root["Azure<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>1 vendor, 1 blamed Azure<br/>MongoDB Atlas"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>3 vendors, 2 blamed Azure<br/>Grafana Cloud, Retool, InfluxData (InfluxDB Cloud)"]:::blames
  root --> h4
  me["InfluxData (InfluxDB Cloud) (this incident)<br/>posted +2 h 31 min"]:::me
  h4 --- me

Full event: timeline, evidence and all vendors →

Detected automatically from incidents that started together and named the same provider. A link means one vendor’s incident named another, not a confirmed cause.

Timeline of updates

  1. resolved

    Incident has been resolved for any more info please check out https://status.azure.com/en-gb/status

From InfluxData (InfluxDB Cloud)’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

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.

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

Impact, status and times are the vendor’s own, as last archived. View on status.influxdata.com (opens in new tab).

InfluxData (InfluxDB Cloud) profileRecent InfluxData (InfluxDB Cloud) incidentsMarkdownJSON