Rewindex

CompaniesLaunchDarklyIncidents

LaunchDarkly: Data Export delayed to Azure Events Hub

MinorStatus: resolvedStarted Resolved (0 min)1 updatestatus.launchdarkly.com (opens in new tab)
Part of an outage event

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

LaunchDarkly’s incident blames Azure as the cause. (hop 1, posted +0 min vs the first vendor naming Azure)

“…Data Export delayed to Azure Events Hub Microsoft Azure DNS experienced an issue earlier today, which resulted in a delay in Data Export publishing events to Azure Events Hub. Microsoft has mitigated…”

Swipe sideways to see the whole diagram.

Azureown incident not archivedWithin an hour4 vendors, 3 blamed AzureLaunchDarkly, InfluxData (InfluxDB Cloud), Confluent, JFrogLaunchDarkly (this incident)posted +0 min
Azureown incident not archivedWithin an hour4 vendors, 3 blamed AzureLaunchDarkly, InfluxData(InfluxDB Cloud), Confluent,JFrogLaunchDarkly (this incident)posted +0 min
LaunchDarkly 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["LaunchDarkly (this incident)<br/>posted +0 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

    Microsoft Azure DNS experienced an issue earlier today, which resulted in a delay in Data Export publishing events to Azure Events Hub. Microsoft has mitigated the Azure DNS issue, and Data Export has resumed publishing events to Azure Events Hub. We observed increased latency in event delivery from 21:30 to 22:01 UTC. All queued events have been delivered, and event publish latency has returned to normal.

From LaunchDarkly’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.launchdarkly.com (opens in new tab).

LaunchDarkly profileRecent LaunchDarkly incidentsMarkdownJSON