Live

Elevated 5xx Errors (15:11–15:32 UTC)

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.

The latest update from LaunchDarkly.

State

Resolved

Started

17 d ago

2026-10-15 15:47 UTC

Lasted

1 min

until 2026-10-15 15:47 UTC

Worst impact

Degraded

Timeline

1 update
15:4715:4715:4715:4815:48
NoticeUpdate postedTimes in UTC

Resolved

1 min 100%

Updates

Times in UTC

As posted by LaunchDarkly

Resolved2026-10-15 15:47 UTC

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.

Affected components

10
Feature workflowsFlag targetingSegment managementProgressive rolloutsRelease pipelinesFeature management (core functionality) - Feature workflowsFeature management (core functionality) - Flag targetingFeature management (core functionality) - Segment management

LaunchDarkly in the last 90 days

Full history
90 days agoToday

Incidents in 90 days

9

Days with an incident

9

Median duration

1 h 15 min

This incident

100% shorter than the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

18 h 55 min
median 1 h 15 min
90 days agoToday

Other LaunchDarkly incidents

All incidents
LaunchDarkly logo

LaunchDarkly·delayed event processing

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.

Resolvedresolved 5 d ago
LaunchDarkly logo

LaunchDarkly·Delays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation

This incident has been resolved.

Resolvedresolved 29 d ago
LaunchDarkly logo

LaunchDarkly·Elevated error rates in the LaunchDarkly application

This incident has been resolved.

Resolvedresolved 29 d ago
LaunchDarkly logo

LaunchDarkly·Flag delivery errors in Streaming API

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.

Resolvedresolved 67 d ago
LaunchDarkly logo

LaunchDarkly·Email delivery failure affecting sign-up verification and notification emails

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.

Resolvedresolved 69 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.cc/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.cc/feed.xml?providers=launchdarkly
Slack
/feed subscribe https://outages.cc/feed.xml?providers=launchdarkly

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane