Skip to main content
LaunchDarkly

Delays in event ingestion

Degraded Lasted 4d 1h · started · LaunchDarkly's page

Level
confirmed
Worst impact
Degraded
Components
Data Export, Metrics, Rollout results processing, Flag usage metrics, Experiment results processing, Rollout results analysis, Experiment results analysis, AI insights, Warehouse native experimentation
Down Index
41of 100

What to do

  • Check whether you use LaunchDarkly Data Export, Metrics, Rollout results processing, Flag usage metrics and 5 more. Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 4d 1h it lasted.

    Anything that failed between 2026-06-09 12:08 UTC and 2026-06-13 13:52 UTC may need a replay.
  • Subscribe to LaunchDarkly's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=launchdarkly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from LaunchDarkly 14

  1. identified

    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.

    provider

  2. monitoring

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

    provider

  3. monitoring

    We are monitoring the status of our services.

    provider

  4. monitoring

    We are continuing to monitor for any further issues.

    provider

  5. monitoring

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

    provider

  6. monitoring

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

    provider

  7. monitoring

    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.

    provider

  8. monitoring

    We are continuing to monitor for any further issues.

    provider

  9. monitoring

    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.

    provider

  10. monitoring

    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.

    provider

  11. monitoring

    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.

    provider

  12. monitoring

    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.

    provider

  13. monitoring

    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.

    provider

  14. resolved

    This incident has been resolved.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-b73503c3a2

Is LaunchDarkly still down?

No, this incident was resolved 2026-06-13 13:52 UTC. For LaunchDarkly's live state, see https://down.guide/launchdarkly.

How long did it last?

4d 1h, from 2026-06-09 12:08 UTC to 2026-06-13 13:52 UTC, by the times LaunchDarkly posted.

What was affected?

LaunchDarkly named Data Export, Metrics, Rollout results processing, Flag usage metrics and 5 more.

What caused it?

LaunchDarkly hasn't published a root cause. If it does, it shows here.

Where does this come from?

LaunchDarkly's official status page, https://status.launchdarkly.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.