Is LaunchDarkly down?
LaunchDarkly status · Developer Tools · checked (2s ago)
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.
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.
isuptime reads this feed on a schedule and reports what it says — how that works, in detail.
LaunchDarkly uptime, last 30 days
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.
- 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, 2s ago. They are checked on one schedule, so the timing is comparable — but overlapping in time does not mean they share a cause.
CloudflarePartial System Outage
- Razorpay1 of 7 services down: Payments API
- ElasticPartial System Outage
- PlayStation NetworkPlayStation Store affected in Russia
- SalesforceDegraded Performance: 1 active incident
- ScalewayPartially Degraded Service
- SnowflakePartially Degraded Service
- Temporal CloudPartially Degraded Service
LaunchDarkly response time trend
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.
- delayed event processing
resolved · Oct 26, 08:52 PM (12d ago)
- Elevated 5xx Errors (15:11–15:32 UTC)
resolved · Oct 15, 03:47 PM (23d ago)
- Delays in Guarded Rollouts, Progressive Rollouts, Release Pipelines, and Experimentation
resolved · Oct 3, 07:29 AM (35d ago)
- Elevated error rates in the LaunchDarkly application
resolved · Oct 2, 02:10 PM (36d ago)
- Flag delivery errors in Streaming API
resolved · Aug 26, 07:45 PM (73d ago)
- Email delivery failure affecting sign-up verification and notification emails
resolved · Aug 24, 12:20 PM (75d ago)
- Flag Updates via Polling API delayed
resolved · Aug 17, 10:36 AM (82d ago)
- Flag Updates delayed in US Region
resolved · Aug 14, 02:47 PM (85d ago)
- Elevated errors on server-side SDK streaming connections
resolved · Aug 7, 07:29 PM (92d ago)
- Investigating - Known Impact
resolved · Jul 31, 05:44 PM (99d ago)
- Delay in Session Replay and Error ingest
resolved · Jul 28, 07:24 PM (102d ago)
- Elevated API Latency and Errors (11:32–11:48 PT)
resolved · Jul 26, 06:32 PM (104d ago)
- Web application unavailable and flag delivery evaluations have elevated failure rate
resolved · Jul 10, 05:10 PM (120d ago)
- Launchdarkly UI is down and flag evaluation errors are occuring
resolved · Jul 10, 04:16 PM (120d ago)
- LaunchDarkly is operational but customer action may be required
resolved · Jul 10, 04:00 PM (120d ago)
- Frequentist experiments cannot be saved or started
resolved · Jul 8, 06:03 PM (122d ago)
- Delays in Experimentation and Guarded Rollout results
resolved · Jul 7, 03:10 PM (123d ago)
- High volume of error alerts related to flag delivery network.
resolved · Jul 6, 08:30 PM (124d ago)
- Verification emails not being sent
resolved · Jul 6, 02:33 PM (124d ago)
- Elevated error rates on event data ingestion endpoints
resolved · Jul 3, 02:29 PM (127d ago)
LaunchDarkly status — frequently asked
- Is LaunchDarkly down right now?
- No — LaunchDarkly is not down. All LaunchDarkly systems are reported operational. Checked (2s 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 399 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 “delayed event processing”, opened Oct 26, 08:52 PM UTC (12d ago) and marked resolved Oct 26, 08:52 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.