- Level
- confirmed
- Worst impact
- Degraded
- Components
- Data Export
- Down Index
- 31of 100
What to do
Check whether you use LaunchDarkly Data Export. 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 44m it lasted.
Anything that failed between 2026-04-30 11:14 UTC and 2026-04-30 11:58 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 are investigating a delay with streaming data export delivery. No data is lost, but customers using streaming data export may notice a multi-minute lag in receiving data.
provider
- monitoring
We've identified latency in Pub/Sub export that were causing streaming data export delays that has since resolved. We're catching up on the export backlog now.
provider
- resolved
We've caught up on the streaming data export 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-f3878788a9
Is LaunchDarkly still down?
No, this incident was resolved 2026-04-30 11:58 UTC. For LaunchDarkly's live state, see https://down.guide/launchdarkly.
How long did it last?
44m, from 2026-04-30 11:14 UTC to 2026-04-30 11:58 UTC, by the times LaunchDarkly posted.
What was affected?
LaunchDarkly named Data Export.
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.