Publisher status · statuspage

Discord status

Live incidents and maintenance pulled from the publisher's official status page.

OPERATIONAL
Discord · discord
No active incidents reported by the publisher
via statuspage
100.00% uptimelast 30 days
2026-06-29: no data2026-06-30: no data2026-07-01: no data2026-07-02: no data2026-07-03: no data2026-07-04: no data2026-07-05: no data2026-07-06: no data2026-07-07: no data2026-07-08: no data2026-07-09: no data2026-07-10: no data2026-07-11: no data2026-07-12: no data2026-07-13: no data2026-07-14: operational all day, 1 checks2026-07-15: operational all day, 4 checks2026-07-16: operational all day, 2 checks2026-07-17: operational all day, 2 checks2026-07-18: no data2026-07-19: no data2026-07-20: no data2026-07-21: no data2026-07-22: no data2026-07-23: no data2026-07-24: no data2026-07-25: no data2026-07-26: operational all day, 6 checks2026-07-27: operational all day, 4 checks2026-07-28: operational all day, 6 checks
30 days agocollecting data · 7/30 daystoday
Checked 16s ago single-source feed every 5 min · publisher feed direct probe, not crowd-reported

Publisher status

Indicator
none
Description
All Systems Operational
Source
https://discordstatus.com
Adapter
statuspage
What this means

Discord reports no active incidents on its official status page.

This is the publisher's own classification. If you still can't connect, the issue may be network-local or specific to your region, publisher feeds don't always flag every user-visible problem.

What to try next

Check your DNS

Flush your DNS cache: ipconfig /flushdns on Windows, sudo dscacheutil -flushcache on macOS.

Try another network

Switch between Wi-Fi and mobile data, or disable your VPN. If it works there, the issue is on your primary network.

Browser reset

Try an incognito window or a different browser, a bad extension or cached error page can masquerade as downtime.

Official status page

discordstatus.com Discord's official status page

FAQ

Why does this page show Discord as up while my game won't connect?
Publisher status pages show the publisher's view, not yours. Discord aggregates many internal signals; user-visible problems (matchmaker queues, regional CDN issues, account auth) sometimes don't trip the public indicator. Check the active incidents list below for narrower scope.
How is this different from a direct probe?
Websites and game servers get hit with a live network request. Publishers don't expose a single check endpoint, so we poll their official status feed (Statuspage, Riot, etc.) every 5 minutes and surface their classification verbatim.
Where does the data come from?
Directly from Discord's own status feed, see https://discordstatus.com. We don't aggregate Twitter or DownDetector signals.

Status badge

Embed a live status badge on your site, README, or status page. Updates automatically, same status-aware SVG the rest of isitdown.io uses.

Discord status
<a href="https://isitdown.io/publisher/discord"><img src="https://isitdown.io/badge/publisher/discord.svg" alt="Discord status"></a>

Related

Epic Games / FortniteRobloxCloudflareGitHubTwitchRedditOpenAIAnthropic / Claude

Methodology

Probe
We poll the publisher's official status page endpoint (Statuspage.io JSON, Riot's status API, etc.) and read their own incident feed.
Counts as DOWN
The publisher reports a major or critical indicator, or the adapter returns a protocol error.
Counts as DEGRADED
The publisher reports minor issues or maintenance. Active incidents are listed even when the overall indicator is green.
Detail
Publisher checks differ from direct probing: we inherit the publisher's own classification. If Atlassian says "all systems operational" while users can't connect, our check will show up, the signal is theirs, not ours.
Cadence
Every 5 minutes, in parallel across 4 independent probe methods (HTTP/1.1 with strict TLS, HTTP/2, a browser User-Agent GET, and a curl-style HEAD) from our edge network. We check probe diversity, not geography — if a site blocks a non-browser User-Agent or only speaks HTTP/1.1, the four cards show it.
Rate-limited targets
If a host returns 429 or consistently drops connections from our IPs, we cap retries at 3 and report the last observed status, we do not flood the target to confirm the outage.
Data source
Our verdict is based on direct multi-method probes, every result above is a live network request, never a Twitter mention or DownDetector aggregate. User reports, when shown, appear separately below as a supplementary signal and are never used to determine the up/down verdict.
JSON: /check?target=discord&format=json Share: https://isitdown.io/publisher/discord