Skip to main content
LaunchDarkly

Observability OpenTelemetry Ingest Delay

Degraded Lasted 36m · started · LaunchDarkly's page

Level
confirmed
Worst impact
Degraded
Components
OpenTelemetry (Logs, Traces, Metrics)
Down Index
30of 100

What to do

  • Check whether you use LaunchDarkly OpenTelemetry (Logs, Traces, Metrics). Check your stack

    Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.
  • Confirm your retries, queues and scheduled jobs caught up after the 36m it lasted.

    Anything that failed between 2026-06-15 17:02 UTC and 2026-06-15 17:38 UTC may need a replay.
  • Subscribe to LaunchDarkly's feed to hear about the next one first. RSS feed

    https://down.guide/feed?provider=launchdarkly works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from LaunchDarkly 3

  1. identified

    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.

    provider

  2. monitoring

    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.

    provider

  3. resolved

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

    provider

Reports count in aggregate; nothing about you is shown.

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.

Questions about DWN-62feb84b5e

Is LaunchDarkly still down?

No, this incident was resolved 2026-06-15 17:38 UTC. For LaunchDarkly's live state, see https://down.guide/launchdarkly.

How long did it last?

36m, from 2026-06-15 17:02 UTC to 2026-06-15 17:38 UTC, by the times LaunchDarkly posted.

What was affected?

LaunchDarkly named OpenTelemetry (Logs, Traces, Metrics).

What caused it?

LaunchDarkly hasn't published a root cause. If it does, it shows here.

Where does this come from?

LaunchDarkly's official status page, https://status.launchdarkly.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.