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.
July 2026
elevated error rates on event data ingestion endpoints
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring the results.
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.
June 2026
LaunchDarkly.com and LaunchDarkly.com/docs unavailable for some
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We've identified the source of the problem for areas that were still seeing issues with the LaunchDarkly.com and docs and have a solution in place. We are now monitoring to ensure everything is resolved.
monitoring
Incident seems to be resolved for the majority of users, however, we are continuing to see some issues for in the San Jose and Los Angeles region. We're working to remediate for these regions.
monitoring
A fix has been implemented and monitoring the results.
identified
LaunchDarkly web application and flag delivery unaffected, but documentation and LaunchDarkly.com are unavailable for some users. A fix is on the way.
Observability OpenTelemetry Ingest Delay
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
The issue with Observability data ingest for OpenTelemetry data has been identified and a fix has been implemented. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is resolved.
Observability signals (errors / logs / traces / OTel metrics) are currently delayed by <1 minutes on average.
identified
Some customers are experiencing delayed Observability data ingest for OpenTelemetry data. We have identified the issue and are continuing our work to resolve it.
Observability signals (errors / logs / traces / OTel metrics) are currently delayed by ~6 minutes on average. Data ingest delays began at 10:02am and are improving as of 10:16am PT.
We identified a brief period of elevated errors affecting some LaunchDarkly application requests between 7:30-7:37pm PT. The issue has recovered, and we are continuing to monitor.
Flag dashboard is failing to load
majorSource not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and were monitoring the results
identified
The issue has been identified and a fix is in progress.
investigating
Currently investigating an issue causing the flag dashboard to fail to load.
May 2026
Issue with Slack notifications for Segment approvals
Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been implemented and we are monitoring notifications.
investigating
We are experiencing issues with sending Slack notifications for segment approvals. Email and in-app notifications still work as expected. We are working on restoring this functionality as soon as possible.
Event Ingestion Delays
majorSource not attested
Last archived state: resolved
View archived record details
identified
We are currently experiencing delays in event ingestion, which is impacting Experimentation results and Guarded Rollouts. No data has been lost — all results and events are intact and will be fully accessible once a fix has been deployed. We have identified the root cause and a fix is being released now.
Delayed processing of Session Replay and Error data
minorSource not attested
Last archived state: resolved
View archived record details
identified
We have identified the issue and a fix is in progress. The backlog is actively decreasing. No data has been lost — all queued events will be processed.
investigating
We are currently experiencing a delay in processing Session Replay and Error event data. Incoming data is being queued and will be processed — no data has been lost. Customers may observe a temporary lag in session and error data appearing in the LaunchDarkly UI.
Elevated Streaming Errors in APAC region
minorSource not attested
Last archived state: resolved
View archived record details
identified
We're identified an infrastructure issue causing elevated error rates and are working on a fix.
investigating
We are investigating elevated error rates for streaming initialization in the APAC region. Some customers using streaming server-side SDKs may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly.
Experiment and multi-armed bandit results delayed
minorSource not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented a fix and are catching up on backlogged data. We estimate that we will be fully caught up in about 1 hour.
identified
We have identified the issue and are continuing our work to resolve it.
investigating
We are currently investigating delays in experiment and multi-armed bandit results. Data is currently delayed by 1-2 hours. No data loss is expected.
