← Live dashboard

Delayed processing of Session Replay and Error data

ResolvedminorOfficial source confirmedSpecific component onlyFirst recorded update Apr 6, 2026, 05:58 PM · Resolved Apr 6, 2026, 07:02 PM

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.

LaunchDarkly live status →

Free for 3 services · Pro adds recovery alertsAdd to Chrome

What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with LaunchDarkly now? Check the current status

Affected services

Observability Data Ingest (Sessions, Errors)

Updates (4)

  1. Apr 6, 2026, 07:02 PM
    Delayed processing of Session Replay and Error data

    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.

    LaunchDarkly ↗
  2. Apr 6, 2026, 06:40 PM
    Delayed processing of Session Replay and Error data

    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.

    LaunchDarkly ↗
  3. Apr 6, 2026, 06:15 PM
    Delayed processing of Session Replay and Error data

    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.

    LaunchDarkly ↗
  4. Apr 6, 2026, 05:58 PM
    Delayed processing of Session Replay and Error data

    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.

    LaunchDarkly ↗

What to do next

  • Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
  • Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
  • Watch the provider going forward. Follow LaunchDarkly's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.