Skip to main content
LaunchDarkly

Degraded Observability Ingest

Degraded Lasted 1h 1m · started · LaunchDarkly's page

Level
confirmed
Worst impact
Degraded
Components
OpenTelemetry (Logs, Traces, Metrics)
Down Index
31of 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 1h 1m it lasted.

    Anything that failed between 2026-02-20 22:02 UTC and 2026-02-20 23:04 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 4

  1. investigating

    Beginning around 1:25 PM PST, we are investigating degraded ingest performance. Some customers may experience delays or gaps in observability data. Updates to follow.

    provider

  2. identified

    We have identified the cause of the degraded ingest performance and are applying mitigation. We are seeing signs of stabilization and continuing to monitor recovery.

    provider

  3. monitoring

    Mitigation has been applied and ingest performance has stabilized. We are monitoring to ensure continued stability.

    provider

  4. resolved

    Ingest performance has remained stable following mitigation. We are no longer observing impact.

    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-6c2c1f43b9

Is LaunchDarkly still down?

No, this incident was resolved 2026-02-20 23:04 UTC. For LaunchDarkly's live state, see https://down.guide/launchdarkly.

How long did it last?

1h 1m, from 2026-02-20 22:02 UTC to 2026-02-20 23:04 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.