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

- Impact (vendor’s label): critical
- Status: resolved
- Started: 2026-07-10 17:40 UTC · Resolved: 2026-07-10 18:19 UTC · Duration: 39 min
- Updates: 5 · Affected components: Guarded Rollouts (core functionality) - Rollout management, Rollout management, Guarded Rollouts (core functionality) - Rollout results analysis, Rollout results analysis, Feature management (core functionality) - Flag targeting, Flag targeting, Observability (core functionality) - OpenTelemetry (Logs, Traces, Metrics), OpenTelemetry (Logs, Traces, Metrics), Global (core functionality) - Metrics, Metrics, Data Export, Feature management (non-core functionality) - Data Export, Experimentation (core functionality) - Experiment results analysis, Experiment results analysis, Automations (non-core functionality) - Emails and notifications, Emails and notifications, Observability (core functionality) - Observability Data Ingest (Sessions, Errors), Observability Data Ingest (Sessions, Errors), Feature management (core functionality) - Release pipelines, Release pipelines, Feature management (core functionality) - Progressive rollouts, Progressive rollouts, Audit log, Global (non-core functionality) - Audit log, Context processing, Feature management (non-core functionality) - Context processing, Feature management (core functionality) - Segment management, Segment management, Guarded Rollouts (core functionality) - Rollout results processing, Rollout results processing, Account management, Feature management (non-core functionality) - Flag usage metrics, Flag usage metrics, Agents (core functionality) - AI insights, AI insights, Agents (core functionality) - Config management, Config management, Experimentation (core functionality) - Experiment results processing, Experiment results processing, Authentication, Global (core functionality) - Authentication, Frontend, Observability (core functionality) - Frontend, Experimentation (core functionality) - Experiment management, Experiment management, Experimentation (core functionality) - Warehouse native experimentation, Warehouse native experimentation, Experimentation (non-core functionality) - Past experiment iterations, Past experiment iterations, Agents (core functionality) - Graphs, Graphs, Observability (core functionality) - Query API, Query API, Global (core functionality) - Web app (app.launchdarkly.com), Web app (app.launchdarkly.com), Automations (non-core functionality) - Expiring Contexts Targets, Expiring Contexts Targets, Feature management (core functionality) - Feature workflows, Feature workflows, Automations (non-core functionality) - Integrations and webhooks, Integrations and webhooks, Agents (core functionality) - Playgrounds and offline evaluations, Playgrounds and offline evaluations
- [Vendor status page: https://stspg.io/3zs2g4y0zjhs](https://stspg.io/3zs2g4y0zjhs)
- [Company: LaunchDarkly](https://rewindex.com/company/launchdarkly.md)

## 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, sol)_
## Timeline of updates

- **investigating** 2026-07-10 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.
- **identified** 2026-07-10 17:12 UTC: We have identified the root cause and are implementing a fix.
- **identified** 2026-07-10 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.
- **monitoring** 2026-07-10 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.
- **resolved** 2026-07-10 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.

## Rewindex changes for this incident

- 2026-07-10 17:40 UTC: [Critical incident: Web application unavailable and flag delivery evaluations have elevated failure rate](https://rewindex.com/change/iaaf37f20947aed.md)


---
Canonical: https://rewindex.com/company/launchdarkly/incidents/chywwz01ptb0 · Markdown: https://rewindex.com/company/launchdarkly/incidents/chywwz01ptb0.md · JSON: https://rewindex.com/api/v1/companies/launchdarkly/incidents/chywwz01ptb0 · Generated 2026-10-18T11:26:50.403Z