- Level
- confirmed
- Worst impact
- Degraded
- Components
- Client-side streaming API
- Regions
- us, us-east-1
What to do
Check whether you use LaunchDarkly Client-side streaming API in us, us-east-1. 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 2h it lasted.
Anything that failed between 2026-08-14 14:47 UTC and 2026-08-14 16:47 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
Flag Updates are currently delayed in the us-east-1 region. We are investigating the issue.
provider
- monitoring
We investigated elevated error rates reported for mobile SDK flag delivery in US East. We've confirmed that flag delivery itself was not impacted. No customer action is required and we are monitoring the situation.
provider
- resolved
The issue is being marked as resolved. We're seeing improved latencies and our systems have recovered.
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-846cade0f3
Is LaunchDarkly still down?
No, this incident was resolved 2026-08-14 16:47 UTC. For LaunchDarkly's live state, see https://down.guide/launchdarkly.
How long did it last?
2h, from 2026-08-14 14:47 UTC to 2026-08-14 16:47 UTC, by the times LaunchDarkly posted.
What was affected?
LaunchDarkly named Client-side streaming API in us, us-east-1.
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.