LaunchDarkly incident
Delayed processing of Session Replay and Error data
Affected components
Update timeline
- identified Apr 06, 2026, 05:58 PM UTC
We are currently experiencing a delay in processing Session Replay and Error event data. Incoming data is being queued and will be processed — no data has been lost. Customers may observe a temporary lag in session and error data appearing in the LaunchDarkly UI. We have identified the root cause as elevated database utilization and are actively working to resolve the backlog. We will provide updates as processing returns to normal.
- identified Apr 06, 2026, 06:15 PM UTC
We have identified the cause of the delayed Session Replay and Error event processing and a fix is in progress. The backlog is actively decreasing. No data has been lost — all queued events will be processed.
- monitoring Apr 06, 2026, 06:40 PM UTC
The delayed processing of Session Replay and Error event data has been resolved. All queued events have been processed and data ingestion is operating normally. No data was lost during this incident. Thank you for your patience.
- resolved Apr 06, 2026, 07:02 PM UTC
The delayed processing of Session Replay and Error event data has been resolved. All queued events have been processed and data ingestion is operating normally. No data was lost during this incident. Thank you for your patience.
Looking to track LaunchDarkly downtime and outages?
Pingoru polls LaunchDarkly's status page every 5 minutes and alerts you the moment it reports an issue — before your customers do.
- Real-time alerts when LaunchDarkly reports an incident
- Email, Slack, Discord, Microsoft Teams, and webhook notifications
- Track LaunchDarkly alongside 5,000+ providers in one dashboard
- Component-level filtering
- Notification groups + maintenance calendar
5 free monitors · No credit card required