Skip to main content
LaunchDarkly

Flag Updates via Polling API delayed

Degraded Lasted 5h 26m · started · LaunchDarkly's page

Level
confirmed
Worst impact
Degraded
Components
Polling API
Down Index
35of 100

What to do

  • Check whether you use LaunchDarkly Polling API. 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 5h 26m it lasted.

    Anything that failed between 2026-08-17 10:36 UTC and 2026-08-17 16:03 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. investigating

    We're experiencing a service degradation which can result in Flag updates via the Polling API to be delayed.

    provider

  2. monitoring

    We've identified the root cause, our CDN provider had an issue on their end which is fixed now. Monitoring for a while to make sure things stabilise.

    provider

  3. resolved

    This incident has been resolved.

    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-517851801a

Is LaunchDarkly still down?

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

How long did it last?

5h 26m, from 2026-08-17 10:36 UTC to 2026-08-17 16:03 UTC, by the times LaunchDarkly posted.

What was affected?

LaunchDarkly named Polling API.

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.