Minor impactResolvedDevOps

LaunchDarkly incident: Investigating - Known Impact

LaunchDarkly reported this minor-impact incident on its official status page on Jul 31, 2026, 17:44 UTC. It was resolved after 5h 10m.

Right now LaunchDarkly is operational. Live LaunchDarkly status →

🔔 Get alerted when LaunchDarkly has issuesFree · email alerts · no credit card
Jul 31, 2026, 17:44 UTC
started
Jul 31, 2026, 22:54 UTC
resolved
5h 10m
duration
Minor
impact

Affected components

  • OpenTelemetry (Logs, Traces, Metrics)
  1. resolvedJul 31, 2026, 22:54 UTC

    The issue with Observability Traces has been resolved. Missing trace data has been recovered.

  2. monitoringJul 31, 2026, 21:58 UTC

    The issue with Observability Traces has been identified and a fix has been implemented. We have recovered most trace data that was missing from July 30th 5:16pm to July 31st 10:59am PT. We will resolve the incident once we fully complete data recovery (expected to complete by 5pm PT).

  3. identifiedJul 31, 2026, 17:59 UTC

    Customers are experiencing missing Observability Traces ingested from July 30th 5:16pm until July 31st 10:59am PT. Observability Logs / Metrics are unaffected. We have identified the issue and are continuing our work to recover the missing Traces data.

  4. investigatingJul 31, 2026, 17:44 UTC

    All customers are experiencing missing Observability Traces starting July 30th at 5:16pm PT. We are investigating and will provide updates as they become available. Trace data is not lost and we are working to recover it.

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