LaunchDarkly incident: Observability Data Delay

Affected components

• Observability Data Ingest (Sessions, Errors)

1. resolvedFeb 19, 2026, 16:09 UTC

   We've caught up on the session/error data backlog.

2. identifiedFeb 19, 2026, 15:54 UTC

   We've identified the root cause and have deployed a fix. We're catching up on the session/error data backlog and should be caught up in ~15 minutes. No data has been lost.

3. investigatingFeb 19, 2026, 15:39 UTC

   Sessions and errors may be delayed by up to 1 hours. We are investigating the root cause. No data is lost.

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.

• Confluence: Disrupted availability of Confluence Cloud in several regionsMajor · Feb 19, 2026, 15:44 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