Rewindex

CompaniesInfluxData (InfluxDB Cloud)Incidents

InfluxData (InfluxDB Cloud): Azure -- DNS instability

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

Azure outage, Apr 1, 2021 · 13 vendors, 13 incidents

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

“…Azure -- DNS instability This incident has been resolved.…”

Swipe sideways to see the whole diagram.

Azureown incident not archivedWithin an hour4 vendors, 3 blamed AzureLaunchDarkly, InfluxData (InfluxDB Cloud), Confluent,JFrogInfluxData (InfluxDB Cloud) (this incident)posted +16 min
Azureown incident not archivedWithin an hour4 vendors, 3 blamed AzureLaunchDarkly, InfluxData(InfluxDB Cloud), Confluent,JFrogInfluxData (InfluxDB Cloud) (thisincident)posted +16 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/>4 vendors, 3 blamed Azure<br/>LaunchDarkly, InfluxData (InfluxDB Cloud), Confluent, JFrog"]:::blames
  root --> h1
  me["InfluxData (InfluxDB Cloud) (this incident)<br/>posted +16 min"]:::me
  h1 --- 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

    This incident has been resolved.

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

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