LaunchDarkly incident

Observability OpenTelemetry Ingest Delay

Resolved after 36 minutes, affecting OpenTelemetry (Logs, Traces, Metrics), on June 15, 2026.

resolved Jun 15, 2026, 05:38 PM UTC

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

Started
Jun 15, 2026, 05:02 PM UTC
Resolved
Jun 15, 2026, 05:38 PM UTC
Duration
36m
Detected by Pingoru
Jun 15, 2026, 05:02 PM UTC

Affected components

OpenTelemetry (Logs, Traces, Metrics)

Update timeline

  1. identified Jun 15, 2026, 05:02 PM 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.

  2. monitoring Jun 15, 2026, 05:33 PM 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. resolved Jun 15, 2026, 05:38 PM UTC

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

Your product runs on more than LaunchDarkly

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →