Companies / LaunchDarkly / incidents
LaunchDarkly: Web application unavailable and flag delivery evaluations have elevated failure rate
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 archived incident (Sol). Check the timeline before relying on it.
Affected components: Guarded Rollouts (core functionality) - Rollout managementRollout managementGuarded Rollouts (core functionality) - Rollout results analysisRollout results analysisFeature management (core functionality) - Flag targetingFlag targetingObservability (core functionality) - OpenTelemetry (Logs, Traces, Metrics)OpenTelemetry (Logs, Traces, Metrics)Global (core functionality) - MetricsMetricsData ExportFeature management (non-core functionality) - Data ExportExperimentation (core functionality) - Experiment results analysisExperiment results analysisAutomations (non-core functionality) - Emails and notificationsEmails and notificationsObservability (core functionality) - Observability Data Ingest (Sessions, Errors)Observability Data Ingest (Sessions, Errors)Feature management (core functionality) - Release pipelinesRelease pipelinesFeature management (core functionality) - Progressive rolloutsProgressive rolloutsAudit logGlobal (non-core functionality) - Audit logContext processingFeature management (non-core functionality) - Context processingFeature management (core functionality) - Segment managementSegment managementGuarded Rollouts (core functionality) - Rollout results processingRollout results processingAccount managementFeature management (non-core functionality) - Flag usage metricsFlag usage metricsAgents (core functionality) - AI insightsAI insightsAgents (core functionality) - Config managementConfig managementExperimentation (core functionality) - Experiment results processingExperiment results processingAuthenticationGlobal (core functionality) - AuthenticationFrontendObservability (core functionality) - FrontendExperimentation (core functionality) - Experiment managementExperiment managementExperimentation (core functionality) - Warehouse native experimentationWarehouse native experimentationExperimentation (non-core functionality) - Past experiment iterationsPast experiment iterationsAgents (core functionality) - GraphsGraphsObservability (core functionality) - Query APIQuery APIGlobal (core functionality) - Web app (app.launchdarkly.com)Web app (app.launchdarkly.com)Automations (non-core functionality) - Expiring Contexts TargetsExpiring Contexts TargetsFeature management (core functionality) - Feature workflowsFeature workflowsAutomations (non-core functionality) - Integrations and webhooksIntegrations and webhooksAgents (core functionality) - Playgrounds and offline evaluationsPlaygrounds and offline evaluations
Timeline of updates
- 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.
- identified
We have identified the root cause and are implementing a fix.
- 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.
- 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.
- 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.
Rewindex changes for this incident
- Critical incident: Web application unavailable and flag delivery evaluations have elevated failure rate 2026-07-10 17:40 UTC
Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). LaunchDarkly profile · Recent LaunchDarkly incidents · Markdown · JSON