Minor impactResolvedDevOps

LaunchDarkly incident: Observability OpenTelemetry Ingest Delay

LaunchDarkly reported this minor-impact incident on its official status page on Jun 15, 2026, 17:02 UTC. It was resolved after 36 min.

Right now LaunchDarkly is operational. Live LaunchDarkly status →

🔔 Get alerted when LaunchDarkly has issuesFree · email alerts · no credit card
Jun 15, 2026, 17:02 UTC
started
Jun 15, 2026, 17:38 UTC
resolved
36 min
duration
Minor
impact

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.

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