Minor impactResolvedDevOps

LaunchDarkly incident: Delay in Session Replay and Error ingest

LaunchDarkly reported this minor-impact incident on its official status page on Jul 28, 2026, 19:24 UTC. It was resolved after 41 min.

Right now LaunchDarkly is operational. Live LaunchDarkly status →

🔔 Get alerted when LaunchDarkly has issuesFree · email alerts · no credit card
Jul 28, 2026, 19:24 UTC
started
Jul 28, 2026, 20:04 UTC
resolved
41 min
duration
Minor
impact

Affected components

  • Observability Data Ingest (Sessions, Errors)
  1. resolvedJul 28, 2026, 20:04 UTC

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

  2. monitoringJul 28, 2026, 19:41 UTC

    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.

  3. identifiedJul 28, 2026, 19:24 UTC

    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.

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

LaunchDarkly incident on Jul 28, 2026: Delay in Session Replay and Error ingest · APIStatus.watch