New AI Incident Response, Multi-Region Agents, and Custom-Domain Status Pages — May 2026
Monitor Features overview Vendor status Uptime & synthetic checks Certificate lifecycle Operate Incident management Live demo
By goal Replace your stack Why ServiceAlert Competitor comparisons Alternatives directory By signal Reliability hub   · Uptime rankings   · SLA compliance Outage map
Services
Check & scan SSL security grader Status checker DNS lookup Response time WHOIS lookup Calculators SLA calculator Downtime calculator Embed Status badges All tools →
Pricing
Guides Help center Uptime monitoring RUM & analytics Teams & shared monitors Developer API reference Status badges Learn Blog Outage reports FAQ Changelog
Dashboard

LaunchDarkly Outage History

Uptime record, past incidents, and downtime history for LaunchDarkly.

Checking current status...
79.1% uptime over 91 days
99.9% ✗ 99.5% ✗ 99% ✗ 95% ✗

90-Day Trend

Feb 25May 25

Monthly Uptime

Month Uptime Days Tracked Days with Issues
May 2026 72% 25 7
April 2026 80% 30 6
March 2026 83.9% 31 5
February 2026 80% 5 1

Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.

Daily Status (Last 91 Days)

Feb 24 Today
Operational Degraded Partial Outage Major Outage Maintenance No Data

Incident History

May 2026
Issue with Slack notifications for Segment approvals

Started: May 22, 6:40 PM

monitoring
A fix has been implemented and we are monitoring notifications.
May 22, 7:33 PM
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.
May 22, 6:40 PM
Event Ingestion Delays
major

Started: May 19, 2:49 PM

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.
May 19, 2:49 PM
Delayed processing of Session Replay and Error data
minor

Started: May 16, 12:03 AM

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.
May 16, 12:14 AM
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.
May 16, 12:03 AM
Elevated Streaming Errors in APAC region
minor

Started: May 6, 3:58 AM

identified
We're identified an infrastructure issue causing elevated error rates and are working on a fix.
May 6, 4:00 AM
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.
May 6, 3:58 AM
Experiment and multi-armed bandit results delayed
minor

Started: May 4, 7:47 PM

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.
May 4, 8:19 PM
identified
We have identified the issue and are continuing our work to resolve it.
May 4, 7:50 PM
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.
May 4, 7:47 PM
Elevated Streaming Errors in Europe
minor

Started: May 4, 10:14 AM

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.
May 4, 3:47 PM
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.
May 4, 2:30 PM
identified
We're identified an infrastructure issue causing elevated error rates and are working on a fix.
May 4, 12:51 PM
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.
May 4, 12:28 PM
Delay in Experimentation Results and Experimentation Warehouse Data Export
minor

Started: May 2, 12:55 PM

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.
May 2, 1:51 PM
identified
We've identified the root cause of the experimentation results processing and data export delays and are working on implementing a fix.
May 2, 1:17 PM
investigating
We are investigating an issue causing delayed experimentation results processing and delayed experimentation data warehouse export.
May 2, 12:55 PM
April 2026
Streaming Data Export Delay
minor

Started: Apr 30, 11:14 AM

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.
Apr 30, 11:45 AM
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.
Apr 30, 11:14 AM
Issue with Experiment Results in case of Flag Variation edits
minor

Started: Apr 29, 8:19 PM

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.
Apr 30, 12:04 AM
identified
We've identified the issue and are implementing a fix for this behavior.
Apr 29, 8:49 PM
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.
Apr 29, 8:19 PM
Issues with Observability Alert Notification
minor

Started: Apr 28, 6:34 PM

monitoring
A fix has been deployed for Observability alerting and we are working to redeliver delayed notifications.
Apr 28, 7:10 PM
identified
We've identified the root cause delaying Observability alert notifications and are deploying a fix. All other notification types are operational.
Apr 28, 6:38 PM
investigating
We are currently investigating an issue prevent Observability alert notifications from being delivered.
Apr 28, 6:34 PM
Delayed Metrics ingest in EU
minor

Started: Apr 27, 3:39 PM

monitoring
We're catching up on backlogged metric data in EU and are monitoring progress. No metric data has been lost.
Apr 27, 4:43 PM
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.
Apr 27, 3:45 PM
investigating
We are investigating an issue causing under-reporting of customer metrics in the EU region.
Apr 27, 3:39 PM
Docs site is down
critical

Started: Apr 20, 10:04 PM

identified
The issue has been identified and a fix is being implemented.
Apr 20, 10:13 PM
investigating
We have linked this issue with an outage on our doc provider's side.
Apr 20, 10:13 PM
investigating
We are currently investigating this issue.
Apr 20, 10:04 PM
Observability Alerts are not Delivering Slack Notifications
minor

Started: Apr 20, 9:27 PM

identified
The issue has been identified and a fix is being implemented.
Apr 20, 10:01 PM
investigating
We are currently investigating an issue where observability alerts are not delivering for Slack notifications to all channels. DM alerts are still functional.
Apr 20, 9:27 PM
Delayed processing of Session Replay and Error data
minor

Started: Apr 6, 5:58 PM

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.
Apr 6, 6:40 PM
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.
Apr 6, 6:15 PM
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.
Apr 6, 5:58 PM
March 2026
Experiment Data Missing for Some Experiment Iterations
minor

Started: Mar 18, 2:07 AM

identified
Our team continues to work on restoring data for previously affected experiment iterations. Complete data restoration expected by tomorrow.
Mar 19, 4:52 AM
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.
Mar 18, 10:37 PM
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...
Mar 18, 4:17 AM
identified
The issue has been identified and a fix is being implemented.
Mar 18, 2:08 AM
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.
Mar 18, 2:07 AM
View live status for LaunchDarkly Browse all services