- Level
- confirmed
- Worst impact
- Degraded
- Components
- SDKs
- Regions
- us
- Down Index
- 34of 100
What to do
Check whether you use LaunchDarkly SDKs in us. 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 46m it lasted.
Anything that failed between 2026-08-07 19:29 UTC and 2026-08-07 20:15 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
- investigating
We are investigating elevated HTTP 500 errors affecting some server-side SDK streaming connections in our US commercial environment. Affected applications may fail to establish or may intermittently lose their streaming connection to LaunchDarkly.
provider
- investigating
We released several mitigations and we're noticing that error rates are dropping. We'll continue to monitor the situation.
provider
- investigating
We are continuing to investigate this issue.
provider
- resolved
SDKs restored to operational
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-d7c8b9c956
Is LaunchDarkly still down?
No, this incident was resolved 2026-08-07 20:15 UTC. For LaunchDarkly's live state, see https://down.guide/launchdarkly.
How long did it last?
46m, from 2026-08-07 19:29 UTC to 2026-08-07 20:15 UTC, by the times LaunchDarkly posted.
What was affected?
LaunchDarkly named SDKs in us.
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.