THIS IS A SCHEDULED EVENT Dec <var data-var='date'>31</var>, <var data-var='time'>01:00</var> - <var data-var='time'>09:00</var> PST Aug <var data-var='date'>25</var>, <var data-var='time'>11:43</var> PDT Scheduled - As 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 disruption, customers must update integrations and workflows to use version 20240415 before the retirement date. We previously announced the end of life (EOL) for older versions as of April 30, 2025. They have remained available during a grace period, which will end on December 31, 2026 For full details, see our API version changelog: https://launchdarkly.com/docs/api#api-version-changelog Upgrading now ensures uninterrupted access and provides immediate improvements in performance and functionality. We recognize this may be a large undertaking, which is why we are providing extended notice. If you need guidance, please reach out to your account team or contact our support team.

Planned Upcoming API Versions Retirement

May <var data-var='date'>22</var>, <var data-var='time'>12:41</var> PDT Resolved - We have confirmed Slack notifications are now coming through for segment approvals again. May <var data-var='date'>22</var>, <var data-var='time'>12:33</var> PDT Monitoring - A fix has been implemented and we are monitoring notifications. May <var data-var='date'>22</var>, <var data-var='time'>11:40</var> PDT 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.

Issue with Slack notifications for Segment approvals

May <var data-var='date'>19</var>, <var data-var='time'>07:54</var> PDT Resolved - 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. Results were delayed from 6:58am PDT to 7:52am PDT May <var data-var='date'>19</var>, <var data-var='time'>07:49</var> PDT 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.

Event Ingestion Delays

May <var data-var='date'>15</var>, <var data-var='time'>18:13</var> PDT Resolved - All queued events have been processed and data ingestion is operating normally. No data was lost during this incident. May <var data-var='date'>15</var>, <var data-var='time'>17:14</var> PDT 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 <var data-var='date'>15</var>, <var data-var='time'>17:03</var> PDT 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.

Delayed processing of Session Replay and Error data

May <var data-var='date'> 5</var>, <var data-var='time'>21:26</var> PDT Resolved - 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. May <var data-var='date'> 5</var>, <var data-var='time'>21:00</var> PDT Identified - We're identified an infrastructure issue causing elevated error rates and are working on a fix. May <var data-var='date'> 5</var>, <var data-var='time'>20:58</var> PDT 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.

Elevated Streaming Errors in APAC region

May <var data-var='date'> 4</var>, <var data-var='time'>13:25</var> PDT Resolved - All experiment and multi-armed bandit result data is caught up. No data was lost. May <var data-var='date'> 4</var>, <var data-var='time'>13:19</var> PDT 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 <var data-var='date'> 4</var>, <var data-var='time'>12:50</var> PDT Identified - We have identified the issue and are continuing our work to resolve it. May <var data-var='date'> 4</var>, <var data-var='time'>12:47</var> PDT 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.

Experiment and multi-armed bandit results delayed

May <var data-var='date'> 4</var>, <var data-var='time'>09:23</var> PDT Resolved - This incident has been resolved. May <var data-var='date'> 4</var>, <var data-var='time'>08:47</var> PDT 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 <var data-var='date'> 4</var>, <var data-var='time'>07:30</var> PDT Update - 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 <var data-var='date'> 4</var>, <var data-var='time'>05:51</var> PDT Identified - We're identified an infrastructure issue causing elevated error rates and are working on a fix. May <var data-var='date'> 4</var>, <var data-var='time'>03:14</var> PDT 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.

Elevated Streaming Errors in Europe

May <var data-var='date'> 2</var>, <var data-var='time'>12:15</var> PDT Resolved - Experimentation results processing and data warehouse export was caught up as of 12:28 pm PT. May <var data-var='date'> 2</var>, <var data-var='time'>06:51</var> PDT 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 <var data-var='date'> 2</var>, <var data-var='time'>06:17</var> PDT Identified - We've identified the root cause of the experimentation results processing and data export delays and are working on implementing a fix. May <var data-var='date'> 2</var>, <var data-var='time'>05:55</var> PDT Investigating - We are investigating an issue causing delayed experimentation results processing and delayed experimentation data warehouse export.

Delay in Experimentation Results and Experimentation Warehouse Data Export

Apr <var data-var='date'>30</var>, <var data-var='time'>19:52</var> PDT Resolved - 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.

Elevated Server SDK Initialization Errors in APAC region

Apr <var data-var='date'>30</var>, <var data-var='time'>17:09</var> PDT Resolved - 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. Apr <var data-var='date'>29</var>, <var data-var='time'>17:04</var> PDT 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 <var data-var='date'>29</var>, <var data-var='time'>13:49</var> PDT Identified - We've identified the issue and are implementing a fix for this behavior. Apr <var data-var='date'>29</var>, <var data-var='time'>13:19</var> PDT 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.

Issue with Experiment Results in case of Flag Variation edits

Apr <var data-var='date'>30</var>, <var data-var='time'>04:58</var> PDT Resolved - We've caught up on the streaming data export backlog. Apr <var data-var='date'>30</var>, <var data-var='time'>04:45</var> PDT 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 <var data-var='date'>30</var>, <var data-var='time'>04:14</var> PDT 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.

Streaming Data Export Delay

Apr <var data-var='date'>29</var>, <var data-var='time'>16:45</var> PDT Resolved - 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.

Errors on streaming SDK initialization

Apr <var data-var='date'>28</var>, <var data-var='time'>12:25</var> PDT Resolved - Observability alerts are functioning and delayed alerts have been redelivered. Apr <var data-var='date'>28</var>, <var data-var='time'>12:10</var> PDT Monitoring - A fix has been deployed for Observability alerting and we are working to redeliver delayed notifications. Apr <var data-var='date'>28</var>, <var data-var='time'>11:38</var> PDT Identified - We've identified the root cause delaying Observability alert notifications and are deploying a fix. All other notification types are operational. Apr <var data-var='date'>28</var>, <var data-var='time'>11:34</var> PDT Investigating - We are currently investigating an issue prevent Observability alert notifications from being delivered.

Issues with Observability Alert Notification

Apr <var data-var='date'>27</var>, <var data-var='time'>10:37</var> PDT Resolved - We've fully caught up on the metrics data backlog. Apr <var data-var='date'>27</var>, <var data-var='time'>09:43</var> PDT Monitoring - We're catching up on backlogged metric data in EU and are monitoring progress. No metric data has been lost. Apr <var data-var='date'>27</var>, <var data-var='time'>08:45</var> PDT 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 <var data-var='date'>27</var>, <var data-var='time'>08:39</var> PDT Investigating - We are investigating an issue causing under-reporting of customer metrics in the EU region.

Delayed Metrics ingest in EU

Apr <var data-var='date'>23</var>, <var data-var='time'>12:00</var> PDT Resolved - We'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.

Issue with Warehouse Data Export

Apr <var data-var='date'>20</var>, <var data-var='time'>16:44</var> PDT Resolved - The issue has been resolved. Apr <var data-var='date'>20</var>, <var data-var='time'>15:01</var> PDT Identified - The issue has been identified and a fix is being implemented. Apr <var data-var='date'>20</var>, <var data-var='time'>14:27</var> PDT Investigating - We are currently investigating an issue where observability alerts are not delivering for Slack notifications to all channels. DM alerts are still functional.

Observability Alerts are not Delivering Slack Notifications

Apr <var data-var='date'>20</var>, <var data-var='time'>15:27</var> PDT Resolved - This incident has been resolved. Apr <var data-var='date'>20</var>, <var data-var='time'>15:13</var> PDT Identified - The issue has been identified and a fix is being implemented. Apr <var data-var='date'>20</var>, <var data-var='time'>15:13</var> PDT Update - We have linked this issue with an outage on our doc provider's side. Apr <var data-var='date'>20</var>, <var data-var='time'>15:04</var> PDT Investigating - We are currently investigating this issue.

Docs site is down

Apr <var data-var='date'> 9</var>, <var data-var='time'>21:30</var> PDT Resolved - 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.

Degraded connectivity for server-side SDKs in EU region

Apr <var data-var='date'> 6</var>, <var data-var='time'>12:02</var> PDT Resolved - 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 <var data-var='date'> 6</var>, <var data-var='time'>11:40</var> PDT 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 <var data-var='date'> 6</var>, <var data-var='time'>11:15</var> PDT Update - 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 <var data-var='date'> 6</var>, <var data-var='time'>10:58</var> PDT 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.

Mar <var data-var='date'>19</var>, <var data-var='time'>17:29</var> PDT Resolved - Our team completed the data restoration for previously affected experiment iterations. Complete data is now available for all experiment iterations in the UI. Mar <var data-var='date'>18</var>, <var data-var='time'>21:52</var> PDT Update - Our team continues to work on restoring data for previously affected experiment iterations. Complete data restoration expected by tomorrow. Mar <var data-var='date'>18</var>, <var data-var='time'>15:37</var> PDT Update - 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 <var data-var='date'>17</var>, <var data-var='time'>21:17</var> PDT Update - 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. Mar <var data-var='date'>17</var>, <var data-var='time'>19:08</var> PDT Identified - The issue has been identified and a fix is being implemented. Mar <var data-var='date'>17</var>, <var data-var='time'>19:07</var> PDT 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.

Experiment Data Missing for Some Experiment Iterations

Mar <var data-var='date'>19</var>, <var data-var='time'>09:58</var> PDT Resolved - 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.

Server-side streaming rejected new connections across all commercial regions

Mar <var data-var='date'>10</var>, <var data-var='time'>21:07</var> PDT Resolved - 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. Mar <var data-var='date'>10</var>, <var data-var='time'>16:42</var> PDT Update - We are continuing to monitor for any further issues. Mar <var data-var='date'>10</var>, <var data-var='time'>16:38</var> PDT Monitoring - A fix has been implemented and we are monitoring the results. Mar <var data-var='date'>10</var>, <var data-var='time'>15:59</var> PDT Investigating - 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.

Event processing delays

Mar <var data-var='date'> 3</var>, <var data-var='time'>17:13</var> PST Resolved - We've corrected the issues affecting the Observability "Errors" usage reporting for February and are finalizing reporting corrections for March. Mar <var data-var='date'> 3</var>, <var data-var='time'>13:15</var> PST Identified - We've identified the root cause affecting the Observability "Errors" usage for some customers and are working to correct it. Mar <var data-var='date'> 3</var>, <var data-var='time'>12:40</var> PST Investigating - We're investigating reports of inaccurate usage reporting for some Observability products.

Observability Usage Reporting

Feb <var data-var='date'>26</var>, <var data-var='time'>09:06</var> PST Resolved - The issue with our application and authentication has been resolved. Performance has remained stable following mitigation. Feb <var data-var='date'>26</var>, <var data-var='time'>09:04</var> PST Update - The issue with our application and authentication has been resolved. Performance has remained stable following mitigation. Feb <var data-var='date'>26</var>, <var data-var='time'>08:42</var> PST Monitoring - 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. Feb <var data-var='date'>26</var>, <var data-var='time'>08:17</var> PST Identified - 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. Feb <var data-var='date'>26</var>, <var data-var='time'>07:43</var> PST Investigating - Some customers are experiencing issues with accessing the web app and authentication. We are investigating and will provide updates as they become available.

Investigating Issues with LaunchDarkly Application and Authentication

Feb <var data-var='date'>20</var>, <var data-var='time'>15:04</var> PST Resolved - Ingest performance has remained stable following mitigation. We are no longer observing impact. Feb <var data-var='date'>20</var>, <var data-var='time'>14:13</var> PST Monitoring - Mitigation has been applied and ingest performance has stabilized. We are monitoring to ensure continued stability. Feb <var data-var='date'>20</var>, <var data-var='time'>14:12</var> PST Identified - 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. Feb <var data-var='date'>20</var>, <var data-var='time'>14:02</var> PST Investigating - 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.

Is LaunchDarkly down?

LaunchDarkly status is UP

Lastest published events

Issue with Slack notifications for Segment approvals

Event Ingestion Delays

Delayed processing of Session Replay and Error data

LaunchDarkly Services, Components and Regions

Recent LaunchDarkly events

Planned Upcoming API Versions Retirement

Issue with Slack notifications for Segment approvals

Event Ingestion Delays

Delayed processing of Session Replay and Error data

Elevated Streaming Errors in APAC region

Experiment and multi-armed bandit results delayed

Get your FREE account now,
5 monitors included!

Is LaunchDarkly down?

LaunchDarkly status is UP

Lastest published events

Issue with Slack notifications for Segment approvals

Event Ingestion Delays

Delayed processing of Session Replay and Error data

LaunchDarkly Services, Components and Regions

Recent LaunchDarkly events

Planned Upcoming API Versions Retirement

Issue with Slack notifications for Segment approvals

Event Ingestion Delays

Delayed processing of Session Replay and Error data

Elevated Streaming Errors in APAC region

Experiment and multi-armed bandit results delayed

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!