outages.live
Live
LaunchDarkly logo

LaunchDarkly

LaunchDarkly is operational

Checked 15 s ago Operational

History

90 days agoToday

Incidents in 90 days

9

Days with an incident

9

Median duration

1 h 15 min

Longest incident

18 h 55 min

Components

39

Flag Delivery Network (core functionality)

Server-side streaming API Operational
90 days ago1 day with an incidentToday
Client-side streaming API Operational
90 days ago1 day with an incidentToday
Polling API Operational
90 days ago1 day with an incidentToday
Edge API Operational
90 days agoNo incidentsToday

Automations (non-core functionality)

Emails and notifications Operational
90 days agoNo incidentsToday
Integrations and webhooks Operational
90 days agoNo incidentsToday
Expiring Contexts Targets Operational
90 days agoNo incidentsToday

Feature management (core functionality)

Feature workflows Operational
90 days ago1 day with an incidentToday
Flag targeting Operational
90 days ago1 day with an incidentToday
Segment management Operational
90 days ago1 day with an incidentToday
Progressive rollouts Operational
90 days ago1 day with an incidentToday
Release pipelines Operational
90 days ago2 days with an incidentToday

Global (non-core functionality)

Audit log Operational
90 days agoNo incidentsToday

Experimentation (core functionality)

Experiment management Operational
90 days ago1 day with an incidentToday
Experiment results processing Operational
90 days ago1 day with an incidentToday
Experiment results analysis Operational
90 days agoNo incidentsToday
Warehouse native experimentation Operational
90 days agoNo incidentsToday

Experimentation (non-core functionality)

Past experiment iterations Operational
90 days agoNo incidentsToday

Global (core functionality)

Authentication Operational
90 days agoNo incidentsToday
Metrics Operational
90 days ago1 day with an incidentToday
Web app (app.launchdarkly.com) Operational
90 days ago2 days with an incidentToday

Feature management (non-core functionality)

Context processing Operational
90 days agoNo incidentsToday
Data Export Operational
90 days agoNo incidentsToday
Flag usage metrics Operational
90 days ago1 day with an incidentToday

Past incidents

Provider status pageTimes in UTC

Oct 26, 2026

Duration1 min20:52 to 20:52delayed event processingDegraded

A scaling inflection point in our realtime event warehouse led to a delay for some event ingestion. The engineering team has remediated the problem and all events should be caught up. Some customers may have seen delays in experiments and in guarded release processing. This is now resolved and the team will carefully monitor.

Oct 15, 2026

Duration1 min15:47 to 15:47Elevated 5xx Errors (15:11–15:32 UTC)Degraded

Between 15:11 and 15:32 UTC today, we observed elevated 5xx errors affecting requests across our services. Approximately 0.7% of requests failed during this period (99.3% succeeded). This incident has been resolved.

Oct 3, 2026

Duration1 h 37 min07:29 to 09:06Delays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and ExperimentationDegraded

This incident has been resolved.

Oct 2, 2026

Duration18 h 55 min14:10 to 09:05Elevated error rates in the LaunchDarkly applicationDegraded

This incident has been resolved.

Aug 26, 2026

Duration1 min20:00 to 20:00Flag delivery errors in Streaming APIDegraded

This incident has been resolved. Between 12:00 and 12:12 PM PDT on August 26, server-side SDKs establishing new streaming connections experienced elevated error rates. Existing streaming connections were not affected, and polling requests continued to be served with error rates below 1%. Some requests to the LaunchDarkly web application also experienced elevated errors between approximately 11:29 AM and 12:03 PM PDT. The issue was caused by an internal configuration change, which has been reverted. All systems have recovered and are operating normally. No customer data was lost or compromised.

Aug 24, 2026

Duration1 h 15 min12:20 to 13:36Email delivery failure affecting sign-up verification and notification emailsDegraded

Email delivery has been restored as of 2:32 PM UTC. Sign-up verification, password reset, teammate invitation, and notification emails are sending normally again. We are re-sending sign-up verification and password reset emails that failed to deliver during the incident window (August 22, 11:48 PM CDT through today). If you attempted to sign up or reset a password during that period and haven't received an email within the next few hours, please retry the action or contact support. We are continuing to monitor email delivery closely and will post a final update once we've confirmed sustained recovery.

Aug 17, 2026

Duration5 h 26 min10:36 to 16:03Flag Updates via Polling API delayedDegraded

This incident has been resolved.

Aug 14, 2026

Duration2 h14:47 to 16:47Flag Updates delayed in US RegionDegraded

The issue is being marked as resolved. We're seeing improved latencies and our systems have recovered.

Aug 7, 2026

Duration46 min19:29 to 20:15Elevated errors on server-side SDK streaming connectionsDegraded

SDKs restored to operational

Maintenance

Planned Upcoming API Versions Retirement

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.

Maintenancestarts in 59 d

Action Recommended: Update SDKs and Relay Proxy for eMudhra CA Issue

Scheduled maintenance is currently in progress. We will provide updates as necessary.

Maintenanceupdated 6 d ago

Follow LaunchDarkly

Your coding agent knows when LaunchDarkly is down, and tells you when a failure is theirs, not yours. You can also get LaunchDarkly incidents in a feed reader or in Slack.

Prompt
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.

Add it as a remote MCP server named "outages" at https://outages.live/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.

Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "launchdarkly" and tell me if LaunchDarkly has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.

Paste this into any coding agent. It adds the server with its own MCP setup.

RSS
https://outages.live/feed.xml?providers=launchdarkly
Slack
/feed subscribe https://outages.live/feed.xml?providers=launchdarkly

Go from tracking outages to fixing production issues with Polylane.

Try Polylane