LaunchDarkly
All Systems Operational
API ? Operational
90 days ago
99.99 % uptime
Today
Streaming API ? Operational
90 days ago
100.0 % uptime
Today
Mobile Streaming API ? Operational
90 days ago
100.0 % uptime
Today
Web interface ? Operational
90 days ago
99.93 % uptime
Today
Feature flag CDN ? Operational
90 days ago
100.0 % uptime
Today
Non-core Services ? Operational
90 days ago
99.99 % uptime
Today
Event Ingestion ? Operational
Analytics Data Stream ? Operational
Usage Metrics ? Operational
Experimentation Operational
Data Export ? Operational
Documentation ? Operational
90 days ago
99.99 % uptime
Today
Integrations ? Operational
90 days ago
100.0 % uptime
Today
Notifications ? 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.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
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
Past Incidents
Oct 24, 2021

No incidents reported today.

Oct 23, 2021

No incidents reported.

Oct 22, 2021

No incidents reported.

Oct 21, 2021

No incidents reported.

Oct 20, 2021

No incidents reported.

Oct 19, 2021
Resolved - This incident has been resolved. Note that flags continued to be served correctly for customers using big segments during this incident.
Oct 19, 12:28 PDT
Monitoring - A fix has been implemented and we are monitoring results.
Oct 19, 11:04 PDT
Identified - Customers are experiencing errors when fetching big segments. We have identified the issue and are working on a fix.
Oct 19, 10:48 PDT
Oct 18, 2021

No incidents reported.

Oct 17, 2021

No incidents reported.

Oct 16, 2021

No incidents reported.

Oct 15, 2021

No incidents reported.

Oct 14, 2021

No incidents reported.

Oct 13, 2021

No incidents reported.

Oct 12, 2021
Resolved - Earlier today we released JavaScript SDK 2.19.3. When we realized the release was broken, we deprecated the release and took it down. For a few hours, the unpkg CDN was caching an invalid URL. After rolling forward with a 2.19.4 release, the unpkg CDN is now returning a valid JS SDK release.

Note that we do not recommend depending on open-source CDNs for serving the LaunchDarkly SDK in production environments.
Oct 12, 21:10 PDT
Oct 11, 2021

No incidents reported.

Oct 10, 2021

No incidents reported.