Looking for an update now? Check the current status, or follow LaunchDarkly for future changes.
98.3%of 58 verified observed days had no reported provider issue
90-Day Trend
Dashed calendar markers below identify legacy observations whose source-at-observation was not recorded.
Monthly Status Summary
Month
Issue-free days
Days Tracked
Days with issues
September 2026
100%
30
0
This percentage summarizes normalized provider-status observations by calendar day. It is not duration-based, component-weighted, or contractual uptime. See the methodology and limitations.
Recorded Daily Status (Last 91 Days)
Jul 23Today
Legacy observation Operational Degraded Partial Outage Major Outage Maintenance No Data
Incident History
October 2026
Delays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation
The backlog of delayed changes has been fully processed as of 1:45 AM PT on October 3. All changes that were delayed during the incident have been applied. No data was lost. We are continuing to monitor.
identified
Some automatic changes in LaunchDarkly are being applied later than expected. This affects stage transitions for guarded and progressive rollouts, release pipeline phase progression, and multi-armed bandit traffic reallocations. Delays began at approximately 4:15 PM PT on October 2 2026.
In-progress rollouts and experiments remain at their current stage and traffic allocation; nothing has been advanced, reverted, or stopped incorrectly. No data is lost. Delayed changes remain queued and will take effect once processing catches up.
Elevated error rates in the LaunchDarkly application
Monitoring. We've applied a fix and error rates have returned to normal, including custom role listing, search, and assignment. We're continuing to monitor while we complete recovery work.
identified
Identified. We've identified the cause of the elevated error rates and are working on a fix. Customers may still be unable to list, search, or assign custom roles; existing roles continue to be enforced. Most other features are operating normally, though some requests may fail intermittently. We'll share another update as recovery progresses.
identified
We're investigating elevated error rates affecting the LaunchDarkly web application and API. Some requests may fail or time out intermittently, including custom role management. We'll share an update as we learn more.
Server-side streaming requests experienced elevated error rates between approximately 12:00 p.m. and 12:12 p.m. PDT, and some SDKs establishing new streaming connections may have been unable to connect. Polling request error rates remained below 1% throughout the incident.
No customer data was lost or compromised. We apologize for the disruption.
Legacy Incident Archive
30 archived records restored. These records predate source-at-observation attestation. They are shown as historical ServiceAlert records only and do not establish a provider-reported incident, resolution, duration, or current active state.
August 2026
Email delivery failure affecting sign-up verification and notification emails
minorSource not attested
Last archived state: resolved
View archived record details
identified
Emails sent by LaunchDarkly — including sign-up verification, password reset, teammate invitation, and workflow notification emails — are currently failing to deliver due to an authentication issue with an upstream email delivery provider. We have identified the cause and are working to restore delivery.
Feature flag delivery, SDKs, and the LaunchDarkly application itself are not affected.
If you are trying to complete sign-up or reset a password, those emails will not arrive until this...
Flag Updates via Polling API delayed
minorSource not attested
Last archived state: resolved
View archived record details
Polling API
monitoring
We've identified the root cause, our CDN provider had an issue on their end which is fixed now. Monitoring for a while to make sure things stabilise.
investigating
We're experiencing a service degradation which can result in Flag updates via the Polling API to be delayed.
Flag Updates delayed in US Region
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We investigated elevated error rates reported for mobile SDK flag delivery in US East. We've confirmed that flag delivery itself was not impacted. No customer action is required and we are monitoring the situation.
investigating
Flag Updates are currently delayed in the us-east-1 region. We are investigating the issue.
Elevated errors on server-side SDK streaming connections
minorSource not attested
Last archived state: resolved
View archived record details
investigating
We released several mitigations and we're noticing that error rates are dropping. We'll continue to monitor the situation.
investigating
We are investigating elevated HTTP 500 errors affecting some server-side SDK
streaming connections in our US commercial environment. Affected applications
may fail to establish or may intermittently lose their streaming connection to
LaunchDarkly.
July 2026
Investigating - Known Impact
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue with Observability Traces has been identified and a fix has been implemented. We have recovered most trace data that was missing from July 30th 5:16pm to July 31st 10:59am PT. We will resolve the incident once we fully complete data recovery (expected to complete by 5pm PT).
identified
Customers are experiencing missing Observability Traces ingested from July 30th 5:16pm until July 31st 10:59am PT. Observability Logs / Metrics are unaffected.
We have identified the issue and are continuing our work to recover the missing Traces data.
investigating
All customers are experiencing missing Observability Traces starting July 30th at 5:16pm PT. We are investigating and will provide updates as they become available. Trace data is not lost and we are working to recover it.
Delay in Session Replay and Error ingest
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue with session replay and error ingest has been identified and a fix has been implemented. We expect to catch up on all backlogged data ingest in ~15 minutes. No data has been lost.
identified
Customers are experiencing delayed session replay and error ingest as of 11:03am PT. We have identified the issue and are continuing our work to resolve it. Data loss is not expected.
Launchdarkly UI is down and flag evaluation errors are occuring
criticalSource not attested
Last archived state: resolved
View archived record details
identified
We are continuing to work on a fix for this issue.
identified
We are continuing to work on a fix for this issue.
identified
The issue has been identified and a fix has been implemented
investigating
We are continuing to investigate this issue.
investigating
We are currently investigating this issue
LaunchDarkly is operational but customer action may be required
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
All LaunchDarkly services are operational, though some customers need to take action to restore their connections to our Flag Delivery Network. Customers continue to successfully reestablish connections by completing the action guidance below and we continue to support customers working through the residual impact.
SDKs and Relay Proxy instances which attempted to establish a connection to LaunchDarkly on July 10 between 09:11 and 11:42 AM PT were intermittently affected. This includes situa...
monitoring
We are continuing to monitor for any further issues, see our previous update for recovery steps.
monitoring
Customers continue to successfully reestablish connections to our streaming services.
We recommend reviewing your application logs for the incident window. Affected SDKs emit messages—varying by language—that contain any of the following: "giving up permanently," "Invalid SDK key," "unauthorized," "not authorized," or "401." Any service that logged these messages may be unable to receive flag updates or send event data until it is restarted.
Here are the recommended actions for each af...
monitoring
Our Flag Delivery services have recovered and we're observing an increase in customer traffic successfully reestablish connections to our streaming services. Customers who continue to encounter 401 connection errors in their SDKs or Relay Proxy instances are advised to restart their applications and/or Relay Proxy instances.
investigating
We are investigating continued impact to customers' mobile and server SDK caused by the previous incident (https://status.launchdarkly.com/incidents/chywwz01ptb0). If customers are receiving SDK or Relay Proxy 401s please re-establish connections.
Frequentist experiments cannot be saved or started
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
identified
We have identified the issue and are working towards releasing a fix.
investigating
We are currently investigating an issue where experiments using frequentist analysis cannot be saved or started.
Verification emails not being sent
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
investigating
Some customers are not receiving account verification emails. Our team is actively working to mitigate this issue.
