LaunchDarkly

All Systems Operational

Uptime over the past 90 days. View historical uptime.
Flag Delivery Network (core functionality) Operational
90 days ago
100.0 % uptime
Today
Server-side streaming API Operational
90 days ago
100.0 % uptime
Today
Client-side streaming API Operational
90 days ago
100.0 % uptime
Today
Polling API Operational
90 days ago
100.0 % uptime
Today
Edge API Operational
90 days ago
100.0 % uptime
Today
Feature management (core functionality) Operational
90 days ago
100.0 % uptime
Today
Feature workflows Operational
90 days ago
100.0 % uptime
Today
Flag targeting Operational
90 days ago
100.0 % uptime
Today
Segment management Operational
90 days ago
100.0 % uptime
Today
Progressive rollouts Operational
90 days ago
100.0 % uptime
Today
Release pipelines Operational
90 days ago
100.0 % uptime
Today
Experimentation (core functionality) Operational
90 days ago
99.99 % uptime
Today
Experiment management Operational
90 days ago
100.0 % uptime
Today
Experiment results processing Operational
90 days ago
100.0 % uptime
Today
Experiment results analysis Operational
90 days ago
99.97 % uptime
Today
Warehouse native experimentation Operational
90 days ago
100.0 % uptime
Today
Guarded Rollouts (core functionality) Operational
90 days ago
100.0 % uptime
Today
Rollout management Operational
90 days ago
100.0 % uptime
Today
Rollout results processing Operational
90 days ago
100.0 % uptime
Today
Rollout results analysis Operational
90 days ago
100.0 % uptime
Today
Global (core functionality) Operational
90 days ago
99.98 % uptime
Today
Authentication Operational
90 days ago
99.98 % uptime
Today
Metrics Operational
90 days ago
100.0 % uptime
Today
Web app (app.launchdarkly.com) Operational
90 days ago
99.98 % uptime
Today
Observability (core functionality) Operational
90 days ago
100.0 % uptime
Today
Frontend Operational
90 days ago
100.0 % uptime
Today
Query API Operational
90 days ago
100.0 % uptime
Today
Observability Data Ingest (Sessions, Errors) Operational
90 days ago
100.0 % uptime
Today
OpenTelemetry (Logs, Traces, Metrics) Operational
90 days ago
100.0 % uptime
Today
Feature management (non-core functionality) Operational
Context processing Operational
Data Export Operational
Flag usage metrics Operational
Experimentation (non-core functionality) Operational
Past experiment iterations Operational
AI Configs (non-core functionality) Operational
AI Config management Operational
Global (non-core functionality) Operational
Audit log Operational
Automations (non-core functionality) Operational
Emails and notifications Operational
Integrations and webhooks Operational
Expiring Contexts Targets Operational
Websites (non-core functionality) Operational
Docs (launchdarkly.com/docs) Operational
Website (launchdarkly.com) Operational
Account management Operational
SDKs Operational
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.

No incidents or maintenance related to this downtime.

Scheduled Maintenance

Planned Upcoming API Versions Retirement Dec 31, 2026 01:00-09:00 PST

As part of our commitment to reliability and security, LaunchDarkly will retire all API versions except 20240415 on December 31, 2026.

After this date, all requests made to retired versions will stop working. To avoid disruption, customers must update integrations and workflows to use version 20240415 before the retirement date.

We previously announced the end of life (EOL) for older versions as of April 30, 2025. They have remained available during a grace period, which will end on December 31, 2026

For full details, see our API version changelog: https://launchdarkly.com/docs/api#api-version-changelog

Upgrading now ensures uninterrupted access and provides immediate improvements in performance and functionality.

We recognize this may be a large undertaking, which is why we are providing extended notice. If you need guidance, please reach out to your account team or contact our support team.
Posted on Aug 25, 2025 - 11:43 PDT
Feb 26, 2026
Investigating Issues with LaunchDarkly Application and Authentication
Resolved - The issue with our application and authentication has been resolved. Performance has remained stable following mitigation.
Feb 26, 09:06 PST
Update - The issue with our application and authentication has been resolved. Performance has remained stable following mitigation.
Feb 26, 09:04 PST
Monitoring - The issue with our application and authentication has been identified and a fix has been implemented. We are continuing to monitor the performance of impacted services. We will continue to update this page until it is resolved.
Feb 26, 08:42 PST
Identified - Some customers are experiencing issues with accessing the web app and authentication. Some customers may see a low number of errors with flag evaluation, as well, but generally our Flag Delivery Network is functional. We have identified the issue and are continuing our work to resolve it.
Feb 26, 08:17 PST
Investigating - Some customers are experiencing issues with accessing the web app and authentication. We are investigating and will provide updates as they become available.
Feb 26, 07:43 PST
Feb 25, 2026

No incidents reported.

Feb 24, 2026

No incidents reported.

Feb 23, 2026

No incidents reported.

Feb 22, 2026

No incidents reported.

Feb 21, 2026

No incidents reported.

Feb 20, 2026
Degraded Observability Ingest
Resolved - Ingest performance has remained stable following mitigation. We are no longer observing impact.
Feb 20, 15:04 PST
Monitoring - Mitigation has been applied and ingest performance has stabilized. We are monitoring to ensure continued stability.
Feb 20, 14:13 PST
Identified - We have identified the cause of the degraded ingest performance and are applying mitigation. We are seeing signs of stabilization and continuing to monitor recovery.
Feb 20, 14:12 PST
Investigating - Beginning around 1:25 PM PST, we are investigating degraded ingest performance. Some customers may experience delays or gaps in observability data. Updates to follow.
Feb 20, 14:02 PST
IP address updates for stream.launchdarkly.com
Completed - The scheduled maintenance has been completed.
Feb 20, 13:28 PST
Scheduled - We are adding additional CIDR ranges (IP ranges) for stream.launchdarkly.com to our public IP list. Some customers may need to update IP allowlists in their firewalls or proxy servers in order for their services to continue establishing streaming connections from server side SDKs to LaunchDarkly without disruption. Please refer to documentation at https://docs.launchdarkly.com/home/advanced/public-ip-list for more information.

Added CIDR ranges:
-3.41.176.128/26
- 3.40.135.64/26
- 3.44.4.128/26
Feb 6, 13:18 PST
Feb 19, 2026
Observability Data Delay
Resolved - We've caught up on the session/error data backlog.
Feb 19, 08:09 PST
Identified - We've identified the root cause and have deployed a fix. We're catching up on the session/error data backlog and should be caught up in ~15 minutes. No data has been lost.
Feb 19, 07:54 PST
Investigating - Sessions and errors may be delayed by up to 1 hours. We are investigating the root cause. No data is lost.
Feb 19, 07:39 PST
Feb 18, 2026

No incidents reported.

Feb 17, 2026

No incidents reported.

Feb 16, 2026

No incidents reported.

Feb 15, 2026

No incidents reported.

Feb 14, 2026

No incidents reported.

Feb 13, 2026

No incidents reported.

Feb 12, 2026
Data attribution issues with Experimentation
Resolved - We have fixed the data attribution issues where running experiment iterations were receiving incorrectly attributed data. This incident is now resolved and results for active experiments are now accurate.
Feb 12, 19:39 PST
Update - We have fixed the data attribution issues where certain experiment iterations are receiving incorrectly attributed data for any new experiments that are created.
We are fixing the data attribution error for active experiments.
Feb 12, 18:38 PST
Identified - The team has identified the root cause and is working on a fix.
Feb 12, 17:32 PST
Investigating - We are investigating an issue where certain experiment iterations are receiving incorrectly attributed data.
Feb 12, 16:30 PST
← Incident History Powered by Atlassian Statuspage