Skip to main content
LaunchDarkly

Delayed processing of Session Replay and Error data

Degraded Lasted 1h 3m · started · LaunchDarkly's page

Level
confirmed
Worst impact
Degraded
Components
Observability Data Ingest (Sessions, Errors)
Down Index
31of 100

What to do

  • Check whether you use LaunchDarkly Observability Data Ingest (Sessions, Errors). Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 1h 3m it lasted.

    Anything that failed between 2026-04-06 17:58 UTC and 2026-04-06 19:02 UTC may need a replay.
  • Subscribe to LaunchDarkly's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=launchdarkly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from LaunchDarkly 4

  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.

    provider

  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.

    provider

  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.

    provider

  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.

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-5fd8cbc56f

Is LaunchDarkly still down?

No, this incident was resolved 2026-04-06 19:02 UTC. For LaunchDarkly's live state, see https://down.guide/launchdarkly.

How long did it last?

1h 3m, from 2026-04-06 17:58 UTC to 2026-04-06 19:02 UTC, by the times LaunchDarkly posted.

What was affected?

LaunchDarkly named Observability Data Ingest (Sessions, Errors).

What caused it?

LaunchDarkly hasn't published a root cause. If it does, it shows here.

Where does this come from?

LaunchDarkly's official status page, https://status.launchdarkly.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.