Flag Updates delayed in US Region
The issue is being marked as resolved. We're seeing improved latencies and our systems have recovered.
The latest update from LaunchDarkly.
State
Resolved
Started
79 d ago
2026-08-14 14:47 UTC
Lasted
2 h
until 2026-08-14 16:47 UTC
Worst impact
Degraded
Timeline
3 updatesInvestigating
1 h 18 min 65%
Monitoring
43 min 35%
Updates
Times in UTCAs posted by LaunchDarkly
The issue is being marked as resolved. We're seeing improved latencies and our systems have recovered.
We investigated elevated error rates reported for mobile SDK flag delivery in US East. We've confirmed that flag delivery itself was not impacted. No customer action is required and we are monitoring the situation.
Flag Updates are currently delayed in the us-east-1 region. We are investigating the issue.
Affected components
2LaunchDarkly in the last 90 days
Full historyIncidents in 90 days
9
Days with an incident
9
Median duration
1 h 15 min
This incident
1.6× the median
Other LaunchDarkly incidents
All incidents
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.
LaunchDarkly·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.
LaunchDarkly·Delays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation
This incident has been resolved.
LaunchDarkly·Elevated error rates in the LaunchDarkly application
This incident has been resolved.
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.
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.
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.
https://outages.cc/feed.xml?providers=launchdarkly/feed subscribe https://outages.cc/feed.xml?providers=launchdarklyFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane