Minor impactResolvedDevOps

LaunchDarkly incident: Delay in Experimentation Results and Experimentation Warehouse Data Export

LaunchDarkly reported this minor-impact incident on its official status page on May 2, 2026, 12:55 UTC. It was resolved after 6h 21m.

Right now LaunchDarkly is operational. Live LaunchDarkly status →

🔔 Get alerted when LaunchDarkly has issuesFree · email alerts · no credit card
May 2, 2026, 12:55 UTC
started
May 2, 2026, 19:15 UTC
resolved
6h 21m
duration
Minor
impact

Affected components

  • Experiment results processing
  • Warehouse native experimentation
  1. resolvedMay 2, 2026, 19:15 UTC

    Experimentation results processing and data warehouse export was caught up as of 12:28 pm PT.

  2. monitoringMay 2, 2026, 13:51 UTC

    We have implemented a fix and are catching up on backlogged experimentation results and data export. We estimate that we will be fully caught up in about 8 hours.

  3. identifiedMay 2, 2026, 13:17 UTC

    We've identified the root cause of the experimentation results processing and data export delays and are working on implementing a fix.

  4. investigatingMay 2, 2026, 12:55 UTC

    We are investigating an issue causing delayed experimentation results processing and delayed experimentation data warehouse export.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in LaunchDarkly's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does LaunchDarkly have incidents?

LaunchDarkly reported 9 incidents in the last 90 days. A typical incident lasted 1h 15m. See LaunchDarkly's uptime and incident history