Rewindex

CompaniesLaunchDarklyIncidents

LaunchDarkly: Increased error rate in event ingestion

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

AWS outage, Nov 25, 2020 · 28 vendors, 29 incidents

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

Swipe sideways to see the whole diagram.

same windowAWSown incident not archivedWithin an hour1 vendor, 1 blamed AWSPipedream1 to 4 hours later4 vendors, 4 blamed AWSHubSpot, Xero, Lattice, HeapLater2 vendors, 2 blamed AWSConfluent, PipedreamLaunchDarkly (this incident)posted −1 h 26 min
same windowAWSown incident not archivedWithin an hour1 vendor, 1 blamed AWSPipedream1 to 4 hours later4 vendors, 4 blamed AWSHubSpot, Xero, Lattice, HeapLater2 vendors, 2 blamed AWSConfluent, PipedreamLaunchDarkly (this incident)posted −1 h 26 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<br/>own incident not archived"]:::inferred
  h1["Within an hour<br/>1 vendor, 1 blamed AWS<br/>Pipedream"]:::blames
  root --> h1
  h4["1 to 4 hours later<br/>4 vendors, 4 blamed AWS<br/>HubSpot, Xero, Lattice, Heap"]:::blames
  root --> h4
  later["Later<br/>2 vendors, 2 blamed AWS<br/>Confluent, Pipedream"]:::blames
  root --> later
  me["LaunchDarkly (this incident)<br/>posted −1 h 26 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

    All available data has been recovered, and all systems fully operational. Data is permanently incomplete for experimentation and usage metrics for the period between 11/25 5:15AM PT and 11/25 9:23AM PT.

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