LaunchDarkly Outage History
Daily status observations, past incidents, and reported issue history for LaunchDarkly.
Checking current status...
90-Day Trend
Monthly Status Summary
| Month | Issue-free days | Days Tracked | Days with Issues |
|---|---|---|---|
| August 2026 | 88% | 25 | 3 |
| July 2026 | 22.6% | 31 | 24 |
| June 2026 | 66.7% | 30 | 10 |
| May 2026 | 100% | 5 | 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.
Daily Status (Last 91 Days)
May 27
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
August 2026
Email delivery failure affecting sign-up verification and notification emails
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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.
Web application unavailable and flag delivery evaluations have elevated failure rate
Started:
monitoring
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.
identified
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.
identified
We have identified the root cause and are implementing a fix.
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 ...
Launchdarkly UI is down and flag evaluation errors are occuring
Started:
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
Started:
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
Started:
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.
High volume of error alerts related to flag delivery network.
Started:
monitoring
We have rolled out a fix and error rates are returning to normal
investigating
We are continuing to investigate this issue.
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.
Verification emails not being sent
Started:
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.
elevated error rates on event data ingestion endpoints
Started:
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
Started:
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
Started:
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.
Elevated errors affecting LaunchDarkly application requests
Started:
monitoring
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.
Delays in event ingestion
Started:
monitoring
We have made major progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are continuing to monitor and will provide another update when recovery is complete.
monitoring
We have made major progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are continuing to monitor and will provide another update when recovery is complete.
monitoring
We have made partial progress. We identified that a small percentage of event data was lost during two windows: June 9, 11:41 - 11:59 UTC and June 10, 23:55 UTC - June 11, 00:21 UTC. Some event-based features may show incomplete data while backfills and recovery continue. We are continuing to monitor and will provide another update when recovery is complete.
monitoring
We have made partial progress. We have identified a brief period of event data loss, and some event-based features may show incomplete data while we continue recovery. We are continuing to monitor.
monitoring
We have made partial progress. We have identified a brief period of event data loss, and some event-based features may show incomplete data while we continue recovery. We are continuing to monitor.
monitoring
We are continuing to monitor for any further issues.
monitoring
We have made partial progress. We have identified a brief period of event data loss, and some event-based features may show incomplete data while we continue recovery. We are continuing to monitor.
monitoring
We have made partial progress. Some features may show data gaps while we complete recovery. We are continuing to monitor.
monitoring
We have made partial progress. Some features may show data gaps while we complete recovery. We are continuing to monitor.
monitoring
We are continuing to monitor for any further issues.
monitoring
We are monitoring the status of our services.
monitoring
A fix has been implemented and we are monitoring the results.
identified
We are currently experiencing delays in event ingestion impacting multiple product areas starting at 12:40pm PT. We have identified the issue and are working on a fix. No data has been lost.
Flag dashboard is failing to load
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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.
Elevated Streaming Errors in Europe
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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
Started:
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.