Companies / LaunchDarkly / incidents

LaunchDarkly: Delayed processing of Session Replay and Error data

Impact: minorStatus: resolvedStarted Resolved (1.1 h)4 updatesSource: stspg.io (opens in new tab)

Affected components: Observability (core functionality) - Observability Data Ingest (Sessions, Errors)Observability Data Ingest (Sessions, Errors)

Timeline of updates

  1. identified

    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

    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

    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

    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.

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). LaunchDarkly profile · Recent LaunchDarkly incidents · Markdown · JSON