Rewindex

CompaniesLaunchDarklyIncidents

LaunchDarkly: Delays in webhooks and numeric experimentation results

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

AWS us-east-1 outage, Dec 22, 2021 · 40 vendors, 40 incidents

LaunchDarkly’s incident started in the same window without naming AWS (timing only, not evidence of a link). (hop 1, posted +18 min vs the first vendor naming AWS)

Swipe sideways to see the whole diagram.

same windowAWS us-east-1own incident not archivedWithin an hour8 vendors, 6 blamed AWSFirebolt, Bitbucket, HubSpot, CircleCI +41 to 4 hours later1 vendorConfluentLaunchDarkly (this incident)posted +18 min
same windowAWS us-east-1own incident not archivedWithin an hour8 vendors, 6 blamed AWSFirebolt, Bitbucket, HubSpot,CircleCI +41 to 4 hours later1 vendorConfluentLaunchDarkly (this incident)posted +18 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["AWS us-east-1<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>8 vendors, 6 blamed AWS<br/>Firebolt, Bitbucket, HubSpot, CircleCI +4"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>1 vendor<br/>Confluent"]:::names
  root --> h4
  me["LaunchDarkly (this incident)<br/>posted +18 min"]:::me
  root -.->|"same window"| 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

    Due to an outage in an upstream provider, we had minor disruptions to a few services. A small percent of webhooks were delayed for up to 30 minutes between 12:30 and 13:00 UTC. All webhooks have now been delivered. Experimentation events for numeric metrics are experiencing delays as the system catches up to the backlog of events. No data loss is expected.

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

LaunchDarkly profileRecent LaunchDarkly incidentsMarkdownJSON