Minor impactResolvedDevOps

LaunchDarkly incident: Delayed processing of Session Replay and Error data

LaunchDarkly reported this minor-impact incident on its official status page on May 16, 2026, 00:03 UTC. It was resolved after 1h 10m.

Right now LaunchDarkly is operational. Live LaunchDarkly status →

🔔 Get alerted when LaunchDarkly has issuesFree · email alerts · no credit card
May 16, 2026, 00:03 UTC
started
May 16, 2026, 01:13 UTC
resolved
1h 10m
duration
Minor
impact

Affected components

  • Observability Data Ingest (Sessions, Errors)
  1. resolvedMay 16, 2026, 01:13 UTC

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

  2. identifiedMay 16, 2026, 00:14 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.

  3. investigatingMay 16, 2026, 00:03 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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in LaunchDarkly's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

How often does LaunchDarkly have incidents?

LaunchDarkly reported 8 incidents in the last 90 days. A typical incident lasted 1h 26m. See LaunchDarkly's uptime and incident history