- Level
- confirmed
- Worst impact
- Degraded
- Regions
- eu
What to do
Check whether you use LaunchDarkly in eu. 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 0m it lasted.
Anything that failed between 2026-04-10 04:30 UTC and 2026-04-10 04:30 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 1
- resolved
Between approximately 9:37 PM and 9:46 PM PT on April 9, 2026, some customers using server-side SDKs in the EU region may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly. The issue resolved. No action is required from customers. Server-side SDKs automatically reconnect and recover from transient connectivity issues.
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-32394944e8
Is LaunchDarkly still down?
No, this incident was resolved 2026-04-10 04:30 UTC. For LaunchDarkly's live state, see https://down.guide/launchdarkly.
How long did it last?
0m, from 2026-04-10 04:30 UTC to 2026-04-10 04:30 UTC, by the times LaunchDarkly posted.
What was affected?
LaunchDarkly named in eu.
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.