LaunchDarkly
All Systems Operational
API ? Operational
90 days ago
100.0 % uptime
Today
Streaming API ? Operational
90 days ago
99.98 % uptime
Today
Mobile Streaming API ? Operational
90 days ago
99.99 % uptime
Today
Web interface ? Operational
90 days ago
100.0 % uptime
Today
Feature flag CDN ? Operational
90 days ago
100.0 % uptime
Today
Non-core Services ? Operational
90 days ago
100.0 % uptime
Today
Event Ingestion ? Operational
Analytics Data Stream ? Operational
Usage Metrics ? Operational
Experimentation Operational
Data Export ? Operational
Documentation ? Operational
90 days ago
100.0 % uptime
Today
Integrations ? Operational
90 days ago
100.0 % uptime
Today
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
had a major outage
had a partial outage
Past Incidents
Jun 6, 2020

No incidents reported today.

Jun 5, 2020

No incidents reported.

Jun 4, 2020

No incidents reported.

Jun 3, 2020

No incidents reported.

Jun 2, 2020

No incidents reported.

Jun 1, 2020
Completed - The scheduled maintenance has been completed.
Jun 1, 18:39 PDT
In progress - app.launchdarkly.com has been updated to require TLSv1.2 for all requests.
Jun 1, 12:10 PDT
Update - The TLS deadline was extended to June 1, 2020.
May 5, 13:56 PDT
Update - The TLS deadline was extended to May 5, 2020.
Apr 16, 14:32 PDT
Update - The TLS deadline was extended to April 17, 2020.
Mar 31, 14:44 PDT
Scheduled - Currently, the LaunchDarkly service secures connections using TLS versions 1.0, 1.1, and 1.2. For customers making a significant number of web connections using TLS 1.0 or 1.1, LaunchDarkly's Support and Customer Success teams will be there to help move toward better network security.

Read more at https://launchdarkly.com/blog/raising-the-security-bar-with-tls-1-2/.
Feb 11, 17:30 PST
May 31, 2020

No incidents reported.

May 30, 2020

No incidents reported.

May 29, 2020
Resolved - This incident has been resolved. At around 10pm, we changed our certificate bundle to exclude “AddTrust External CA Root” which is scheduled to expire in a few hours and whose continued presence would interfere with connectivity to our Roku clients (see https://community.roku.com/t5/Roku-Developer-Program/Potential-service-disruption-Upcoming-SSL-certificate-expiration-could-impact-channel-operations/td-p/567871). We subsequently observed an increase in TLS negotiation failures. On investigation, we discovered that the new certificate bundle contained a valid chain that worked for all clients on most platforms but some clients on some platforms were unable to complete a valid trust chain without the presence of the removed, expiring certificate. At just after 11pm, we introduced a new intermediate certificate into our certificate bundle. This change allowed the remaining clients to establish a valid trust chain and restore their connection to our service.
May 29, 23:36 PDT
Monitoring - A fix has been implemented and we are monitoring the results.
May 29, 23:22 PDT
Investigating - Some clients are experiencing connection errors due to a change in our TLS configuration. We are investigating and will update when the issue is resolved.
May 29, 23:00 PDT
May 28, 2020
Resolved - This incident has been resolved.
May 28, 21:42 PDT
Monitoring - A fix has been implemented and we are monitoring the users API. It may be a few minutes before previously received user data is available from the API.
May 28, 19:34 PDT
Identified - We have identified the cause of the user indexing slowness and are working on a fix.
May 28, 19:24 PDT
Investigating - API requests for users are slow and indexing of new user data is delayed. We are investigating.
May 28, 19:18 PDT
May 27, 2020

No incidents reported.

May 26, 2020

No incidents reported.

May 25, 2020

No incidents reported.

May 24, 2020

No incidents reported.

May 23, 2020

No incidents reported.