LaunchDarkly incident: Observability – Degraded OTel Telemetry Processing

Affected components

• OpenTelemetry (Logs, Traces, Metrics)

1. resolvedFeb 12, 2026, 03:53 UTC

   This incident has been resolved. Telemetry data was dropped between 5:03 PM and 7:30 PM PT. All systems are now operating normally.

2. investigatingFeb 11, 2026, 13:03 UTC

   We are currently investigating an issue affecting OTel telemetry ingestion in LaunchDarkly Observability. Some telemetry data may not be processed as expected. Our team is actively working to identify the root cause and mitigate impact.

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.

• Render: Some deploys may be slow or hangingMajor · Feb 11, 2026, 16:16 UTC
• Confluent Cloud: All new cluster creations in Azure westus3, southcentralus, and eastus2 are failingMajor · Feb 11, 2026, 22:14 UTC
• Datadog: Delayed Traces in APM Trace SearchMinor · Feb 11, 2026, 20:56 UTC
• Datadog: Delayed Traces in APMMinor · Feb 12, 2026, 00: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