LaunchDarkly incident: Delayed processing of Session Replay and Error data

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.

• Confluent Cloud: Elevated error rates and latency on produce and consume operations on AWS us-east-1 AZ4Major · May 8, 2026, 01:14 UTC
• Linode: [DirtyFrag] Linux Privilege Escalation VulnerabilityMinor · May 8, 2026, 13:40 UTC
• Linode: [Fragnesia] Linux Privilege Escalation VulnerabilityMinor · May 13, 2026, 21:02 UTC
• Mixpanel: Query API degraded performanceMinor · May 14, 2026, 23:17 UTC
• LiveKit: Intermittent connectivity disruptions in US regionsMinor · May 15, 2026, 16:57 UTC

How often does LaunchDarkly have incidents?

LaunchDarkly reported 15 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 1h 19m. See LaunchDarkly's uptime and incident history