Changes / LaunchDarkly / Web application unavailable and flag delivery evaluations have elevated failure rate
LaunchDarkly: Critical incident: Web application unavailable and flag delivery evaluations have elevated failure rate
Summary
LaunchDarkly reported a critical incident from 2026-07-10 17:40 UTC to 2026-07-10 18:19 UTC, when it was resolved: app.launchdarkly.com was unavailable and flag-value retrieval had elevated failure rates. Customers using client-side or server-side SDKs should have continued seeing last known flag values where a local cache existed.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Web application unavailable and flag delivery evaluations have elevated failure rate
Before: not present
After: critical
Before: not present
After: resolved
Before: not present
After: 2026-07-10 17:40 UTC
Before: not present
After: 2026-07-10 18:19 UTC
Before: not present
After: Account management, Agents (core functionality) - AI insights, Agents (core functionality) - Config management, Agents (core functionality) - Graphs, Agents (core functionality) - Playgrounds and offline evaluations, AI insights, Audit log, Authentication, Automations (non-core functionality) - Emails and notifications, Automations (non-core functionality) - Expiring Contexts Targets, Automations (non-core functionality) - Integrations and webhooks, Config management, Context processing, Data Export, Emails and notifications, Experimentation (core functionality) - Experiment management, Experimentation (core functionality) - Experiment results analysis, Experimentation (core functionality) - Experiment results processing, Experimentation (core functionality) - Warehouse native experimentation, Experimentation (non-core functionality) - Past experiment iterations, Experiment management, Experiment results analysis, Experiment results processing, Expiring Contexts Targets, Feature management (core functionality) - Feature workflows, Feature management (core functionality) - Flag targeting, Feature management (core functionality) - Progressive rollouts, Feature management (core functionality) - Release pipelines, Feature management (core functionality) - Segment management, Feature management (non-core functionality) - Context processing, Feature management (non-core functionality) - Data Export, Feature management (non-core functionality) - Flag usage metrics, Feature workflows, Flag targeting, Flag usage metrics, Frontend, Global (core functionality) - Authentication, Global (core functionality) - Metrics, Global (core functionality) - Web app (app.launchdarkly.com), Global (non-core functionality) - Audit log, Graphs, Guarded Rollouts (core functionality) - Rollout management, Guarded Rollouts (core functionality) - Rollout results analysis, Guarded Rollouts (core functionality) - Rollout results processing, Integrations and webhooks, Metrics, Observability (core functionality) - Frontend, Observability (core functionality) - Observability Data Ingest (Sessions, Errors), Observability (core functionality) - OpenTelemetry (Logs, Traces, Metrics), Observability (core functionality) - Query API, Observability Data Ingest (Sessions, Errors), OpenTelemetry (Logs, Traces, Metrics), Past experiment iterations, Playgrounds and offline evaluations, Progressive rollouts, Query API, Release pipelines, Rollout management, Rollout results analysis, Rollout results processing, Segment management, Warehouse native experimentation, Web app (app.launchdarkly.com)
Before: not present
After: 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.
Before: not present
After: We have identified the root cause and are implementing a fix.
Before: not present
After: 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.
Before: not present
After: 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.
Before: not present
After: 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.
First version of this incident archived by Rewindex. View the live incident.
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Critical incident: Web application unavailable and flag delivery evaluations have elevated failure rate (this change) LaunchDarkly reported a critical incident from 2026-07-10 17:40 UTC to 2026-07-10 18:19 UTC, when it was resolved: app.launchdarkly.com was unavailable and flag-value retrieval had elevated failure rates. Customers using client-side or server-side SDKs should have continued seeing last known flag values where a local cache existed. | Major incident |
All LaunchDarkly changes → · LaunchDarkly profile · Markdown · JSON