Delayed processing of Session Replay and Error data

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 10m it lasted.

  Anything that failed between 2026-05-16 00:03 UTC and 2026-05-16 01:13 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. investigatingMay 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.

   provider

2. identifiedMay 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.

   provider

3. resolvedMay 16, 2026, 1:13 AM UTC

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

   provider

Corrections

None so far.

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