# Delays in event ingestion - Provider: [LaunchDarkly](https://down.guide/providers/launchdarkly) - Confidence: Confirmed - Impact: Degraded - lasted 4d 1h - started 2026-06-09 12:08 UTC - Data Export, Metrics, Rollout results processing +6 - id: DWN-b73503c3a2 - Official page: https://stspg.io/x49f0n3lpj8h ## Updates from LaunchDarkly ### 2026-06-08 20:46 UTC: 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. ### 2026-06-08 21:24 UTC: monitoring A fix has been implemented and we are monitoring the results. ### 2026-06-09 02:03 UTC: monitoring We are monitoring the status of our services. ### 2026-06-09 02:23 UTC: monitoring We are continuing to monitor for any further issues. ### 2026-06-09 12:08 UTC: monitoring We have made partial progress. Some features may show data gaps while we complete recovery. We are continuing to monitor. ### 2026-06-10 18:54 UTC: monitoring We have made partial progress. Some features may show data gaps while we complete recovery. We are continuing to monitor. ### 2026-06-11 01:31 UTC: 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. ### 2026-06-11 04:07 UTC: monitoring We are continuing to monitor for any further issues. ### 2026-06-11 04:07 UTC: 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. ### 2026-06-11 04:12 UTC: 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. ### 2026-06-11 05:14 UTC: 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. ### 2026-06-11 15:37 UTC: 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. ### 2026-06-12 22:15 UTC: 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. ### 2026-06-13 13:52 UTC: resolved This incident has been resolved. From the builder: does your app depend on LaunchDarkly? [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=launchdarkly) detects problems in your own logs without hand-written monitors, and you can ask it in plain language which errors mention LaunchDarkly. --- down.guide reads providers' official status pages every minute and adds its own evidence, always labeled. Free, no account. Agents: MCP at https://down.guide/mcp, REST at https://down.guide/api/v1, feeds at https://down.guide/feed. Built by [Sazabi](https://www.sazabi.com/?utm_source=down-guide&utm_medium=markdown&utm_content=DWN-b73503c3a2), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.