LaunchDarkly incident

Delays in event ingestion

Minor Resolved View vendor source →

LaunchDarkly experienced a minor incident on June 9, 2026 affecting Data Export and Metrics and 1 more component, lasting 4d 1h. The incident has been resolved; the full update timeline is below.

Started
Jun 09, 2026, 12:08 PM UTC
Resolved
Jun 13, 2026, 01:52 PM UTC
Duration
4d 1h
Detected by Pingoru
Jun 09, 2026, 12:08 PM UTC

Affected components

Data ExportMetricsRollout results processingFlag usage metricsExperiment results processingRollout results analysisExperiment results analysisWarehouse native experimentationAI insights

Update timeline

  1. identified Jun 08, 2026, 08:46 PM 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.

  2. monitoring Jun 08, 2026, 09:24 PM UTC

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

  3. monitoring Jun 09, 2026, 02:03 AM UTC

    We are monitoring the status of our services.

  4. monitoring Jun 09, 2026, 02:23 AM UTC

    We are continuing to monitor for any further issues.

  5. monitoring Jun 09, 2026, 12:08 PM UTC

    We are continuing to monitor for any further issues.

  6. monitoring Jun 10, 2026, 06:54 PM UTC

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

  7. monitoring Jun 11, 2026, 01:31 AM 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.

  8. monitoring Jun 11, 2026, 04:07 AM UTC

    We are continuing to monitor for any further issues.

  9. monitoring Jun 11, 2026, 04:07 AM 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.

  10. monitoring Jun 11, 2026, 04:12 AM 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.

  11. monitoring Jun 11, 2026, 05:14 AM 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.

  12. monitoring Jun 11, 2026, 03:37 PM 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.

  13. monitoring Jun 12, 2026, 10:15 PM 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.

  14. resolved Jun 13, 2026, 01:52 PM UTC

    This incident has been resolved.