What visitors reported during this incident

No visitor reports were filed for this incident.

Having problems with LaunchDarkly now? Check the current status

Affected services

OpenTelemetry (Logs, Traces, Metrics)Observability Data Ingest (Sessions, Errors)Emails and notificationsAuthenticationMetricsFlag usage metricsRollout results analysisFeature workflowsFlag targetingIntegrations and webhooksQuery APIGraphsExperiment results analysisProgressive rolloutsAI insightsWarehouse native experimentationAudit logExperiment managementRollout managementConfig managementData ExportRollout results processingWeb app (app.launchdarkly.com)Past experiment iterationsContext processingExpiring Contexts TargetsPlaygrounds and offline evaluationsRelease pipelinesFrontendExperiment results processingSegment managementAccount management

Updates (5)

Jul 10, 2026, 06:19 PM
Web application unavailable and flag delivery evaluations have elevated failure rate
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 a
LaunchDarkly ↗
Jul 10, 2026, 05:54 PM
Web application unavailable and flag delivery evaluations have elevated failure rate
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.
LaunchDarkly ↗
Jul 10, 2026, 05:40 PM
Web application unavailable and flag delivery evaluations have elevated failure rate
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.
LaunchDarkly ↗
Jul 10, 2026, 05:12 PM
Web application unavailable and flag delivery evaluations have elevated failure rate
We have identified the root cause and are implementing a fix.
LaunchDarkly ↗
Jul 10, 2026, 05:10 PM
Web application unavailable and flag delivery evaluations have elevated failure rate
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.
LaunchDarkly ↗

What to do next

Verify your own services recovered cleanly. Some upstream outages leave queues or caches in a degraded state, run smoke tests before declaring green internally.
Save the post-mortem. Vendors usually publish a detailed RCA 1-3 days later. We'll add it to this page when it appears.
Watch the provider going forward. Follow LaunchDarkly's status feed →

GlobalOutageMap aggregates publicly reported signals. We never claim authoritative status, always cross-check the provider's official channel before making business decisions.