- Level
- confirmed
- Worst impact
- Degraded
- Down Index
- 34of 100
What to do
Check whether your product depends on LaunchDarkly. 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 4h 33m it lasted.
Anything that failed between 2026-03-03 20:40 UTC and 2026-03-04 01:13 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
- investigating
We're investigating reports of inaccurate usage reporting for some Observability products.
provider
- identified
We've identified the root cause affecting the Observability "Errors" usage for some customers and are working to correct it.
provider
- resolved
We've corrected the issues affecting the Observability "Errors" usage reporting for February and are finalizing reporting corrections for March.
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-0f9fe476ba
Is LaunchDarkly still down?
No, this incident was resolved 2026-03-04 01:13 UTC. For LaunchDarkly's live state, see https://down.guide/launchdarkly.
How long did it last?
4h 33m, from 2026-03-03 20:40 UTC to 2026-03-04 01:13 UTC, by the times LaunchDarkly posted.
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.