- Level
- confirmed
- Worst impact
- Major outage
- Components
- Emails and notifications, Feature workflows, Audit log, Experiment management, Past experiment iterations, Authentication, Context processing, Rollout management, Config management, Frontend, Flag targeting, Data Export, Integrations and webhooks, Metrics, Rollout results processing, Query API, Graphs, Flag usage metrics, Experiment results processing, Expiring Contexts Targets, Web app (app.launchdarkly.com), Segment management, Rollout results analysis, Observability Data Ingest (Sessions, Errors), Playgrounds and offline evaluations, Experiment results analysis, Progressive rollouts, OpenTelemetry (Logs, Traces, Metrics), AI insights, Release pipelines, Warehouse native experimentation, Account management
- Down Index
- 67of 100
What to do
Check whether you use LaunchDarkly Emails and notifications, Feature workflows, Audit log, Experiment management and 28 more. 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 39m it lasted.
Anything that failed between 2026-07-10 17:40 UTC and 2026-07-10 18:19 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 5
- investigating
The LaunchDarkly web application (app.launchdarkly.com) was unavailable and is actively recovering at the moment. The Flag Delivery network was also impacted, causing an elevated failure rate with retrieving flag values. Customers using client-side or server-side SDKs should continue to see the last known flag values if a local cache exists, or fall back to in-code values. Customers using our Relay Proxy should continue to see last known flag values if a local cache exists. Customers using our Edge SDKs should continue to see last known flag values. Some event data loss may have occurred.
provider
- identified
We have identified the root cause and are implementing a fix.
provider
- identified
The web application availability has recovered. Flag delivery and event ingestion continue to be impacted and are actively recovering. Our engineering team continues to work on remediation.
provider
- monitoring
Production service impact has been restored. However, customers might need to restart their applications to fully reconnect to LaunchDarkly's services. Our engineering team is working on guidance that can be provided to customers.
provider
- resolved
All service availability has been fully restored. Customers using server-side SDKs might need to restart their applications to re-enable the SDKs' connection to LaunchDarkly. Customers using the Relay Proxy may also need to restart their Relay Proxy; in this case, the Relay Proxy should be restarted before restarting their applications that connect to it. To determine if an application needs to be restarted, customers can look at their application logs. Affected SDKs will emit (depending on language) logs containing one of "giving up permanently", "Invalid SDK key", "unauthorized", or "not authorized", or "401". Services which emitted logs such as these before 9:13AM PT may be unable to receive flag updates and will be unable to send events to LaunchDarkly until they are restarted.
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-ee49c00169
Is LaunchDarkly still down?
No, this incident was resolved 2026-07-10 18:19 UTC. For LaunchDarkly's live state, see https://down.guide/launchdarkly.
How long did it last?
39m, from 2026-07-10 17:40 UTC to 2026-07-10 18:19 UTC, by the times LaunchDarkly posted.
What was affected?
LaunchDarkly named Emails and notifications, Feature workflows, Audit log, Experiment management and 28 more.
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.