LaunchDarkly Status

LaunchDarkly

All Systems Operational

Uptime over the past 90 days. View historical uptime.

API Operational

90 days ago

99.98 % 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.97 % 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

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

Notifications Operational

90 days ago

100.0 % uptime

Today

Operational

Degraded Performance

Partial Outage

Major Outage

Maintenance

Scheduled Maintenance

Postponed: Planned deprecation of TLS 1.0/1.1 for LaunchDarkly endpoints Nov 1, 11:00-12:00 PST

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

Past Incidents

Dec 6, 2021

No incidents reported today.

Dec 5, 2021

No incidents reported.

Dec 4, 2021

Event Processing Delays

Resolved - This incident has been resolved.
Dec 4, 21:00 PST

Monitoring - A fix has been implemented and the system is catching up with the delayed data..
Dec 3, 17:00 PST

Update - We are continuing to process the backlog of Flag Insights data.
Dec 3, 16:40 PST

Identified - Flag Insights data is delayed.
Dec 3, 11:05 PST

Monitoring - A fix has been implemented. Our event infrastructure has processed the backlog and caught up.
Dec 3, 10:30 PST

Investigating - Our event processing infrastructure is running behind which may cause stale data to be shown in the application. We are working on a fix. No data has been lost and the system should be caught up shortly.
Dec 3, 10:18 PST

Dec 3, 2021

Dec 2, 2021

No incidents reported.

Dec 1, 2021

No incidents reported.

Nov 30, 2021

No incidents reported.

Nov 29, 2021

No incidents reported.

Nov 28, 2021

No incidents reported.

Nov 27, 2021

No incidents reported.

Nov 26, 2021

No incidents reported.

Nov 25, 2021

No incidents reported.

Nov 24, 2021

Missing last seen data for members

Resolved - We are not planning additional work on this issue over the US Thanksgiving holiday weekend. We will update the status of any additional remediations by EOD Pacific Time on Monday, November 29th.
Nov 24, 19:15 PST

Identified - We have identified an issue with missing "lastSeen" times for members last visiting the site and access tokens last used prior to November 12, 2021. We have restored "lastSeen" timestamps for members who accessed via the web interface prior to November 12. "lastSeen" timestamps that should be dated before November 12 are still missing from API, leading to some members being shown as never having visited the site and some access tokens shown as never having been used. "lastSeen" timestamps for members who have used the site via the web or an access token since November 12 are accurate. "lastSeen" timestamps for access tokens that have been used since November 12 are also accurate.

We are continuing to work to restore "lastSeen" timestamps for members and access tokens that would be based purely on access token accesses prior to November 12.
Nov 24, 18:38 PST

Investigating - We are investigating an issue around missing data for members' last activity. Currently this field is absent for all members and API tokens which have not been used since Friday, Nov 12 at 4:24PM PST.
Nov 24, 14:30 PST

Nov 23, 2021

No incidents reported.

Nov 22, 2021

No incidents reported.

Related