LaunchDarkly
All Systems Operational
API ? Operational
90 days ago
99.96 % 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.94 % uptime
Today
Feature flag CDN ? Operational
90 days ago
99.96 % 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.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
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 August 31, 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.
Posted on Aug 4, 18:46 PDT
Past Incidents
Aug 5, 2021

No incidents reported today.

Aug 4, 2021

No incidents reported.

Aug 3, 2021

No incidents reported.

Aug 2, 2021

No incidents reported.

Aug 1, 2021

No incidents reported.

Jul 31, 2021

No incidents reported.

Jul 30, 2021
Resolved - All of the missing usage and insights data has been restored.
Jul 30, 20:08 PDT
Update - We are restoring missing data associated with the usage and insights features of our product. There is partial data between 7-29 17:15 UTC and 7-30 3:15 UTC for these features. Our core service remains operational and no data has been lost.
We’re currently recovering the data for that period, but it may appear to be incomplete through Saturday as our backfill completes.
Jul 29, 22:23 PDT
Update - We are continuing to work on a fix for this issue.
Jul 29, 17:38 PDT
Identified - We have identified the issue causing flag insights and usage data to be delayed. We expect the delays to be resolved later today. We will provide another update by 6pm PT.
Jul 29, 13:10 PDT
Investigating - We are currently investigating this issue.
Jul 29, 10:46 PDT
Jul 29, 2021
Jul 28, 2021

No incidents reported.

Jul 27, 2021
Resolved - This incident has been resolved.
Jul 27, 08:56 PDT
Monitoring - A fix has been implemented and we are monitoring the results.
Jul 27, 08:54 PDT
Update - We are continuing to work on a fix for this issue.
Jul 27, 07:58 PDT
Identified - The issue has been identified and a fix is being implemented.
Jul 27, 07:57 PDT
Update - We are continuing to investigate this issue.
Jul 27, 07:57 PDT
Investigating - We have identified an issue that prevents flags from being updated via our UI.
Jul 27, 07:55 PDT
Jul 26, 2021

No incidents reported.

Jul 25, 2021

No incidents reported.

Jul 24, 2021

No incidents reported.

Jul 23, 2021

No incidents reported.

Jul 22, 2021

No incidents reported.