LaunchDarkly outage, 10 July 2026
Web application unavailable and flag delivery evaluations have elevated failure rate
- Started
- Resolved
- 10 Jul 2026, 18:19 UTC (after 39 min)
- Impact
- Critical
- Affected
- Emails and notifications, Feature workflows, Audit log, Experiment management, Past experiment iterations, Authentication, Context processing, Rollout management, Config management, Frontend, Flag targeting, Data Export
Last update from LaunchDarkly
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 re...
Read the full incident on the official LaunchDarkly status page
Is LaunchDarkly down now?
This page is the record of one past incident. For the live status, see Is LaunchDarkly down right now? - it reads the official status page every 2 minutes.