New Multi-region uptime checks and custom-domain status pages

LaunchDarkly Outage History

Daily provider-status observations and published incident history for LaunchDarkly.

Operational

LaunchDarkly is operational. Verified . Official provider source.

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

Jul 24Oct 21

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 23 Today
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
minor Observed active window 1h 40m

View incident details and source

Started:

Experiment management Rollout management Release pipelines
monitoring
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
minor Observed active window 18h 59m

View incident details and source

Started:

Web app (app.launchdarkly.com)
monitoring
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.
August 2026
Flag delivery errors in Streaming API
minor Observed active window 24m

View incident details and source

Started:

Server-side streaming API
monitoring
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.

May 2026
Elevated Streaming Errors in Europe
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We've implemented a fix and have mitigated impact as of 8:35am PT. Streaming SDKs should be able to connect successfully at this time.
identified
We're continuing to address the root cause of the elevated error rate. Server SDKs may require additional time to initialize while requests are retried.
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 Europe region. Some customers using streaming server-side SDKs may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly.
Delay in Experimentation Results and Experimentation Warehouse Data Export
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We have implemented a fix and are catching up on backlogged experimentation results and data export. We estimate that we will be fully caught up in about 8 hours.
identified
We've identified the root cause of the experimentation results processing and data export delays and are working on implementing a fix.
investigating
We are investigating an issue causing delayed experimentation results processing and delayed experimentation data warehouse export.
April 2026
Streaming Data Export Delay
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We've identified latency in Pub/Sub export that were causing streaming data export delays that has since resolved. We're catching up on the export backlog now.
investigating
We are investigating a delay with streaming data export delivery. No data is lost, but customers using streaming data export may notice a multi-minute lag in receiving data.
Issue with Experiment Results in case of Flag Variation edits
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We've released a fix to prevent this issue in new experiments and iterations. We're working to resolve this issue for experiment data recently processed.
identified
We've identified the issue and are implementing a fix for this behavior.
investigating
We are aware of an issue affecting some customers that may result in sample ratio mismatches (SRMs) or empty experiment results if flag variations are edited between experiment iterations.
Issues with Observability Alert Notification
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
A fix has been deployed for Observability alerting and we are working to redeliver delayed notifications.
identified
We've identified the root cause delaying Observability alert notifications and are deploying a fix. All other notification types are operational.
investigating
We are currently investigating an issue prevent Observability alert notifications from being delivered.
Delayed Metrics ingest in EU
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
We're catching up on backlogged metric data in EU and are monitoring progress. No metric data has been lost.
identified
We've identified that metrics ingest was delayed between 11:11 - 11:27am ET. No metric data has been lost. We're working on catching up on the delayed data.
investigating
We are investigating an issue causing under-reporting of customer metrics in the EU region.
Docs site is down
critical Source not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
investigating
We have linked this issue with an outage on our doc provider's side.
investigating
We are currently investigating this issue.
Observability Alerts are not Delivering Slack Notifications
minor Source not attested
Last archived state: resolved
View archived record details
identified
The issue has been identified and a fix is being implemented.
investigating
We are currently investigating an issue where observability alerts are not delivering for Slack notifications to all channels. DM alerts are still functional.
Delayed processing of Session Replay and Error data
minor Source not attested
Last archived state: resolved
View archived record details
monitoring
The delayed processing of Session Replay and Error event data has been resolved. All queued events have been processed and data ingestion is operating normally. No data was lost during this incident. Thank you for your patience.
identified
We have identified the cause of the delayed Session Replay and Error event processing and a fix is in progress. The backlog is actively decreasing. No data has been lost — all queued events will be processed.
identified
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. We have identified the root cause as elevated database utilization and are actively working to resolve the backlog. We will provide updates as processing returns to normal.
March 2026
Experiment Data Missing for Some Experiment Iterations
minor Source not attested
Last archived state: resolved
View archived record details
identified
Our team continues to work on restoring data for previously affected experiment iterations. Complete data restoration expected by tomorrow.
identified
Our team continues to work on restoring data for previously affected experiment iterations. We will provide a further update once full historical data recovery is complete.
identified
We have implemented a mitigation that restores data availability for all current experiment iterations. Affected accounts should now see up-to-date reporting and exposure data in the UI. Our team continues to work on restoring data for previously affected experimen...
identified
The issue has been identified and a fix is being implemented.
investigating
We are aware of an issue affecting experiment reporting data for a subset of accounts. Affected users may see incomplete data for some experiment iterations in the UI.