LaunchDarkly incident

Delayed processing of Session Replay and Error data

Minor Resolved View vendor source →

LaunchDarkly experienced a minor incident on April 6, 2026 affecting Observability Data Ingest (Sessions, Errors), lasting 1h 3m. The incident has been resolved; the full update timeline is below.

Started
Apr 06, 2026, 05:58 PM UTC
Resolved
Apr 06, 2026, 07:02 PM UTC
Duration
1h 3m
Detected by Pingoru
Apr 06, 2026, 05:58 PM UTC

Affected components

Observability Data Ingest (Sessions, Errors)

Update timeline

  1. 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.

  2. 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.

  3. 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.

  4. 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.