LaunchDarkly outage: Web application unavailable and flag delivery evaluations have elevated failure rate

Affected components

• AI insights
• Account management
• Audit log
• Authentication
• Config management
• Context processing
• Data Export
• Emails and notifications
• Experiment management
• Experiment results analysis
• Experiment results processing
• Expiring Contexts Targets
• Feature workflows
• Flag targeting
• Flag usage metrics
• Frontend
• Graphs
• Integrations and webhooks
• Metrics
• Observability Data Ingest (Sessions, Errors)
• OpenTelemetry (Logs, Traces, Metrics)
• Past experiment iterations
• Playgrounds and offline evaluations
• Progressive rollouts
• Query API

1. resolvedJul 10, 2026, 18:19 UTC

   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.

2. monitoringJul 10, 2026, 17:54 UTC

   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.

3. identifiedJul 10, 2026, 17:40 UTC

   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.

4. identifiedJul 10, 2026, 17:12 UTC

   We have identified the root cause and are implementing a fix.

5. investigatingJul 10, 2026, 17:10 UTC

   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.

What APIStatus.watch saw

Our 5-minute checks didn't record a change in LaunchDarkly's overall status around this incident. Smaller or regional incidents often leave a provider's overall status green.

Other services with incidents at the same time

Overlapping incidents aren't necessarily related.

• Plaid: Service Disruption Impacting Wells Fargo connectionsMajor · Jul 10, 2026, 16:04 UTC
• Discord: Issues with billing operationsMajor · Jul 10, 2026, 16:49 UTC
• Inngest: Issues Affecting Function Triggering from EventsMajor · Jul 10, 2026, 17:44 UTC
• Mailgun: Mailgun Control Panel Unavailable For Some UsersMajor · Jul 10, 2026, 18:07 UTC
• DigitalOcean: Kubernetes Deployments in NYC1Minor · Jul 9, 2026, 20:31 UTC
• Snyk: Snyk Partial Test DegradationMinor · Jul 10, 2026, 13:41 UTC
• Plaid: Elevated Item add errorsMinor · Jul 10, 2026, 16:51 UTC

How often does LaunchDarkly have incidents?

LaunchDarkly reported 15 incidents in the last 90 days, 2 of them major or critical. A typical incident lasted 1h 19m. See LaunchDarkly's uptime and incident history