CheckUpstream measured Discord at 100.000% availability across 1793 independent checks (global · api). 24 incidents were recorded in the past 12 months; the most recent resolved earlier today after 2 hours. Status signals are polled from Discord's official Atlassian Statuspage status page, alongside independent probes and community reports.
180 days measured availability how this is computed
100.000%
global · api · n=1793 · p95 141ms (30d)
Share of our own checks against Discord endpoints that returned Discord's expected response. Evidence that their API edge is answering correctly — not that every product behind it works.
Vendor disclosed: 22 incidents · 171 of 180 days with none posted · 9h 22m of declared impact
Fewer incidents in the last 30 days than 18% of 232 tracked services.
Share of each window with no impact declared by Discord
7d
99.193%
30d
99.651%
90d
99.884%
180d
99.783%
1y
99.893%
Downtime like this can be refundable
If you're a paying Discord customer, outages in these windows may count against Discord'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 Discord entitlement →Does Discord actually matter to you?
A Discord 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 22 incidents Discord published and resolved in the last 180 days, measured between their own start and resolution times. It describes how long Discord takes to close an incident they have acknowledged — not how often they have them, and not how available they were.
Aug 31, 22:54 UTC · resolved in 1h 56m · Resolved
Aug 14, 06:09 UTC · resolved in 20m · Resolved
Aug 7, 22:21 UTC · resolved in 48m · Resolved
Live Discord status for your README or docs. Updates itself — no API key, no maintenance.
[](https://checkupstream.com/reliability/discord)GitHub READMEs, GitLab, MDX docs — links to the live reliability page.
Discord is currently Operational. CheckUpstream tracks Discord in real-time across the official status page, RSS / Atom feeds, and community telemetry. Refresh this page for the latest reading.
Discord's last resolved incident started earlier today and lasted 1h 56m (a partial outage).
Looking for the live "is Discord down" view? See the Discord Live status page.
Aug 7, 22:21 UTC · resolved in 8m · Resolved
Jun 10, 17:15 UTC · resolved in 1h 24m · Resolved
Jun 9, 21:24 UTC · resolved in 20m · Resolved
May 22, 01:55 UTC · resolved in 1h 45m · Resolved
May 8, 19:08 UTC · resolved in 3h 31m · Resolved
May 2, 17:03 UTC · resolved in 27m · Resolved
Apr 28, 19:20 UTC · resolved in 2h · Resolved
Apr 19, 02:37 UTC · resolved in 1h 23m · Resolved
Apr 16, 19:47 UTC · resolved in 43m · Resolved
Apr 7, 01:48 UTC · resolved in 1h 17m · Resolved
Mar 28, 21:23 UTC · resolved in 21m · Resolved
Discord's 30-day measured availability is 100.000%, from CheckUpstream's own probes against Discord endpoints. It is the share of checks that returned the expected response, not a figure taken from Discord's status page.
Sign up to CheckUpstream and add Discord 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 Discord'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.