LaunchDarkly
All Systems Operational
API ? Operational
90 days ago
99.99 % uptime
Today
Streaming API ? Operational
90 days ago
99.99 % uptime
Today
Mobile Streaming API ? Operational
90 days ago
99.96 % uptime
Today
Web interface ? Operational
90 days ago
99.99 % uptime
Today
Feature flag CDN ? Operational
90 days ago
100.0 % uptime
Today
Non-core Services ? Operational
90 days ago
99.95 % uptime
Today
Event Ingestion ? Operational
Usage Metrics ? Operational
Experimentation Operational
Data Export ? Operational
Documentation ? Operational
90 days ago
100.0 % uptime
Today
Integrations ? Operational
90 days ago
99.92 % uptime
Today
Notifications ? Operational
90 days ago
99.94 % uptime
Today
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
Update - The TLS 1.0/1.1 disablement scheduled for November 1, 2021 has been postponed to give customers more time to update their applications to support TLS 1.2. We will communicate a new cutoff date soon.

In the meantime, we will continue to work with customers to advise which projects and applications are continuing to use TLS 1.0 or 1.1.
Oct 29, 17:11 PDT
Update - We will be undergoing scheduled maintenance during this time.
Aug 27, 14:04 PDT
Update - We will be undergoing scheduled maintenance during this time.
Aug 26, 22:19 PDT
Scheduled - Currently, the LaunchDarkly dashboard (app.launchdarkly.com) requires TLS 1.2, but the events and streaming API allow TLS versions 1.0, 1.1, and 1.2.

Starting November 1, 2021, 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

Our analysis indicates this change would primarily affect applications using the LaunchDarkly .NET SDK in legacy environments. On August 3, we sent an email to LaunchDarkly account owners and admins associated with projects we have observed making TLS 1.0/1.1 requests to our service. If you have not received a separate email notification, your application is already making requests using TLS 1.2 and will not be affected by this change.

Please feel free to contact LaunchDarkly Support with any questions or concerns.
Aug 4, 18:46 PDT
On February 1, 2022, LaunchDarkly will enable service support for the HTTP/2 protocol. This will increase the performance of our Flag Delivery Network for all customers.

However, Erlang SDK versions prior to 1.1.2 will no longer be able to connect to and communicate with LaunchDarkly. Versions 1.1.2+ of the Erlang SDK contain a change which will ensure the SDK continues to work once HTTP/2 requests are supported. Customers using affected Erlang SDK versions should upgrade their SDK to the latest version to avoid any problems.

No other LaunchDarkly SDKs are affected by this change, nor is any other LaunchDarkly functionality.

Please feel free to contact LaunchDarkly Support with any questions or concerns.
Posted on Dec 9, 11:32 PST
Past Incidents
Jan 22, 2022

No incidents reported today.

Jan 21, 2022
Resolved - This incident has been resolved.
Jan 21, 04:14 PST
Investigating - We're experiencing an elevated level of Streaming API errors and are currently looking into the issue.
Jan 21, 03:08 PST
Jan 20, 2022
Resolved - This incident has been resolved.
Jan 20, 13:30 PST
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 20, 13:07 PST
Update - We began seeing elevated errors from our client-side streaming at 11:52am PST. We are continuing to investigate this issue.
Jan 20, 12:49 PST
Investigating - We are seeing an elevated error rate from our Streaming API. Clients may see increased error rates and higher latency in flag updates.
Jan 20, 12:14 PST
Jan 19, 2022
Resolved - This incident has been resolved. We have backfilled events during the affected period and all experiment results should now be complete.
Jan 19, 15:52 PST
Update - Experiment Conversion events may be missing for running experiments 8:25pm - 10:25pm UTC. Please reach out via your preferred support channel if your experiments were affected and require data backfill.
Jan 19, 15:14 PST
Monitoring - A fix has been implemented and we are monitoring the results.
Jan 19, 14:45 PST
Identified - The issue has been identified and a fix is being implemented.
Jan 19, 14:26 PST
Investigating - Starting at 8:25PM UTC we are experiencing a delay in our experimentation results. We are currently investigating this issue.
Jan 19, 13:28 PST
Jan 18, 2022

No incidents reported.

Jan 17, 2022

No incidents reported.

Jan 16, 2022

No incidents reported.

Jan 15, 2022

No incidents reported.

Jan 14, 2022

No incidents reported.

Jan 13, 2022

No incidents reported.

Jan 12, 2022

No incidents reported.

Jan 11, 2022

No incidents reported.

Jan 10, 2022

No incidents reported.

Jan 9, 2022

No incidents reported.

Jan 8, 2022

No incidents reported.