CheckUpstream measured LaunchDarkly at 100.000% availability across 2819 independent checks (global · api). 36 incidents were recorded in the past 12 months; the most recent resolved 5 days ago after 25 minutes. Status signals are polled from LaunchDarkly's official Atlassian Statuspage status page, alongside independent probes and community reports.
Share of our own checks against LaunchDarkly endpoints that returned LaunchDarkly's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 35 incidents · 355 of 365 days with none posted · 14h 7m of declared impact
Fewer incidents in the last 30 days than 15% of 232 tracked services.
Share of each window with no impact declared by LaunchDarkly
7d
99.926%
30d
99.554%
90d
99.842%
180d
99.673%
1y
99.839%
Downtime like this can be refundable
If you're a paying LaunchDarkly customer, outages in these windows may count against LaunchDarkly's SLA — vendors owe service credits for missed uptime targets, but only if you file inside the deadline. CheckUpstream tracks the entitlement, drafts the claim, and hands you the filing link.
A LaunchDarkly outage only matters if something you ship depends on it. Point us at a public repository and we will read its dependencies and tell you — no account, nothing stored.
Time to resolve, from LaunchDarkly's own incident posts (1 year)
Median time to resolve
1h 16m
Slowest 10% take longer than
6h 25m
From 35 incidents LaunchDarkly published and resolved in the last 1 year, measured between their own start and resolution times. It describes how long LaunchDarkly takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Frequently Asked Questions
›Is LaunchDarkly currently down?
LaunchDarkly is currently Operational. CheckUpstream tracks LaunchDarkly in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
LaunchDarkly's last resolved incident started 5 days ago and lasted 24 minutes (degraded performance).
›What's LaunchDarkly's 30-day uptime?
LaunchDarkly's 30-day measured availability is 100.000%, from CheckUpstream's own probes against LaunchDarkly endpoints. It is the share of checks that returned the expected response, not a figure taken from LaunchDarkly's status page.
›How do I monitor LaunchDarkly in production?
Sign up to CheckUpstream and add LaunchDarkly to a watchlist. We send incident alerts via Slack, email, webhook, or PagerDuty within seconds of detection, covering both the official status page and community signals (HN, Reddit, Bluesky, Cloudflare Radar).
›How does CheckUpstream track LaunchDarkly?
We poll LaunchDarkly's official status page on a 1-5 minute cadence, parse its RSS / Atom feed as a fallback, ingest community signals from social platforms, and aggregate per-org SDK telemetry. Multiple sources reduce false positives versus any single feed alone.