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.
90 days measured availability how this is computed
100.000%
global · api · n=2819 · p95 788ms (30d)
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: 23 incidents · 86 of 90 days with none posted · 3h 24m 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.
Track your LaunchDarkly entitlement →Does LaunchDarkly actually matter to you?
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.
Check a repository →From 23 incidents LaunchDarkly published and resolved in the last 90 days, 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.
Aug 26, 19:45 UTC · resolved in 24m · Resolved
Aug 26, 19:45 UTC · resolved in 5m · Resolved
Aug 24, 12:20 UTC · resolved in 1h 19m · Resolved
Live LaunchDarkly status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/launchdarkly)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
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.
Looking for the live "is LaunchDarkly down" view? See the LaunchDarkly Live status page.
Aug 17, 10:36 UTC · resolved in 5h 33m · Resolved
Aug 14, 14:47 UTC · resolved in 8m · Resolved
Jul 31, 17:44 UTC · resolved in 11m · Resolved
Jul 28, 19:24 UTC · resolved in 6m · Resolved
Jul 28, 19:24 UTC · resolved in 46m · Resolved
Jul 10, 19:21 UTC · resolved in 18d 23h · Resolved
Jul 10, 17:10 UTC · resolved in 1h 9m · Resolved
Jul 10, 16:16 UTC · resolved in 1h 33m · Resolved
Jul 8, 18:03 UTC · resolved in 1h 47m · Resolved
Jul 6, 20:52 UTC · resolved in 3h 8m · Resolved
Jul 6, 14:33 UTC · resolved in 1h 27m · Resolved
Jul 3, 14:29 UTC · resolved in 1h 40m · Resolved
Jun 17, 19:43 UTC · resolved in 5h 51m · Resolved
Jun 15, 17:26 UTC · resolved in 13m · Resolved
LaunchDarkly's last resolved incident started 5 days ago and lasted 24 minutes (degraded performance).
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.
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).
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.