Skip to main content
LaunchDarkly logo

Is LaunchDarkly Down?

No — LaunchDarkly is up

Reachable from all 8 checked regions

Average response time: 144ms

Last checked · checks run every 6 hours

Official status page: https://status.launchdarkly.com

LaunchDarkly uptime

100%
Last 7 days
100%
Last 30 days
100%
Last 90 days
170ms
Avg response, 30 days

Measured from multiple regions every 6 hours. Percentages count only checks that returned an availability answer — 76 days measured so far. A dash means that window does not yet hold enough measured days to publish a figure.

30-day history

76-day clean streak
Sep 14: 100.00% uptime, 31 checks
Sep 15: 100.00% uptime, 32 checks
Sep 16: 100.00% uptime, 32 checks
Sep 17: 100.00% uptime, 32 checks
Sep 18: 100.00% uptime, 32 checks
Sep 19: 100.00% uptime, 32 checks
Sep 20: 100.00% uptime, 32 checks
Sep 21: 100.00% uptime, 32 checks
Sep 22: 100.00% uptime, 32 checks
Sep 23: 100.00% uptime, 32 checks
Sep 24: 100.00% uptime, 32 checks
Sep 25: 100.00% uptime, 32 checks
Sep 26: 100.00% uptime, 32 checks
Sep 27: 100.00% uptime, 32 checks
Sep 28: 100.00% uptime, 32 checks
Sep 29: 100.00% uptime, 32 checks
Sep 30: 100.00% uptime, 32 checks
Oct 1: 100.00% uptime, 30 checks
Oct 2: 100.00% uptime, 32 checks
Oct 3: 100.00% uptime, 32 checks
Oct 4: 100.00% uptime, 32 checks
Oct 5: 100.00% uptime, 32 checks
Oct 6: 100.00% uptime, 32 checks
Oct 7: 100.00% uptime, 32 checks
Oct 8: 100.00% uptime, 32 checks
Oct 9: 100.00% uptime, 32 checks
Oct 10: 100.00% uptime, 32 checks
Oct 11: 100.00% uptime, 32 checks
Oct 12: 100.00% uptime, 32 checks
Oct 13: 100.00% uptime, 32 checks
Sep 14 Today
No downtime Partial Downtime Not measurable No data

Reachability by region

Each region runs its own request from a different part of the world. A service can be up for one continent and down for another, which is usually the first sign of a routing or CDN problem.

ewr
170ms
DNS 48ms TCP 13ms TLS 31ms TTFB 134ms
fra
65ms
DNS 24ms TCP 1ms TLS 13ms TTFB 57ms
gru
64ms
DNS 8ms TCP 1ms TLS 8ms TTFB 56ms
iad
132ms
DNS 96ms TCP 2ms TLS 7ms TTFB 121ms
jnb
328ms
DNS 67ms TCP 0ms TLS 65ms TTFB 180ms
lax
127ms
DNS 27ms TCP 1ms TLS 25ms TTFB 78ms
lhr
102ms
DNS 18ms TCP 3ms TLS 14ms TTFB 77ms
nrt
164ms
DNS 100ms TCP 2ms TLS 11ms TTFB 152ms

What LaunchDarkly does

LaunchDarkly is a feature management platform that decides, at runtime, which users see which version of a feature. Engineering teams use it to release code behind flags, roll changes out gradually and switch a broken feature off without deploying. That makes it a live dependency of the application rather than a build-time tool.

What an outage looks like

Flag changes made in the LaunchDarkly dashboard stop reaching applications, so a rollout appears to save but never takes effect for users. Applications starting up fresh may fall back to the default values compiled into their code, which can turn features off for everyone at once or expose ones meant to stay hidden. The web app itself may fail to load or save targeting rules.

What to do about it

Check status.launchdarkly.com, which separates the Flag Delivery Network from the web app, the streaming and polling APIs, and experimentation, because flags already delivered can keep working while the dashboard is unavailable. SDKs cache their last known flag values, so running services usually continue on the previous configuration. Delay restarts and deploys until delivery recovers, since a restart is what forces a service onto defaults.

Is it down for everyone, or just you?

If this page says LaunchDarkly is up but it is not loading for you, the problem is between you and them. Run a check against any URL from up to 17 cities across three regions to find out where it breaks.

Test it yourself

Related services

Datadog
Datadog
Sentry
Sentry
GitHub
GitHub
PagerDuty
PagerDuty

LaunchDarkly outage FAQ

Do my feature flags still work if LaunchDarkly is down?
Generally yes for services that are already running. LaunchDarkly SDKs hold the last flag values they received in memory, so an application that was connected before the incident keeps evaluating flags normally even when it cannot reach the service. What stops is change: new flag updates do not arrive, so anything you toggle during the outage will not take effect until delivery recovers.
What happens when a service restarts during a LaunchDarkly outage?
It loses the cached values and falls back to the defaults written into your code. This is the failure mode that turns a LaunchDarkly incident into a user-visible one, because a routine deploy or autoscaling event can flip a whole fleet onto default behaviour mid-incident. Holding deploys and restarts until the Flag Delivery Network is healthy is the single most useful thing to do.
Is the LaunchDarkly dashboard down or is flag delivery affected?
They are separate components and fail independently. The status page lists the web app apart from the Flag Delivery Network and the streaming, polling and edge APIs, so a dashboard you cannot log into does not necessarily mean your applications are affected. Check which component is degraded before assuming production is at risk, because the two incidents call for very different responses.
Can I turn off a broken feature while LaunchDarkly is unavailable?
Not through LaunchDarkly, which is why this timing hurts. If flag delivery is degraded, a kill switch you flip in the dashboard will not reach running applications. Fall back to whatever controls you own directly, such as a configuration change, a load balancer rule or a rollback of the deploy that introduced the feature, and re-apply the flag change once delivery returns.
Does a LaunchDarkly outage affect experiments and metrics?
Yes, and it can distort results beyond the incident window. Experimentation is tracked as its own component, and when event delivery is degraded the exposures and conversions recorded during that period may be incomplete. Treat any experiment running across an outage with suspicion, and check whether the affected days should be excluded before acting on the numbers.

How we measure this

  • We request LaunchDarkly's public endpoint every 6 hours from Fly.io regions across six continents — the most recent check ran from 8 of them.
  • A region counts as down only when it gets no usable HTTP response. A 403 or 429 means the origin answered and refused us, which we report as blocked, never as an outage.
  • A single failing region is treated as probe noise. We only change the verdict when two consecutive cycles agree.
  • Response times average only the regions that actually served the page, so a timeout never inflates the number.
  • Where LaunchDarkly publishes an official status feed we read it too. An all-clear from the vendor can soften an unconfirmed degradation; a vendor-declared outage only worsens our verdict when our own checks corroborate it.

Get alerted when LaunchDarkly goes down

This page refreshes every 6 hours. Your own monitors run as often as every 30 seconds, from up to 17 cities across three regions, and tell you the moment something breaks.

Start Free Monitoring
Free plan available No credit card required