Skip to main content
LaunchDarkly

Delay in Session Replay and Error ingest

Degraded Lasted 41m · 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 41m it lasted.

    Anything that failed between 2026-07-28 19:24 UTC and 2026-07-28 20:04 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 3

  1. identified

    Customers are experiencing delayed session replay and error ingest as of 11:03am PT. We have identified the issue and are continuing our work to resolve it. Data loss is not expected.

    provider

  2. monitoring

    The issue with session replay and error ingest has been identified and a fix has been implemented. We expect to catch up on all backlogged data ingest in ~15 minutes. No data has been lost.

    provider

  3. resolved

    The issue with session replay and error ingest has been resolved. We've caught up on all backlogged data as of 1:01pm PT.

    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-e0472b95c9

Is LaunchDarkly still down?

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

How long did it last?

41m, from 2026-07-28 19:24 UTC to 2026-07-28 20:04 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.