Minor impactResolvedDevOps

LaunchDarkly incident: Delays in event ingestion

LaunchDarkly reported this minor-impact incident on its official status page on Jun 9, 2026, 12:08 UTC. It was resolved after 4d 1h.

Right now LaunchDarkly is operational. Live LaunchDarkly status →

🔔 Get alerted when LaunchDarkly has issuesFree · email alerts · no credit card
Jun 9, 2026, 12:08 UTC
started
Jun 13, 2026, 13:52 UTC
resolved
4d 1h
duration
Minor
impact

Affected components

  • AI insights
  • Data Export
  • Experiment results analysis
  • Experiment results processing
  • Flag usage metrics
  • Metrics
  • Rollout results analysis
  • Rollout results processing
  • Warehouse native experimentation
  1. resolvedJun 13, 2026, 13:52 UTC

    This incident has been resolved.

  2. monitoringJun 12, 2026, 22:15 UTC

    We have made major progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are continuing to monitor and will provide another update when recovery is complete.

  3. monitoringJun 11, 2026, 15:37 UTC

    We have made major progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are continuing to monitor and will provide another update when recovery is complete.

  4. monitoringJun 11, 2026, 05:14 UTC

    We have made partial progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are continuing to monitor and will provide another update when recovery is complete.

  5. monitoringJun 11, 2026, 04:12 UTC

    We have made partial progress. We have identified a brief period of event data loss, and some event-based features may show incomplete data while we continue recovery. We are continuing to monitor.

  6. monitoringJun 11, 2026, 04:07 UTC

    We have made partial progress. We have identified a brief period of event data loss, and some event-based features may show incomplete data while we continue recovery. We are continuing to monitor.

  7. monitoringJun 11, 2026, 04:07 UTC

    We are continuing to monitor for any further issues.

  8. monitoringJun 11, 2026, 01:31 UTC

    We have made partial progress. We have identified a brief period of event data loss, and some event-based features may show incomplete data while we continue recovery. We are continuing to monitor.

  9. monitoringJun 10, 2026, 18:54 UTC

    We have made partial progress. Some features may show data gaps while we complete recovery. We are continuing to monitor.

  10. monitoringJun 9, 2026, 12:08 UTC

    We have made partial progress. Some features may show data gaps while we complete recovery. We are continuing to monitor.

  11. monitoringJun 9, 2026, 02:23 UTC

    We are continuing to monitor for any further issues.

  12. monitoringJun 9, 2026, 02:03 UTC

    We are monitoring the status of our services.

  13. monitoringJun 8, 2026, 21:24 UTC

    A fix has been implemented and we are monitoring the results.

  14. identifiedJun 8, 2026, 20:46 UTC

    We are currently experiencing delays in event ingestion impacting multiple product areas starting at 12:40pm PT. We have identified the issue and are working on a fix. No data has been lost.

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 8 incidents in the last 90 days. A typical incident lasted 1h 26m. See LaunchDarkly's uptime and incident history