LaunchDarkly incident

Delayed processing of Session Replay and Error data

Minor Resolved View vendor source →

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

Started
May 16, 2026, 12:03 AM UTC
Resolved
May 16, 2026, 01:13 AM UTC
Duration
1h 9m
Detected by Pingoru
May 16, 2026, 12:03 AM UTC

Affected components

Observability Data Ingest (Sessions, Errors)

Update timeline

  1. investigating May 16, 2026, 12:03 AM 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.

  2. identified May 16, 2026, 12:14 AM UTC

    We have identified the issue and a fix is in progress. The backlog is actively decreasing. No data has been lost — all queued events will be processed.

  3. resolved May 16, 2026, 01:13 AM UTC

    All queued events have been processed and data ingestion is operating normally. No data was lost during this incident.