LaunchDarkly
All Systems Operational
Flag Delivery Network ? Operational
90 days ago
100.0 % uptime
Today
Server-side streaming API ? Operational
90 days ago
100.0 % uptime
Today
Client-side streaming API ? Operational
90 days ago
100.0 % uptime
Today
Polling API ? Operational
90 days ago
100.0 % uptime
Today
Feature management (core functionality) ? Operational
90 days ago
99.94 % uptime
Today
Feature workflows ? Operational
90 days ago
99.92 % uptime
Today
Flag targeting ? Operational
90 days ago
99.96 % uptime
Today
Feature management (non-core functionality) ? Operational
Audit log ? Operational
Data Export ? Operational
Emails and notifications ? Operational
Flag usage metrics ? Operational
Account management ? Operational
Documentation ? Operational
Experimentation ? Operational
Integrations and webhooks ? Operational
SDKs ? Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
During the month of June 2022, the following SDK versions will reach their end of life in accordance with LaunchDarkly's End of Life policy (https://launchdarkly.com/policies/end-of-life-policy).

- .NET server-side SDK 5.14.x
- .NET server-side SDK 6.0.x
- C server-side SDK 2.3.x
- Go server-side SDK 5.3.x
- Haskell server-side SDK 2.1.x
- Java server-side SDK 5.4.x
- Node.js server-side SDK 5.14.x
- Node.js server-side SDK 6.0.x
- PHP server-side SDK 3.8.x
- Python server-side SDK 7.1.x
- Ruby server-side SDK 6.1.x

Customers using these or older SDK versions should update to supported SDK versions. For more information, read about our supported SDK versions (https://docs.launchdarkly.com/sdk/concepts/versioning#supported-versions).

Posted on Jun 1, 09:38 PDT
Past Incidents
Jun 24, 2022

No incidents reported today.

Jun 23, 2022

No incidents reported.

Jun 22, 2022
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 - For guidance on how to resolve TLS 1.2 support for applications using the LaunchDarkly .NET SDK, see https://docs.launchdarkly.com/sdk/server-side/dotnet#transport-layer-security-tls-and-other-networking-issues.
Mar 28, 11:41 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
Jun 21, 2022

No incidents reported.

Jun 20, 2022

No incidents reported.

Jun 19, 2022

No incidents reported.

Jun 18, 2022

No incidents reported.

Jun 17, 2022
Resolved - We had experienced elevated client stream connection errors between 14:39 UTC - 15:56 UTC. Client-side SDK connecting around this time could see errors in logs and fallback to cached or default flag values. The issue is now resolved.
Jun 17, 14:40 PDT
Identified - The issue has been identified and a fix is being implemented.
Jun 17, 09:35 PDT
Investigating - We're experiencing an elevated level of client stream connection errors. Client-side SDK connecting right now could see errors in logs and fallback to cached or default flag values. We are currently looking into the issue.
Jun 17, 08:03 PDT
Resolved - This incident has been resolved.
Jun 17, 14:10 PDT
Identified - The issue has been identified and a fix is being implemented.
Jun 17, 08:58 PDT
Investigating - Creating expiring user targets resulted in errors and we are currently looking into the issue.
Jun 17, 08:46 PDT
Jun 16, 2022
Resolved - We had experienced elevated client stream connection errors between 19:38 UTC - 20:17 UTC. Client-side SDK connecting around this time could see errors in logs and fallback to cached or default flag values. The issue is now resolved.
Jun 16, 12:30 PDT
Jun 15, 2022
Resolved - The root cause is addressed and the incident has been resolved
Jun 15, 08:31 PDT
Identified - We had experiencing an elevated level of evaluation endpoint errors that impacts the SDKs between 11:30 - 14:00 UTC.
Jun 15, 08:30 PDT
Investigating - We're experiencing an elevated level of evaluation endpoint errors that impacts the Client-side SDKs and are currently looking into the issue.
Jun 15, 08:01 PDT
Resolved - We had experienced elevated API error between 11:30AM-11:38AM UTC. We've identified the issue and implemented a fix. The issue is resolved.
Jun 15, 05:23 PDT
Monitoring - We had experienced elevated API error between 11:30AM-11:38AM UTC. We've identified the issue and implemented a fix. We are monitoring the issue
Jun 15, 05:12 PDT
Jun 14, 2022
Resolved - We have deployed a fix and the incident has been resolved.
Jun 14, 08:32 PDT
Identified - The issue has been identified and a fix is being implemented.
Jun 14, 06:38 PDT
Investigating - We have one user reporting that Feature Flags page is not accessible. We are currently investigating.
Jun 14, 06:02 PDT
Jun 13, 2022

No incidents reported.

Jun 12, 2022

No incidents reported.

Jun 11, 2022

No incidents reported.

Jun 10, 2022

No incidents reported.