- Level
- confirmed
- Worst impact
- Degraded
- Components
- Observability Data Ingest (Sessions, Errors)
- Down Index
- 30of 100
What to do
Check whether you use LaunchDarkly Observability Data Ingest (Sessions, Errors). 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 30m it lasted.
Anything that failed between 2026-02-19 15:39 UTC and 2026-02-19 16:09 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
Sessions and errors may be delayed by up to 1 hours. We are investigating the root cause. No data is lost.
provider
- identified
We've identified the root cause and have deployed a fix. We're catching up on the session/error data backlog and should be caught up in ~15 minutes. No data has been lost.
provider
- resolved
We've caught up on the session/error data backlog.
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-fb1edfa247
Is LaunchDarkly still down?
No, this incident was resolved 2026-02-19 16:09 UTC. For LaunchDarkly's live state, see https://down.guide/launchdarkly.
How long did it last?
30m, from 2026-02-19 15:39 UTC to 2026-02-19 16:09 UTC, by the times LaunchDarkly posted.
What was affected?
LaunchDarkly named Observability Data Ingest (Sessions, Errors).
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.