Completed -
The deprecation of TLS versions 1.0 and 1.1 was successfully completed.
Jun 22, 12:31 PDT
Update -
Scheduled maintenance is still in progress. We will provide updates as necessary.
Jun 22, 11:08 PDT
In progress -
TLSv1.2 is now required for our standard SDK endpoints.
Jun 22, 11:08 PDT
Update -
In an hour from now, we will be disabling TLS 1.0 and TLS 1.1, and requiring TLS 1.2 or greater, for the following LaunchDarkly endpoints:
* clientstream.launchdarkly.com
* events.launchdarkly.com
* stream.launchdarkly.com
Jun 22, 10:00 PDT
Update -
Today's TLSv1 brownout has already concluded.
On Wednesday, June 22, 2022 at 18:00 UTC, we will be disabling TLS 1.0 and TLS 1.1, and requiring TLS 1.2 or greater, for the following LaunchDarkly endpoints:
* clientstream.launchdarkly.com
* events.launchdarkly.com
* stream.launchdarkly.com
Jun 15, 18:31 PDT
Update -
Today's TLSv1 brownout will start in 60 minutes (at 17:00 UTC) and last for approximately four hours (from 17:00-21:00 UTC).
Jun 15, 09:00 PDT
Update -
Today's TLSv1 brownout has concluded. The final planned window for temporary TLS 1.0/1.1 disablement is Wednesday, June 15: 17:00-21:00 UTC.
We intend to end support for TLS 1.0/1.1 on Wednesday, June 22.
Jun 8, 14:13 PDT
Update -
Today's TLSv1 brownout will start in 60 minutes (at 17:00 UTC) and last for approximately four hours (from 17:00-21:00 UTC).
Jun 8, 09:00 PDT
Update -
Today's TLSv1 brownout has concluded. The next planned windows for temporary TLS 1.0/1.1 disablement are
* Wednesday, June 8: 17:00-21:00 UTC
* Wednesday, June 15: 17:00-21:00 UTC.
We plan to end support for TLS 1.0/1.1 on Wednesday, June 22.
Jun 1, 18:12 PDT
Update -
Today's TLSv1 brownout will start in 60 minutes (at 17:00 UTC) and last for approximately four hours (from 17:00-21:00 UTC).
Jun 1, 09:02 PDT
Update -
Today's TLSv1 brownout has concluded. The next planned windows for temporary TLS 1.0/1.1 disablement are
* Wednesday, June 1: 17:00-21:00 UTC
* Wednesday, June 8: 17:00-21:00 UTC
May 25, 14:00 PDT
Update -
Today's TLSv1 brownout will start in 60 minutes (at 17:00 UTC) and last for approximately four hours (from 17:00-21:00 UTC).
May 25, 09:01 PDT
Update -
Today's TLSv1 controlled outage has concluded. The next planned windows for temporary TLS 1.0/1.1 disablement are:
* Wednesday, May 25: 17:00-21:00 UTC
* Wednesday, June 1: 17:00-21:00 UTC
* Wednesday, June 8: 17:00-21:00 UTC
May 18, 15:54 PDT
Update -
Today's TLSv1 controlled outage will start in 60 minutes (at 17:00 UTC) and last for approximately four hours (from 17:00-21:00 UTC).
May 18, 09:09 PDT
Update -
Today's TLSv1 brownout has concluded. The next planned windows for temporary TLS 1.0/1.1 disablement are
* Wednesday, May 18: 17:00-21:00 UTC
* Wednesday, May 25: 17:00-21:00 UTC
* Wednesday, June 1: 17:00-21:00 UTC
May 11, 15:11 PDT
Update -
Today's TLSv1 brownout will start in 60 minutes and last for approximately four hours.
May 11, 09:00 PDT
Update -
The next planned windows for temporary TLS 1.0/1.1 disablement are
* Wednesday, May 11: 17:00-21:00 UTC
* Wednesday, May 18: 17:00-21:00 UTC
* Wednesday, May 25: 17:00-21:00 UTC
* Wednesday, June 1: 17:00-21:00 UTC
May 9, 16:55 PDT
Update -
Today's TLSv1 brownout will start in 30 minutes and last for approximately four hours.
May 4, 09:30 PDT
Update -
Today's TLSv1 brownout will start in 45 minutes and last for approximately two hours.
Apr 26, 09:14 PDT
Update -
We have postponed requiring TLS 1.2 for the events and streaming endpoints until June 22, 2022, in order to allow more time for customers to update their services. We anticipate the new deadline will be the final deadline. As noted previously, the affected services are primarily .NET applications in legacy environments. We have notified affected customers by email and banners in the LaunchDarkly dashboard.
The next planned windows for temporary TLS 1.0/1.1 disablement are
* Tuesday, April 26: 17:00-19:00 UTC
* Wednesday, May 4: 17:00-21:00 UTC
Please feel free to contact LaunchDarkly Support with any questions or concerns.
Apr 22, 16:37 PDT
Update -
The first TLSv1 brownout will begin in one hour and last for approximately one hour.
Apr 13, 09:02 PDT
Update -
Today's TLSv1 brownout has concluded. The next planned windows for temporary TLS 1.0/1.1 disablement are
* Wednesday, April 13: 17:00-18:00 UTC
* Wednesday, April 20: 17:00-18:00 UTC
Apr 6, 11:18 PDT
Update -
The first TLSv1 brownout will begin in one hour and last for approximately one hour.
Apr 6, 08:59 PDT
Update -
The disablement window planned for March 30 has been canceled. The next planned windows for temporary TLS 1.0/1.1 disablement are
* Wednesday, April 6: 17:00-18:00 UTC
* Wednesday, April 13: 17:00-18:00 UTC
Mar 28, 11:42 PDT
Update -
The next planned windows for temporary TLS 1.0/1.1 disablement are
* Wednesday, March 30: 17:00-18:00 UTC
* Wednesday, April 6: 17:00-18:00 UTC
Mar 16, 16:43 PDT
Scheduled -
Currently, the LaunchDarkly dashboard (app.launchdarkly.com) requires TLS 1.2, but the events and streaming endpoints allow TLS versions 1.0, 1.1, and 1.2.
Starting April 26, 2022, we will be disabling TLS 1.0 and TLS 1.1, and requiring TLS 1.2 or greater, for the following LaunchDarkly endpoints:
* clientstream.launchdarkly.com
* events.launchdarkly.com
* stream.launchdarkly.com
This change would primarily affect applications using the LaunchDarkly .NET SDK in legacy environments. We are notifying affected customers by email and banners in the LaunchDarkly dashboard. In order to assist customers in locating affected services, we will periodically disable TLS 1.0/1.1 support for a brief window of time; we will announce these windows in advance on the status page.
Please feel free to contact LaunchDarkly Support with any questions or concerns.
Mar 16, 16:30 PDT