Last updated: November 11, 2026
Is LaunchDarkly down? User reports show no current problems with LaunchDarkly
LaunchDarkly is a feature management platform that lets engineering teams turn features on and off with flags instead of new code releases. This page tracks the live LaunchDarkly status, outage reports and the flag delivery problems teams report most.
Report a problem !
Select which issue applies
LaunchDarkly problems reported in the last 24 hours
Most reported problems
All quiet. No issues reported in the last 24 hours.
Your feedback
How would you rate LaunchDarkly over the past 3 months?
Most reported locations
Where LaunchDarkly reports are coming from in the last 24 hours.
No problem locations to show yet. LaunchDarkly looks fine right now. Locations appear here as soon as users submit reports.
Latest LaunchDarkly user reports
No reports yet — be the first to report a problem above.
LaunchDarkly outage history
Our latest check and the live report status for LaunchDarkly.
✓ Our latest check (10 November 2026, 9:51 AM PKT): launchdarkly.com answered normally in 118 ms.
Good news. LaunchDarkly has no reported problems right now. If it is not working for you, report it above and your report will appear here.
LaunchDarkly uptime and reports
Live report counts and the day by day record for the last 30 days.
User reports received in each period.
Last 30 days, day by day: 12 October 2026 to 10 November 2026
Green: up. Red: outage. Amber: some checks failed. Grey: no record yet.
The daily record builds from today as our checks run. Grey days have no saved record yet. A red day marks a confirmed outage.
Get LaunchDarkly down alerts
Leave your email and we will tell you when LaunchDarkly is having problems, and when it is back up. No spam.
LaunchDarkly on social media
An early signal from outside our site, watched in rotation.
Posts on Bluesky saying LaunchDarkly is down. Checked 11 November 2026, 12:06 AM PKT.
Quiet right now. Nobody on Bluesky is saying LaunchDarkly is down.
- @flarestart.bsky.social 26 Feb, 9:34 PM PKT
LaunchDarkly Is Down Again — And That's a Problem via Dev.to Webdev #DevNews #WebDevelopment
Guides that can fix it
Step by step fixes for the problems people report most.
→ An App Is Not Working? Fixes for Android and iPhone
→ Login Problems That Are Not an Outage
→ How to Clear the Cache in Firefox, Safari and Edge
Is LaunchDarkly Down Right Now?
No, LaunchDarkly is not down for everyone right now. The live LaunchDarkly status above tracks user reports, and flag delivery is working normally for most teams at the moment.
LaunchDarkly is the feature flag platform used by engineering teams to roll out code safely. When a LaunchDarkly outage happens, SDKs stop getting fresh flag values and apps fall back to default behavior. Reports here help you tell an incident apart from a bug in your own setup.
Is LaunchDarkly Down for Me or Everyone?
Did every service stop updating flags at the same time? If yes, it is likely a real incident on the delivery side. If only one app misbehaves, the problem is local, like a stale cache or a wrong SDK key. The chart above shows which pattern other teams see. The next step for many readers is simple, they pull up Leonardo AI and compare the picture.
Why Are My Flags Not Updating?
The classic cause is a stale SDK cache. Server SDKs keep flag values in memory and refresh them over a streaming connection. If that connection drops, the SDK serves the last values it received, so dashboard changes never reach the app.
A restart fixes more cases than teams expect. After some incidents, SDKs that connected during the bad window stay stuck until the app restarts. Check your logs for unauthorized or 401 messages from that window.
Why Does My App Get Fallback Values?
Fallback values appear when the SDK has no flag data yet or cannot reach LaunchDarkly at all. Evaluating a flag before the SDK finishes starting is the most common trigger. The evaluation reason then shows a client not ready error.
A wrong SDK key does the same damage in silence. Using a key from the wrong environment, or a client side ID in a server SDK, leaves the app with no matching flags. The evaluation then returns your coded default every single time.
Why Do Old Variations Still Show in My Analytics?
Old app versions are the usual answer. Devices and servers running last month’s build keep evaluating flags the old way and keep sending those events. Even a small share of old builds can put a retired variation on your graph every day.
Offline contexts play a part too. Mobile SDKs cache flag values while a device is offline. When it reconnects, it sends evaluations from that cache until fresh data arrives.
Common LaunchDarkly Problems and Fixes
Flag Changes Not Reaching the App
Restart the application or the Relay Proxy to force a fresh connection. Then change the flag again and watch the evaluation in the debugger. If updates flow after the restart, the old connection was stuck.
SDK Returns Client Not Ready
Wait for the SDK to finish starting before you evaluate any flag. Use the ready signal your SDK offers. This removes the race between startup and the first flag check.
Flag Shows as Not Found
Check the flag key in your code against the key in the dashboard, letter for letter. Also confirm the SDK key belongs to the same environment as the flag. A key from another environment causes this error.
Wrong Variation Type Error
Match the variation method to the flag type. A mismatch returns an error kind instead of a value.
Relay Proxy Stops Syncing
Restart the Relay Proxy first, then check that it can reach the flag delivery network. Review its logs for 401 or unauthorized messages. Those point to a key or connection problem, not a flag problem.
Having a problem with LaunchDarkly?
Comments are public and help others understand the issue.
Frequently Asked Questions
Why is my LaunchDarkly flag not updating in production?
The SDK is usually serving a stale cache after its streaming connection dropped. Restart the app or the Relay Proxy to force a fresh connection. Then test the flag in the live debugger to confirm the new value arrives.
What does a CLIENT_NOT_READY error mean in LaunchDarkly?
It means your code evaluated a flag before the SDK finished loading flag data. Wait for the initialization signal before the first evaluation. Server side SDKs expose a ready promise, and client SDKs fire a ready event you can listen for.
Why does my app keep showing fallback values?
Fallback values appear when the SDK cannot load flag data, often from a wrong SDK key or a blocked connection. Check that the key matches the right project and environment. Also confirm your network allows the SDK to reach the flag delivery endpoints.
Do I need to restart my app after a LaunchDarkly incident?
Sometimes, yes. SDKs that connected during a bad incident window can stay stuck and stop receiving flag updates. Restarting the app or the Relay Proxy rebuilds the connection. Client and mobile SDKs usually reconnect on their own when the app reloads.
Why do I still see a retired flag variation in the evaluations graph?
An old version of your app is still running somewhere and sending those events. Cached values on offline devices can also produce late events. Use the usage view to find which SDK versions are still active in your project.
What is the Relay Proxy and why does it need restarts?
The Relay Proxy sits between LaunchDarkly and your SDKs and forwards flag updates to them. It holds long lived connections, so after a network incident those connections can break silently. A restart makes it open fresh connections and resume syncing flags.