LaunchDarkly Outage History

85 incidents recorded over the last 365 days, 82 of them resolved. Durations are measured from when PulsAPI first saw the problem to when it cleared, which is usually longer than the vendor's own figure.

Live LaunchDarkly status93.71% uptime history

Every Recorded LaunchDarkly Incident

LaunchDarkly incidents, newest first, with date, duration and status.
DateIncidentDurationStatus
Dec 31, 2026Planned Upcoming API Versions RetirementAs part of our commitment to reliability and security, LaunchDarkly will retire all API versions except 20240415 on December 31, 2026. After this date, all requests made to retired versions will stop working. To avoid…8h 0mScheduled
Aug 17, 2026Flag Updates via Polling API delayedThis incident has been resolved.5h 26mResolved
Aug 14, 2026Flag Updates delayed in US RegionThe issue is being marked as resolved. We're seeing improved latencies and our systems have recovered.2h 0mResolved
Aug 7, 2026Elevated errors on server-side SDK streaming connectionsSDKs restored to operational46 minResolved
Jul 31, 2026Investigating - Known ImpactThe issue with Observability Traces has been resolved. Missing trace data has been recovered.5h 10mResolved
Jul 28, 2026Delay in Session Replay and Error ingestThe issue with session replay and error ingest has been resolved. We've caught up on all backlogged data as of 1:01pm PT.40 minResolved
Jul 26, 2026Elevated API Latency and Errors (11:32–11:48 PT)Between 11:32 and 11:48 PT, customers experienced increased latency and elevated error rates on API endpoints. Latency and error rates have returned to normal, and the incident has been resolved.0 minResolved
Jul 10, 2026Web application unavailable and flag delivery evaluations have elevated failure rateAll service availability has been fully restored. Customers using server-side SDKs might need to restart their applications to re-enable the SDKs' connection to LaunchDarkly. Customers using the Relay Proxy may also…1h 9mResolved
Jul 10, 2026Launchdarkly UI is down and flag evaluation errors are occuringLaunchDarkly UI has recovered. We will continue to monitor Flag Delivery and event ingest here: https://status.launchdarkly.com/incidents/chywwz01ptb0.1h 31mResolved
Jul 10, 2026LaunchDarkly is operational but customer action may be requiredThis incident has been resolved.458h 15mResolved
Jul 8, 2026Frequentist experiments cannot be saved or startedThis incident has been resolved.1h 38mResolved
Jul 7, 2026Delays in Experimentation and Guarded Rollout resultsEvent ingestion is operating normally. Experimentation results, Guarded Rollouts, and in-product data charts were delayed ~5 min between 7:13–7:53 AM PT. No data was lost. We apologize for any inconvenience.0 minResolved
Jul 6, 2026High volume of error alerts related to flag delivery network.All error rates have normalized.29 minResolved
Jul 6, 2026Verification emails not being sentThis incident has been resolved.1h 19mResolved
Jul 3, 2026Elevated error rates on event data ingestion endpointsThis incident has been resolved.1h 37mResolved
Jun 17, 2026LaunchDarkly.com and LaunchDarkly.com/docs unavailable for someWe're now seeing restored access in the affected regions.5h 46mResolved
Jun 15, 2026Observability OpenTelemetry Ingest DelayThe issue with Observability data ingest for OpenTelemetry data has been resolved. Impacted services have returned to normal operation.36 minResolved
Jun 12, 2026Elevated errors affecting LaunchDarkly application requestsMonitoring has confirmed no further impact outside of the initially reported 7:30-7:37pm PT timeframe35 minResolved
Jun 10, 2026Removing legacy IP addresses for stream.launchdarkly.comThe scheduled maintenance has been completed.1h 0mScheduled
Jun 8, 2026Delays in event ingestionThis incident has been resolved.113h 6mResolved
Jun 3, 2026Flag dashboard is failing to loadThe incident has been resolved and the flag dashboard is successfully loading.55 minResolved
May 22, 2026Issue with Slack notifications for Segment approvalsWe have confirmed Slack notifications are now coming through for segment approvals again.1h 1mResolved
May 19, 2026Event Ingestion DelaysThis 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. Results were…5 minResolved
May 16, 2026Delayed processing of Session Replay and Error dataAll queued events have been processed and data ingestion is operating normally. No data was lost during this incident.1h 9mResolved
May 6, 2026Elevated Streaming Errors in APAC regionWe've implemented a fix and have mitigated impact as of 9:25pm PT. Streaming SDKs should be able to connect successfully at this time.27 minResolved
May 4, 2026Experiment and multi-armed bandit results delayedAll experiment and multi-armed bandit result data is caught up. No data was lost.37 minResolved
May 4, 2026Elevated Streaming Errors in EuropeThis incident has been resolved.6h 8mResolved
May 2, 2026Delay in Experimentation Results and Experimentation Warehouse Data ExportExperimentation results processing and data warehouse export was caught up as of 12:28 pm PT.6h 20mResolved
May 1, 2026Elevated Server SDK Initialization Errors in APAC regionWe'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.-74 minResolved
Apr 30, 2026Streaming Data Export DelayWe've caught up on the streaming data export backlog.43 minResolved
Apr 30, 2026Errors on streaming SDK initializationWe'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…-45 minResolved
Apr 29, 2026Issue with Experiment Results in case of Flag Variation editsWe 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.27h 50mResolved
Apr 29, 2026Issue with Warehouse Data ExportWe've addressed an issue that prevented warehouse data export from 12pm to 6pm PT on April 23. All missing data has been retroactively pushed to customer warehouses.-8122 minResolved
Apr 28, 2026Issues with Observability Alert NotificationObservability alerts are functioning and delayed alerts have been redelivered.51 minResolved
Apr 27, 2026Delayed Metrics ingest in EUWe've fully caught up on the metrics data backlog.1h 58mResolved
Apr 20, 2026Docs site is downThis incident has been resolved.22 minResolved
Apr 20, 2026Observability Alerts are not Delivering Slack NotificationsThe issue has been resolved.2h 17mResolved
Apr 10, 2026Degraded connectivity for server-side SDKs in EU regionBetween 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…-71 minResolved
Apr 6, 2026Delayed processing of Session Replay and Error dataThe 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…1h 3mResolved
Mar 19, 2026Server-side streaming rejected new connections across all commercial regionsServer-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…0 minResolved
Mar 18, 2026Experiment Data Missing for Some Experiment IterationsOur team completed the data restoration for previously affected experiment iterations. Complete data is now available for all experiment iterations in the UI.46h 21mResolved
Mar 10, 2026Event processing delaysThe 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.5h 7mResolved
Mar 3, 2026Observability Usage ReportingWe've corrected the issues affecting the Observability "Errors" usage reporting for February and are finalizing reporting corrections for March.4h 32mResolved
Feb 26, 2026Investigating Issues with LaunchDarkly Application and AuthenticationThe issue with our application and authentication has been resolved. Performance has remained stable following mitigation.1h 22mResolved
Feb 20, 2026Degraded Observability IngestIngest performance has remained stable following mitigation. We are no longer observing impact.1h 1mResolved
Feb 20, 2026IP address updates for stream.launchdarkly.comThe scheduled maintenance has been completed.1h 0mScheduled
Feb 19, 2026Observability Data DelayWe've caught up on the session/error data backlog.29 minResolved
Feb 12, 2026Data attribution issues with ExperimentationWe 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.4h 8mResolved
Feb 11, 2026Observability – Degraded OTel Telemetry ProcessingThis incident has been resolved. Telemetry data was dropped between 5:03 PM and 7:30 PM PT. All systems are now operating normally.14h 50mResolved
Feb 10, 2026Degraded Observability for Customers Using AWS CloudWatch Metric Streams or Firehose Log ExportThis issue has been resolved. Observability ingestion from AWS CloudWatch Metric Streams and CloudWatch Firehose log export has returned to normal. Data sent during the incident window may not have been ingested, and…1h 30mResolved
Feb 6, 2026Increased error rate in our UI and API endpointsCustomers are seeing expected behavior when accessing the LaunchDarkly UI and API.49 minResolved
Jan 31, 2026Data ingestion delaysThis incident has been resolved and all data processing pipelines are fully caught up. No data was lost.2h 18mResolved
Jan 26, 2026Elevated error rate when configuring Okta SCIMThis incident has been resolved.4h 18mResolved
Jan 12, 2026Unable to edit JSON flag variationsThis incident has been resolved.1h 56mResolved
Jan 8, 2026Guarded releases event ingestion delaysThis incident has been resolved.3h 13mResolved
Dec 17, 2025Delay in Observability product data ingestThis incident has been resolved.2h 17mResolved
Dec 15, 2025Investigating - Increase in SDK errorsThis incident has been resolved.2h 24mResolved
Dec 4, 2025Event Processing Delays - Experiment Results Utilizing Attribute Filtering affectedWe have recovered from delays in experimentation results that are sliced by attributes. No data has been lost.6h 30mResolved
Dec 3, 2025Delays in publishing data export eventsAll of the delayed data has been processed and this incident is resolved.14h 13mResolved
Dec 3, 2025Elevated error rates in apac region for server side sdksElevated error rates in apac region for server side sdks attempting to make new connections to the streaming service from 8:05 AM PT to 8:11 AM PT. The issue is now resolved-272 minResolved
Nov 26, 2025Intermittent issues accessing flag detailsThis incident has been resolved.42 minResolved
Nov 24, 2025Delayed Event ProcessingThis incident has been resolved.3h 31mResolved
Nov 13, 2025Investigating elevated latencyThe issue with the AI Configs list page has been resolved. Impacted services have returned to normal operation.2h 46mResolved
Nov 12, 2025Elevated error rates for a small number of customersBetween 7:37am and 8:19am PT, a small number of customers in the us-east-1 region encountered elevated error rates with Polling SDK and API requests. This was caused by a minor issue affecting a CDN POP, which has since…-278 minResolved
Nov 5, 2025Customers unable to edit custom rules on flagsThis incident has been resolved.1h 19mResolved
Nov 3, 2025AI Configs monitoring page tab failing to loadThis incident has been resolved.1h 11mResolved
Nov 1, 2025Delayed flag updates for small number of customersA limited number of customers (primarily in EU regions) with Polling SDK connections experienced elevated latency and errors rates between 9:05am and 9:58am PT, caused by a service incident in our CDN provider.0 minResolved
Oct 28, 2025Live Events not loadingWe've resolved an issue causing Live Events to not load.48 minResolved
Oct 28, 2025Experiment results and metrics unavailableWe've resolved an issue causing Experiment results to fail to load.33 minResolved
Oct 20, 2025Elevated latencies and delaysThis incident has been resolved. One of our mitigation steps involved adding new IPs for stream.launchdarkly.com to our public IP list. Some customers may need to update IP allowlists in their firewalls or proxy…23h 45mResolved
Oct 10, 2025Delays in event dataThe issue with delays in event data has been resolved. Event data is up to date and impacted services have returned to normal operation47 minResolved
Oct 7, 2025Delayed flag updates for small number of customersThe issue has been resolved. Flag updates have returned to normal operation.10 minResolved
Oct 3, 2025Errors generating new client librariesUsers are now able to generate new client libraries.1h 23mResolved
Oct 1, 2025Delay in event processingThis incident has been resolved.34 minResolved
Sep 30, 2025Self-serve legacy customers are unable to check out or modify planThe issue with legacy self-serve check out has been resolved.2h 52mResolved
Sep 22, 2025Increased error rate on flag status APIFrom 11:38 am PT - 11:46 am PT we experienced an elevated error rate on the flag evaluation and flag status APIs, used by flag list, flag targeting, and feature monitoring endpoints.-38 minResolved
Sep 19, 2025Goals Endpoint Initialization Failures Impacting ExperimentsThe issue with the Goals endpoint has been resolved. We will continue monitoring to ensure normal operation.31 minResolved
Sep 19, 2025Customers are unable to edit flag JSONThe issue where the JSON failed to load when clicking “Edit JSON” has been fixed. Functionality is now fully restored.35 minResolved
Sep 19, 2025Customers on Foundation plans are unable to invite new membersThis incident has been resolved.4h 14mResolved
Sep 17, 2025Trial Customers Blocked from Foundational Plan UpgradeThe issue preventing trial customers from upgrading to the Foundational plan has been resolved. All functionality is now operating as expected.1h 33mResolved
Sep 17, 2025Delayed flag updates for small number of customersA small number of customers experienced delayed flag updates made between 16:22 and 16:49 PT. The issue has been resolved, and all services are now operating normally.-72 minResolved
Sep 9, 2025Guarded releases and Experiments are experiencing elevated errorsWe have turned on Views for Early Access users and confirmed there are no issues with Guarded Releases or Experiments. This issue is fully resolved.2h 30mResolved
Aug 28, 2025Elevated TLS negotiation error rate for server side SDKs in streaming modeBetween 10:12 AM and 10:52 AM PT, a small subset of customers using LaunchDarkly server-side SDKs in streaming mode on older TLS versions may have experienced TLS negotiation errors when initializing SDKs. The issue has…-90 minResolved
Aug 27, 2025CORS errors for a small subset of customersA small number of customers using the LaunchDarkly JavaScript client side SDK with use cases that involved a single browser session requesting the same LaunchDarkly environment from two or more domains in certain…-91 minResolved
Aug 25, 2025Onboarding/Quickstart Not VisibleThis incident has been resolved.3h 5mResolved

How to Read This LaunchDarkly Incident Log

Each row is an incident PulsAPI observed, not a summary written afterwards. The duration is wall-clock time between the first failing check and the first clean one, so it includes the window before LaunchDarkly acknowledged anything. Vendor post-mortems typically measure from acknowledgement, which is why their numbers are usually shorter.

Incidents still open have no duration yet and are listed as ongoing rather than being given a running total. The archive covers the last 365 days; anything older has aged out of the window rather than never having happened.

The longest single LaunchDarkly outage in this window ran 19d 2h, against a mean recovery of 11h 6m. If you depend on LaunchDarkly in a customer-facing path, the longest figure is the one to design around. The mean is what happens on a normal bad day; the maximum is what happens on the worst one.