Identified - We have identified the root cause and are implementing a fix.
Jul 10, 2026 - 10:12 PDT
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.
Jul 10, 2026 - 10:10 PDT
As part of our commitment to reliability and security, LaunchDarkly will retire all API versions except 20240415 on December 31, 2026.
After this date, all requests made to retired versions will stop working. To avoid disruption, customers must update integrations and workflows to use version 20240415 before the retirement date.
We previously announced the end of life (EOL) for older versions as of April 30, 2025. They have remained available during a grace period, which will end on December 31, 2026
Upgrading now ensures uninterrupted access and provides immediate improvements in performance and functionality.
We recognize this may be a large undertaking, which is why we are providing extended notice. If you need guidance, please reach out to your account team or contact our support team. Posted on
Aug 25, 2025 - 11:43 PDT
Past Incidents
Jul 10, 2026
Unresolved incidents: Web application unavailable and flag delivery evaluations have elevated failure rate, Launchdarkly UI is down and flag evaluation errors are occuring.
Resolved -
Event ingestion is operating normally. Experimentation results, Guarded Rollouts, and in-product data charts were delayed ~5 min between 7:13–7:53 AM PT. No data was lost. We apologize for any inconvenience.
Jul 7, 08:10 PDT
Resolved -
All error rates have normalized.
Jul 6, 14:21 PDT
Monitoring -
We have rolled out a fix and error rates are returning to normal
Jul 6, 14:09 PDT
Update -
We are continuing to investigate this issue.
Jul 6, 14:08 PDT
Investigating -
At 13:21 Pacific Time, we experienced a high volume of error alerts affecting users' ability to interact with the LaunchDarkly application including logging in and UI / API responsiveness. We quickly identified the root cause relating to flag delivery. We are expecting errors decreasing now.
Jul 6, 15:30 PDT
Resolved -
This incident has been resolved.
Jul 3, 09:06 PDT
Monitoring -
A fix has been implemented and we are monitoring the results.
Jul 3, 08:13 PDT
Investigating -
We are investigating elevated error rates on our event data ingestion endpoints affecting production customers, between approximately 7:00 AM PDT and 7:15 AM PDT. During this window, a portion of feature flag, experimentation, and AI/agent event data may have been rejected or delayed.
Flag delivery and evaluation are not affected. SDKs continue to serve flags normally. Observability ingest is not affected.
Jul 3, 07:29 PDT