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> PSTAug <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

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.

Delayed processing of Session Replay and Error data

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.

Degraded Observability Ingest

Feb <var data-var='date'>20</var>, <var data-var='time'>13:28</var> PST Completed - The scheduled maintenance has been completed.Feb <var data-var='date'> 6</var>, <var data-var='time'>13:18</var> PST Scheduled - We are adding additional CIDR ranges (IP ranges) for stream.launchdarkly.com to our public IP list. Some customers may need to update IP allowlists in their firewalls or proxy servers in order for their services to continue establishing streaming connections from server side SDKs to LaunchDarkly without disruption. Please refer to documentation at https://docs.launchdarkly.com/home/advanced/public-ip-list for more information. Added CIDR ranges: -3.41.176.128/26 - 3.40.135.64/26 - 3.44.4.128/26

IP address updates for stream.launchdarkly.com

Feb <var data-var='date'>19</var>, <var data-var='time'>08:09</var> PST Resolved - We've caught up on the session/error data backlog.Feb <var data-var='date'>19</var>, <var data-var='time'>07:54</var> PST Identified - 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.Feb <var data-var='date'>19</var>, <var data-var='time'>07:39</var> PST Investigating - Sessions and errors may be delayed by up to 1 hours. We are investigating the root cause. No data is lost.

Observability Data Delay

Feb <var data-var='date'>12</var>, <var data-var='time'>19:39</var> PST Resolved - 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.Feb <var data-var='date'>12</var>, <var data-var='time'>18:38</var> PST Update - 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.Feb <var data-var='date'>12</var>, <var data-var='time'>17:32</var> PST Identified - The team has identified the root cause and is working on a fix.Feb <var data-var='date'>12</var>, <var data-var='time'>16:30</var> PST Investigating - We are investigating an issue where certain experiment iterations are receiving incorrectly attributed data.

Data attribution issues with Experimentation

Feb <var data-var='date'>11</var>, <var data-var='time'>19:53</var> PST Resolved - This incident has been resolved. Telemetry data was dropped between 5:03 PM and 7:30 PM PT. All systems are now operating normally.Feb <var data-var='date'>11</var>, <var data-var='time'>05:03</var> PST Investigating - 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.

Observability – Degraded OTel Telemetry Processing

Feb <var data-var='date'>10</var>, <var data-var='time'>01:01</var> PST Resolved - This 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 customers may see gaps in metrics or logs for that period.Feb <var data-var='date'> 9</var>, <var data-var='time'>23:30</var> PST Investigating - Some customers using LaunchDarkly Observability with AWS CloudWatch Metric Stream and/or CloudWatch Firehose log export may experience delayed ingestion of metrics/logs into Observability. The impact is limited to Observability data ingestion and related dashboards/alerts.

Degraded Observability for Customers Using AWS CloudWatch Metric Streams or Firehose Log Export

Feb <var data-var='date'> 6</var>, <var data-var='time'>04:44</var> PST Resolved - Customers are seeing expected behavior when accessing the LaunchDarkly UI and API.Feb <var data-var='date'> 6</var>, <var data-var='time'>03:55</var> PST Investigating - We are investigating an issue where a small number of customers may experience errors when accessing the LaunchDarkly UI and API. Feature flag delivery is not impacted. We will provide updates as the investigation continues.

Increased error rate in our UI and API endpoints

Jan <var data-var='date'>31</var>, <var data-var='time'>04:20</var> PST Resolved - This incident has been resolved and all data processing pipelines are fully caught up. No data was lost.Jan <var data-var='date'>31</var>, <var data-var='time'>03:35</var> PST Monitoring - A fix has been implemented and our event processing pipeline for Observability and Opentelemetry are fully caught up. We're continuing to monitor as our event processing pipeline catches up for Flag Status, Evaluations, and Contexts.Jan <var data-var='date'>31</var>, <var data-var='time'>02:23</var> PST Identified - We have identified the issue and are continuing our work to resolve it.Jan <var data-var='date'>31</var>, <var data-var='time'>02:02</var> PST Investigating - All customers are experiencing data ingestion delays with the following: - Observability sessions and errors - Opentelemetry logs, traces, and metrics - Flag status - Evaluations - Contexts We are investigating and will provide updates as they become available. No data loss is expected.

Data ingestion delays

Jan <var data-var='date'>26</var>, <var data-var='time'>14:13</var> PST Resolved - This incident has been resolved.Jan <var data-var='date'>26</var>, <var data-var='time'>12:29</var> PST Monitoring - We believe the issue is resolved for all customers. We're continuing to monitor the situation.Jan <var data-var='date'>26</var>, <var data-var='time'>11:56</var> PST Update - Some customers using Okta SCIM are encountering errors when provisioning and managing LaunchDarkly members. We continue to work on a remediation and have engaged with Okta's support team.Jan <var data-var='date'>26</var>, <var data-var='time'>09:54</var> PST Identified - Some customers are experiencing errors when configuring LaunchDarkly with Okta SCIM. We have identified the issue and are continuing our work to resolve it.

Elevated error rate when configuring Okta SCIM

Jan <var data-var='date'>12</var>, <var data-var='time'>11:44</var> PST Resolved - This incident has been resolved.Jan <var data-var='date'>12</var>, <var data-var='time'>11:16</var> PST Monitoring - A fix has been implemented for the issue preventing editing some JSON flag variations.Jan <var data-var='date'>12</var>, <var data-var='time'>10:49</var> PST Identified - We've identified a front-end issue that is causing issues editing certain JSON flag variations and are working on a fix.Jan <var data-var='date'>12</var>, <var data-var='time'>09:48</var> PST Investigating - Customers may experience issues editing JSON flag variation. We are investigating the root cause and will provide updates shortly.

Unable to edit JSON flag variations

Jan <var data-var='date'> 8</var>, <var data-var='time'>15:29</var> PST Completed - The scheduled maintenance has been completed.Nov <var data-var='date'>21</var>, <var data-var='time'>13:25</var> PST Scheduled - This is a notice that in 2 weeks, we will be adding additional public IPs for events.launchdarkly.com to our public IP list. Some customers may need to update IP allowlists in their firewalls or proxy servers in order for their services to continue sending events from server side SDKs to LaunchDarkly without disruption. Please refer to documentation at https://docs.launchdarkly.com/home/advanced/public-ip-list for more information. We intend to make the change on Dec 4th at 9AM PT. These are the added IP addresses: - 98.85.144.30 - 44.212.135.77 - 98.84.223.204 - 34.204.223.64 - 34.237.35.85 - 3.230.236.93 - 54.88.169.116 - 18.213.209.109 - 3.223.167.178 - 44.195.158.232 - 54.164.137.47 - 52.73.153.168 - 35.175.163.127 - 34.199.229.234 - 34.199.60.133 - 34.192.178.245 - 54.204.244.215 - 18.213.83.244 - 52.202.59.218 - 54.221.194.114 - 98.90.126.95 - 54.161.227.152 - 35.169.83.195 - 3.231.249.26 - 35.175.69.45 - 52.20.213.57 - 54.236.147.34 - 34.232.39.208 - 52.206.189.20 - 44.222.30.36 - 52.1.52.226 - 34.236.176.195 - 3.225.191.53 - 98.87.132.107 - 52.45.107.255 - 34.238.97.13 - 34.206.199.98 - 44.209.246.116 - 54.83.131.69 - 3.216.34.97 - 18.234.10.207 - 54.211.36.54 - 54.80.162.97 - 98.85.205.70 - 3.220.11.5 - 34.236.82.115 - 54.158.240.223 - 44.220.241.117 - 34.226.252.42 - 3.222.208.197

IP address updates for events.launchdarkly.com

Jan <var data-var='date'> 8</var>, <var data-var='time'>14:00</var> PST Resolved - This incident has been resolved.Jan <var data-var='date'> 8</var>, <var data-var='time'>11:08</var> PST Update - Events are caught up.Jan <var data-var='date'> 8</var>, <var data-var='time'>10:57</var> PST Monitoring - A fix has been implemented and we are monitoring the results. We expect to catch up on all events within the next 15 minutes, no data loss is expected.Jan <var data-var='date'> 8</var>, <var data-var='time'>10:46</var> PST Identified - We are currently experiencing delays with guarded releases event ingestion. We are investigating and will provide updates as they become available.

Guarded releases event ingestion delays

Dec <var data-var='date'>17</var>, <var data-var='time'>12:51</var> PST Resolved - This incident has been resolved.Dec <var data-var='date'>17</var>, <var data-var='time'>12:20</var> PST Monitoring - A fix has been implemented and we are monitoring the results.Dec <var data-var='date'>17</var>, <var data-var='time'>11:35</var> PST Identified - We have identified the cause of the ingest delay and are catching up on the backlogged messages. We expect to be caught up on all delayed sessions and errors in the next hour. Data loss is not expected.Dec <var data-var='date'>17</var>, <var data-var='time'>10:33</var> PST Investigating - Sessions and errors may be delayed by up to 3 hours. We are investigating the root cause.

Delay in Observability product data ingest

Dec <var data-var='date'>15</var>, <var data-var='time'>08:38</var> PST Resolved - This incident has been resolved.Dec <var data-var='date'>15</var>, <var data-var='time'>08:20</var> PST Monitoring - A fix has been implemented and we are monitoring the results.Dec <var data-var='date'>15</var>, <var data-var='time'>07:43</var> PST Update - We are observing a reduction in SDK errors. We are continuing to work on a fix.Dec <var data-var='date'>15</var>, <var data-var='time'>07:31</var> PST Identified - The issue has been identified and a fix is being implemented.Dec <var data-var='date'>15</var>, <var data-var='time'>07:22</var> PST Update - We are continuing to investigate this issue.Dec <var data-var='date'>15</var>, <var data-var='time'>07:03</var> PST Update - We are also observing a small percentage timeouts when modifying feature flags via our API or UI. We are continuing to investigate this error.Dec <var data-var='date'>15</var>, <var data-var='time'>06:42</var> PST Update - We are continuing to investigate this issue.Dec <var data-var='date'>15</var>, <var data-var='time'>06:14</var> PST Investigating - We are investigating an increase in SDK error rates affecting a small portion of requests, currently estimated at less than one percent. SDKs will automatically retry these errors, so the primary customer impact is expected to be longer SDK initialization times rather than request failures. We believe the issue is related to an ongoing incident affecting one of our vendors. Our team is actively working to mitigate the impact and will provide additional updates as more information becomes available.

Investigating - Increase in SDK errors

Dec <var data-var='date'>11</var>, <var data-var='time'>09:44</var> PST Completed - The scheduled maintenance has been completed.Nov <var data-var='date'>20</var>, <var data-var='time'>14:54</var> PST Scheduled - We are adding additional public IPs for stream.launchdarkly.com to our public IP list. Some customers may need to update IP allowlists in their firewalls or proxy servers in order for their services to continue establishing streaming connections from server side SDKs to LaunchDarkly without disruption. Please refer to documentation at https://docs.launchdarkly.com/home/advanced/public-ip-list for more information. Added IP addresses: 54.154.242.172 34.254.129.50 52.31.141.156 52.30.206.184 34.252.74.89 54.195.91.253 52.30.93.40 34.249.165.146 52.17.108.103 79.125.65.61 18.200.175.192 34.251.52.49 52.212.183.84 34.251.227.185 54.74.103.246 52.211.120.5 52.211.63.57 18.200.180.85 54.246.141.209 54.77.34.178 54.76.123.134 54.77.209.136 99.80.210.140 54.72.235.236 52.49.228.174

Dec <var data-var='date'> 4</var>, <var data-var='time'>19:47</var> PST Resolved - We have recovered from delays in experimentation results that are sliced by attributes. No data has been lost.Dec <var data-var='date'> 4</var>, <var data-var='time'>13:16</var> PST Investigating - We are investigation an issue with delays in experimentation results that are sliced by attributes. No data has been lost.

Event Processing Delays - Experiment Results Utilizing Attribute Filtering affected

Dec <var data-var='date'> 4</var>, <var data-var='time'>05:05</var> PST Resolved - All of the delayed data has been processed and this incident is resolved.Dec <var data-var='date'> 4</var>, <var data-var='time'>01:50</var> PST Update - We are continuing to process the delayed data. The data is now updated through 2025-12-04, 01:00:00 UTC.Dec <var data-var='date'> 3</var>, <var data-var='time'>21:09</var> PST Update - We are continuing to process the data and data is current as of 2025-12-03, 08:00:00 UTC. We'll continue to update as we process data.Dec <var data-var='date'> 3</var>, <var data-var='time'>14:52</var> PST Identified - Some customers who have configured Snowflake, BigQuery, or Redshift data export destinations may be experiencing delays in events published. There is no data loss. Exported data events are currently 32 hours behind. We are recovering steadily and will continue to send updates

Delays in publishing data export events

Dec <var data-var='date'> 3</var>, <var data-var='time'>08:00</var> PST Resolved - Elevated 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

Is LaunchDarkly down?

LaunchDarkly status is UP

Lastest published events

Delayed processing of Session Replay and Error data

Experiment Data Missing for Some Experiment Iterations

Server-side streaming rejected new connections across all commercial regions

LaunchDarkly Services, Components and Regions

Recent LaunchDarkly events

Planned Upcoming API Versions Retirement

Delayed processing of Session Replay and Error data

Experiment Data Missing for Some Experiment Iterations

Server-side streaming rejected new connections across all commercial regions

Event processing delays

Observability Usage Reporting

Get your FREE account now,
5 monitors included!

Is LaunchDarkly down?

LaunchDarkly status is UP

Lastest published events

Delayed processing of Session Replay and Error data

Experiment Data Missing for Some Experiment Iterations

Server-side streaming rejected new connections across all commercial regions

LaunchDarkly Services, Components and Regions

Recent LaunchDarkly events

Planned Upcoming API Versions Retirement

Delayed processing of Session Replay and Error data

Experiment Data Missing for Some Experiment Iterations

Server-side streaming rejected new connections across all commercial regions

Event processing delays

Observability Usage Reporting

Get your FREE account now,5 monitors included!

Get your FREE account now,
5 monitors included!