LaunchDarkly Outage History
LaunchDarkly is up right nowPingoru has recorded 73 incidents for LaunchDarkly: 71 in the last 12 months and 11 in the last 90 days.
Show as a table
| Month | Incidents | Hours with an open incident |
|---|---|---|
| April 2026 | 10 | 34 of 720 (5%) |
| May 2026 | 8 | 16 of 744 (2%) |
| June 2026 | 5 | 120 of 720 (17%) |
| July 2026 | 11 | 347 of 744 (47%) |
| August 2026 | 5 | 10 of 744 (1%) |
| September 2026 | 0 | 0 of 720 (0%) |
| October 2026 | 3 | 19 of 525 (4%) |
Incidents, newest first
Major May 19, 2026 Event Ingestion Delays 5m Rollout results processing, Experiment results processing
Started May 19, 2026, 02:49 PM UTC· resolved May 19, 2026, 02:54 PM UTC
- identified May 19, 2026, 02:49 PM UTC
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.
- resolved May 19, 2026, 02:54 PM UTC
This incident has been resolved. Event ingestion is operating normally and all Experimentation results and Guarded Rollouts are fully restored. No data was lost. We apologize for any inconvenience caused.
Minor May 16, 2026 Delayed processing of Session Replay and Error data 1h 9m Observability Data Ingest (Sessions, Errors)
Started May 16, 2026, 12:03 AM UTC· resolved May 16, 2026, 01:13 AM UTC
- investigating May 16, 2026, 12:03 AM UTC
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.
- identified May 16, 2026, 12:14 AM UTC
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.
- resolved May 16, 2026, 01:13 AM UTC
All queued events have been processed and data ingestion is operating normally. No data was lost during this incident.
Minor May 6, 2026 Elevated Streaming Errors in APAC region 27m Server-side streaming API
Started May 06, 2026, 03:58 AM UTC· resolved May 06, 2026, 04:26 AM UTC
- investigating May 06, 2026, 03:58 AM UTC
We are investigating elevated error rates for streaming initialization in the APAC region. Some customers using streaming server-side SDKs in the APAC region with may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly.
- identified May 06, 2026, 04:00 AM UTC
We're identified an infrastructure issue causing elevated error rates and are working on a fix.
- resolved May 06, 2026, 04:26 AM UTC
We've implemented a fix and have mitigated impact as of 9:25pm PT. Streaming SDKs should be able to connect successfully at this time.
Minor May 4, 2026 Experiment and multi-armed bandit results delayed 37m Experiment results processing
Started May 04, 2026, 07:47 PM UTC· resolved May 04, 2026, 08:25 PM UTC
- investigating May 04, 2026, 07:47 PM UTC
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.
- identified May 04, 2026, 07:50 PM UTC
We have identified the issue and are continuing our work to resolve it.
- monitoring May 04, 2026, 08:19 PM UTC
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.
- resolved May 04, 2026, 08:25 PM UTC
All experiment and multi-armed bandit result data is caught up. No data was lost.
Minor May 4, 2026 Elevated Streaming Errors in Europe 6h 8m Server-side streaming API
Started May 04, 2026, 10:14 AM UTC· resolved May 04, 2026, 04:23 PM UTC
- investigating May 04, 2026, 12:28 PM UTC
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.
- identified May 04, 2026, 12:51 PM UTC
We're identified an infrastructure issue causing elevated error rates and are working on a fix.
- identified May 04, 2026, 02:30 PM UTC
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.
- monitoring May 04, 2026, 03:47 PM UTC
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.
- resolved May 04, 2026, 04:23 PM UTC
This incident has been resolved.
Minor May 2, 2026 Delay in Experimentation Results and Experimentation Warehouse Data Export 6h 20m Experiment results processing, Warehouse native experimentation
Started May 02, 2026, 12:55 PM UTC· resolved May 02, 2026, 07:15 PM UTC
- investigating May 02, 2026, 12:55 PM UTC
We are investigating an issue causing delayed experimentation results processing and delayed experimentation data warehouse export.
- identified May 02, 2026, 01:17 PM UTC
We've identified the root cause of the experimentation results processing and data export delays and are working on implementing a fix.
- monitoring May 02, 2026, 01:51 PM UTC
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.
- resolved May 02, 2026, 07:15 PM UTC
Experimentation results processing and data warehouse export was caught up as of 12:28 pm PT.
Notice May 1, 2026 Elevated Server SDK Initialization Errors in APAC region –
Started May 01, 2026, 02:52 AM UTC· resolved May 01, 2026, 02:52 AM UTC
- resolved May 01, 2026, 04:06 AM UTC
We've identified elevated error rates with server-side streaming initialization requests in the APAC region between 19:52 and 19:56 PT. Some customers may have experienced initialization timeouts despite SDK retries.
Minor April 30, 2026 Streaming Data Export Delay 43m Data Export
Started Apr 30, 2026, 11:14 AM UTC· resolved Apr 30, 2026, 11:58 AM UTC
- investigating Apr 30, 2026, 11:14 AM UTC
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.
- monitoring Apr 30, 2026, 11:45 AM UTC
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.
- resolved Apr 30, 2026, 11:58 AM UTC
We've caught up on the streaming data export backlog.
Notice April 29, 2026 Errors on streaming SDK initialization –
Started Apr 29, 2026, 11:45 PM UTC· resolved Apr 29, 2026, 11:45 PM UTC
- resolved Apr 30, 2026, 12:30 AM UTC
We've identified an infrastructure issue that caused some 503 responses in feature flagging streaming client initialization on the US LaunchDarkly instance between 16:45 and 17:05 PT. SDKs should automatically retry initialization in most cases.
Minor April 29, 2026 Issue with Experiment Results in case of Flag Variation edits 1d 3h Experiment results processing, Experiment results analysis
Started Apr 29, 2026, 08:19 PM UTC· resolved May 01, 2026, 12:09 AM UTC
- investigating Apr 29, 2026, 08:19 PM UTC
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.
- identified Apr 29, 2026, 08:49 PM UTC
We've identified the issue and are implementing a fix for this behavior.
- monitoring Apr 30, 2026, 12:04 AM UTC
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.
- resolved May 01, 2026, 12:09 AM UTC
We have validated a fix to resolve all remaining experiments with inaccurate sample ratio mismatches (SRMs) or empty experiment results. The vast majority of experiments and experimentation customers were not impacted.
Minor April 28, 2026 Issues with Observability Alert Notification 51m Emails and notifications
Started Apr 28, 2026, 06:34 PM UTC· resolved Apr 28, 2026, 07:25 PM UTC
- investigating Apr 28, 2026, 06:34 PM UTC
We are currently investigating an issue prevent Observability alert notifications from being delivered.
- identified Apr 28, 2026, 06:38 PM UTC
We've identified the root cause preventing Observability alert notifications and are deploying a fix. All other notification types are operational.
- monitoring Apr 28, 2026, 07:10 PM UTC
A fix has been deployed for Observability alerting and we are working to redeliver delayed notifications.
- resolved Apr 28, 2026, 07:25 PM UTC
Observability alerts are functioning and delayed alerts have been redelivered.
Minor April 27, 2026 Delayed Metrics ingest in EU 1h 58m Metrics
Started Apr 27, 2026, 03:39 PM UTC· resolved Apr 27, 2026, 05:37 PM UTC
- investigating Apr 27, 2026, 03:39 PM UTC
We are investigating an issue causing under-reporting of customer metrics in the EU region.
- identified Apr 27, 2026, 03:45 PM UTC
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.
- monitoring Apr 27, 2026, 04:43 PM UTC
We're catching up on backlogged metric data in EU and are monitoring progress. No metric data has been lost.
- resolved Apr 27, 2026, 05:37 PM UTC
We've fully caught up on the metrics data backlog.
Minor April 23, 2026 Issue with Warehouse Data Export –
Started Apr 23, 2026, 07:00 PM UTC· resolved Apr 23, 2026, 07:00 PM UTC
- resolved Apr 29, 2026, 10:22 AM UTC
We're addressing an issue that prevented warehouse data export from 12pm to 6pm PT on April 23 and are working to backfill that data to customer warehouses.
Critical April 20, 2026 Docs site is down 22m Docs (launchdarkly.com/docs)
Started Apr 20, 2026, 10:04 PM UTC· resolved Apr 20, 2026, 10:27 PM UTC
- investigating Apr 20, 2026, 10:04 PM UTC
We are currently investigating this issue.
- investigating Apr 20, 2026, 10:13 PM UTC
We have linked this issue with an outage on our doc provider's side.
- identified Apr 20, 2026, 10:13 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Apr 20, 2026, 10:27 PM UTC
This incident has been resolved.
Minor April 20, 2026 Observability Alerts are not Delivering Slack Notifications 2h 17m Emails and notifications
Started Apr 20, 2026, 09:27 PM UTC· resolved Apr 20, 2026, 11:44 PM UTC
- investigating Apr 20, 2026, 09:27 PM UTC
We are currently investigating an issue where observability alerts are not delivering for Slack notifications to all channels. DM alerts are still functional.
- identified Apr 20, 2026, 10:01 PM UTC
The issue has been identified and a fix is being implemented.
- resolved Apr 20, 2026, 11:44 PM UTC
The issue has been resolved.
Notice April 10, 2026 Degraded connectivity for server-side SDKs in EU region –
Started Apr 10, 2026, 04:30 AM UTC· resolved Apr 10, 2026, 04:30 AM UTC
- resolved Apr 10, 2026, 05:41 AM UTC
Between approximately 9:37 PM and 9:46 PM PT on April 9, 2026, some customers using server-side SDKs in the EU region may have experienced longer than normal initialization times or timeouts when connecting to LaunchDarkly. The issue resolved. No action is required from customers. Server-side SDKs automatically reconnect and recover from transient connectivity issues.
Major March 19, 2026 Server-side streaming rejected new connections across all commercial regions 42m
Started Mar 19, 2026, 03:53 PM UTC· resolved Mar 19, 2026, 04:35 PM UTC
- resolved Mar 19, 2026, 04:58 PM UTC
Server-side streaming began rejecting new connections across all commercial regions, causing 500/503 errors for customers attempting to establish new SDK streaming connections for a brief period of time. Detailed timelines of the incident: - us-east-1 : 7:53 AM PST to 8:24 AM PST - ap-southeast-1: 7:53 AM PST to 7:55 AM PST - eu-west-1: 7:53 AM PST to 8:35 AM PST The team was quickly able to deploy the mitigation before an incident could be declared in our status pages, this is why we're posting it, retroactively. By 8:35am PST connections were re-established successfully in all commercial regions.
Minor March 18, 2026 Experiment Data Missing for Some Experiment Iterations 1d 22h Past experiment iterations
Started Mar 18, 2026, 02:07 AM UTC· resolved Mar 20, 2026, 12:29 AM UTC
- investigating Mar 18, 2026, 02:07 AM UTC
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.
- identified Mar 18, 2026, 02:08 AM UTC
The issue has been identified and a fix is being implemented.
- identified Mar 18, 2026, 04:17 AM UTC
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 experiment iterations. We will provide a further update once full historical data recovery is complete.
- identified Mar 18, 2026, 10:37 PM UTC
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 Mar 19, 2026, 04:52 AM UTC
Our team continues to work on restoring data for previously affected experiment iterations. Complete data restoration expected by tomorrow.
- resolved Mar 20, 2026, 12:29 AM UTC
Our team completed the data restoration for previously affected experiment iterations. Complete data is now available for all experiment iterations in the UI.
Minor March 10, 2026 Event processing delays 5h 7m Experiment results processing, Warehouse native experimentation
Started Mar 10, 2026, 10:59 PM UTC· resolved Mar 11, 2026, 04:07 AM UTC
- investigating Mar 10, 2026, 10:59 PM UTC
Event processing is currently delayed for and will show stale data for several product areas, including: - Autogenerated metric creation - Data Export - Experimentation No data has been lost.
- monitoring Mar 10, 2026, 11:38 PM UTC
A fix has been implemented and we are monitoring the results.
- monitoring Mar 10, 2026, 11:42 PM UTC
We are continuing to monitor for any further issues.
- resolved Mar 11, 2026, 04:07 AM UTC
The issue with Event processing has been resolved. Impacted services have returned to normal operation. Flag Delivery was not impacted. There was no data loss experienced.
Notice March 3, 2026 Observability Usage Reporting 4h 32m
Started Mar 03, 2026, 08:40 PM UTC· resolved Mar 04, 2026, 01:13 AM UTC
- investigating Mar 03, 2026, 08:40 PM UTC
We're investigating reports of inaccurate usage reporting for some Observability products.
- identified Mar 03, 2026, 09:15 PM UTC
We've identified the root cause affecting the Observability "Errors" usage for some customers and are working to correct it.
- resolved Mar 04, 2026, 01:13 AM UTC
We've corrected the issues affecting the Observability "Errors" usage reporting for February and are finalizing reporting corrections for March.
Major February 26, 2026 Investigating Issues with LaunchDarkly Application and Authentication 1h 22m Authentication, Web app (app.launchdarkly.com)
Started Feb 26, 2026, 03:43 PM UTC· resolved Feb 26, 2026, 05:06 PM UTC
- investigating Feb 26, 2026, 03:43 PM UTC
Some customers are experiencing issues with accessing the web app and authentication. We are investigating and will provide updates as they become available.
- identified Feb 26, 2026, 04:17 PM UTC
Some customers are experiencing issues with accessing the web app and authentication. Some customers may see a low number of errors with flag evaluation, as well, but generally our Flag Delivery Network is functional. We have identified the issue and are continuing our work to resolve it.
- monitoring Feb 26, 2026, 04:42 PM UTC
The issue with our application and authentication 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.
- monitoring Feb 26, 2026, 05:04 PM UTC
The issue with our application and authentication has been resolved. Performance has remained stable following mitigation.
- resolved Feb 26, 2026, 05:06 PM UTC
The issue with our application and authentication has been resolved. Performance has remained stable following mitigation.
Notice February 20, 2026 Degraded Observability Ingest 1h 1m OpenTelemetry (Logs, Traces, Metrics)
Started Feb 20, 2026, 10:02 PM UTC· resolved Feb 20, 2026, 11:04 PM UTC
- investigating Feb 20, 2026, 10:02 PM UTC
Beginning around 1:25 PM PST, we are investigating degraded ingest performance. Some customers may experience delays or gaps in observability data. Updates to follow.
- identified Feb 20, 2026, 10:12 PM UTC
We have identified the cause of the degraded ingest performance and are applying mitigation. We are seeing signs of stabilization and continuing to monitor recovery.
- monitoring Feb 20, 2026, 10:13 PM UTC
Mitigation has been applied and ingest performance has stabilized. We are monitoring to ensure continued stability.
- resolved Feb 20, 2026, 11:04 PM UTC
Ingest performance has remained stable following mitigation. We are no longer observing impact.
Minor February 19, 2026 Observability Data Delay 29m Observability Data Ingest (Sessions, Errors)
Started Feb 19, 2026, 03:39 PM UTC· resolved Feb 19, 2026, 04:09 PM UTC
- investigating Feb 19, 2026, 03:39 PM UTC
Sessions and errors may be delayed by up to 1 hours. We are investigating the root cause. No data is lost.
- identified Feb 19, 2026, 03:54 PM UTC
We've identified the root cause and have deployed a fix. We're catching up on the session/error data backlog and should be caught up in ~15 minutes. No data has been lost.
- resolved Feb 19, 2026, 04:09 PM UTC
We've caught up on the session/error data backlog.
Major February 12, 2026 Data attribution issues with Experimentation 4h 8m Experiment results analysis
Started Feb 12, 2026, 11:30 PM UTC· resolved Feb 13, 2026, 03:39 AM UTC
- investigating Feb 13, 2026, 01:31 AM UTC
We are investigating an issue where certain experiment iterations are receiving incorrectly attributed data.
- identified Feb 13, 2026, 01:32 AM UTC
The team has identified the root cause and is working on a fix.
- identified Feb 13, 2026, 02:38 AM UTC
We have fixed the data attribution issues where certain experiment iterations are receiving incorrectly attributed data for any new experiments that are created. We are fixing the data attribution error for active experiments.
- resolved Feb 13, 2026, 03:39 AM UTC
We have fixed the data attribution issues where running experiment iterations were receiving incorrectly attributed data. This incident is now resolved and results for active experiments are now accurate.
Minor February 11, 2026 Observability – Degraded OTel Telemetry Processing 14h 50m OpenTelemetry (Logs, Traces, Metrics)
Started Feb 11, 2026, 01:03 PM UTC· resolved Feb 12, 2026, 03:53 AM UTC
- investigating Feb 12, 2026, 03:50 AM UTC
We are currently investigating an issue affecting OTel telemetry ingestion in LaunchDarkly Observability. Some telemetry data may not be processed as expected. Our team is actively working to identify the root cause and mitigate impact.
- resolved Feb 12, 2026, 03:53 AM UTC
This incident has been resolved. Telemetry data was dropped between 5:03 PM and 7:30 PM PT. All systems are now operating normally.