LaunchDarkly incident: Observability OpenTelemetry Ingest Delay

Affected components

• OpenTelemetry (Logs, Traces, Metrics)

1. resolvedJun 15, 2026, 17:38 UTC

   The issue with Observability data ingest for OpenTelemetry data has been resolved. Impacted services have returned to normal operation.

2. monitoringJun 15, 2026, 17:33 UTC

   The issue with Observability data ingest for OpenTelemetry data has been identified and a fix has been implemented. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is resolved. Observability signals (errors / logs / traces / OTel metrics) are currently delayed by <1 minutes on average.

3. identifiedJun 15, 2026, 17:02 UTC

   Some customers are experiencing delayed Observability data ingest for OpenTelemetry data. We have identified the issue and are continuing our work to resolve it. Observability signals (errors / logs / traces / OTel metrics) are currently delayed by ~6 minutes on average. Data ingest delays began at 10:02am and are improving as of 10:16am PT.

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.

• Snowflake: INC20000034Critical · Jun 15, 2026, 14:30 UTC
• Elasticsearch: Intermittent Elastic Cloud Serverless Availability Issues in AWS us-east-1Major · Jun 15, 2026, 17:31 UTC
• Akamai: Edge Delivery - HTTP Content Delivery in EuropeMinor · Jun 5, 2026, 16:36 UTC
• LogRocket: Delayed analytics ingestion and alertsMinor · Jun 15, 2026, 15:05 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