LaunchDarkly status · Developer Tools · checked (3s ago)
Operational
No — LaunchDarkly is not down. All LaunchDarkly systems are reported operational.
According to LaunchDarkly's official status page, LaunchDarkly was reporting “All Systems Operational” when isuptime last checked at . Over the last 30 days, LaunchDarkly's feed reported no outage in 100.00% of our checks.
No outage reported (30d)
100.00%
Share of our checks where LaunchDarkly's feed reported no outage. Degraded counts as no-outage. Not an SLA.
Response time
799 ms
How long the last status check took
Reported by
Operational
All Systems Operational
Is LaunchDarkly down for you right now?
Everything above is read from LaunchDarkly's own status feed. This is what other visitors are saying in the last 24 hours — useful when the feed is green and you are still stuck, and never used to change the status above.
Nobody has reported LaunchDarkly in the last 24 hours. Yours would be the first.
Reports are anonymous counts and are kept for 24 hours, then deleted. No account, no message, nothing stored about who reported. One report per service per hour, changeable until the hour is out.
What LaunchDarkly is
LaunchDarkly is a feature flag and experimentation platform. Applications hold a streaming connection to it and change behaviour based on the flags it serves, which means a LaunchDarkly problem can quietly change how someone else's product behaves.
What LaunchDarkly's status feed covers
The status page separates flag delivery — the streaming and polling endpoints SDKs actually depend on — from the dashboard and the management API. That split is the one to read: the dashboard being down is an inconvenience, whereas flag delivery failing is what affects production traffic.
One bar per day. Each shows the share of that day's checks where LaunchDarkly's own status feed reported no outage — degraded counts as no-outage. Days with no bar are days isuptime recorded no checks, not days LaunchDarkly was down.
2026-08-2530 of 30 days recordedToday
No outage reported (99%+)
95–99%
80–95%
Under 80%
No data
Other services reporting problems right now
9 other services isuptime tracks were also reporting a problem as of the same check, 3s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
Each point is one check of LaunchDarkly's status endpoint.
LaunchDarkly outage history
LaunchDarkly has published 50 incidents in the last 12 months, the 20 most recent shown here. Only what LaunchDarkly posted itself — not every problem users hit.
No — LaunchDarkly is not down. All LaunchDarkly systems are reported operational. Checked (3s ago).
What is LaunchDarkly's status right now?
LaunchDarkly is reporting “All Systems Operational” on its official status page — Operational — as of . That status feed answered our last check in 799 ms. isuptime reads this from LaunchDarkly's own published feed and does not test LaunchDarkly independently.
When did LaunchDarkly last go down?
The most recent incident LaunchDarkly published was “Flag delivery errors in Streaming API”, opened Aug 26, 07:45 PM UTC (27d ago) and marked resolved Aug 26, 08:00 PM UTC. That is the latest entry in LaunchDarkly's own incident feed, not every problem users experienced.
What is LaunchDarkly's uptime?
isuptime does not measure LaunchDarkly's uptime directly — it reads LaunchDarkly's own published status feed. Over the last 30 days, LaunchDarkly's own status feed reported no outage in 100.00% of isuptime's checks. Periods the provider called degraded count as no-outage, and this is isuptime's own measurement, not a contractual SLA.
Is it just me, or is LaunchDarkly down for everyone?
LaunchDarkly reports all systems operational, so the problem is likely local to your network, browser or account. Try a different network or device.
LaunchDarkly says operational but it is not working for me
LaunchDarkly SDKs are built to survive this: they cache the last known flag values and fall back to the defaults in your code, so an evaluation returning the wrong variation is often a stale cache or a missing default rather than an outage. Check that your SDK key matches the environment you think it does, and that streaming is not being blocked by a proxy that closes long-lived connections.
