Is Discord down?
Vendor reports no incidentWhat Discord reports
Discord reports no incident on its status page.
As of the last successful poll, 2026-11-05 15:00 UTC.
Our regional reading
This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.
Checks passingchecked moments ago
Our checks of Discord pass from all 10 regions we check.
As of Nov 5, 2026, 3:03 PM UTC, RealUptime's checks of Discord passed in all 10 regions that returned a reading.
Email me when Discord reports an incident on its status page, and again when it reports it resolved.
Discord reports: All systems operational (“All Systems Operational”)
Discord's own component breakdown, as they publish it
- APIOperational
- AtlantaOperational
- CloudFlareOperational
- DesktopOperational
- BrazilOperational
- Media ProxyOperational
- Tax Calculation ServiceOperational
- iOSOperational
- AndroidOperational
- Creator PayoutsOperational
- GatewayOperational
- RotterdamOperational
- Hong KongOperational
- Push NotificationsOperational
- WebOperational
- IndiaOperational
- SearchOperational
- JapanOperational
- RussiaOperational
- SingaporeOperational
- Server Web PagesOperational
- South AfricaOperational
- PaymentsOperational
- South KoreaOperational
- Marketing SiteOperational
- SydneyOperational
- US CentralOperational
- US EastOperational
- US SouthOperational
- US WestOperational
These are Discord's components, named and scored by Discord. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.
This is Discord's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.
Discord response time, by region
Check your own site while you wait on Discord
Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Discord. It cannot diagnose Discord's own systems.
What we measured, function by function
Discord answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.
- WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- GatewayUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- InvitesUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- Marketing siteUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- Media CDNUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
- VoiceUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Checks passingCanada: Checks passingUK: Checks passingSoutheast Asia: Checks passingAustralia: Checks passingSouth America: Checks passing
What our checks show, and what people reported
- North AmericaChecks passingUS-East, US-West, US-Central, Canada
- US-EastChecks passinglatency: 57msstatus code: 200checked: Nov 5, 2026, 3:02 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Discord normally. We do not have enough reports from US-East to say anything about what people there are seeing.
- US-WestChecks passinglatency: 148msstatus code: 200checked: Nov 5, 2026, 3:03 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Discord normally. We do not have enough reports from US-West to say anything about what people there are seeing.
- US-CentralChecks passinglatency: 193msstatus code: 200checked: Nov 5, 2026, 3:00 PM UTC0 people in the last 5 minutesNot enough reports to sayOur US-Central probes reach Discord normally. We do not have enough reports from US-Central to say anything about what people there are seeing.
- CanadaChecks passinglatency: 664msstatus code: 200checked: Nov 5, 2026, 3:00 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Canada probes reach Discord normally. We do not have enough reports from Canada to say anything about what people there are seeing.
- South AmericaChecks passinglatency: 314msstatus code: 200checked: Nov 5, 2026, 3:02 PM UTC0 people in the last 5 minutesNot enough reports to sayOur South America probes reach Discord normally. We do not have enough reports from South America to say anything about what people there are seeing.
- EuropeChecks passingEurope, UK
- EuropeChecks passinglatency: 145msstatus code: 200checked: Nov 5, 2026, 3:03 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Discord normally. We do not have enough reports from Europe to say anything about what people there are seeing.
- UKChecks passinglatency: 151msstatus code: 200checked: Nov 5, 2026, 3:02 PM UTC0 people in the last 5 minutesNot enough reports to sayOur UK probes reach Discord normally. We do not have enough reports from UK to say anything about what people there are seeing.
- Asia PacificChecks passingAsia-Pacific, Southeast Asia, Australia
- Asia-PacificChecks passinglatency: 335msstatus code: 200checked: Nov 5, 2026, 3:03 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Discord normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
- Southeast AsiaChecks passinglatency: 417msstatus code: 200checked: Nov 5, 2026, 3:02 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Southeast Asia probes reach Discord normally. We do not have enough reports from Southeast Asia to say anything about what people there are seeing.
- AustraliaChecks passinglatency: 593msstatus code: 200checked: Nov 5, 2026, 3:03 PM UTC0 people in the last 5 minutesNot enough reports to sayOur Australia probes reach Discord normally. We do not have enough reports from Australia to say anything about what people there are seeing.
Somewhere else or not sure: 0 people in the last 5 minutes
These are unverified reports from people using Discord, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We started counting reports for Discord on September 11, 2026.
Recent probe events
check entries are our own probes' readings; declared entries are the vendor's. How this check works
We have been measuring Discord since August 8, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.
Need this in writing? Generate an SLA evidence report for Discord covering any window you pick, with our check readings and Discord's own claim at the time, side by side.
Full check history for Discord: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.
Put this badge in your README
Live, from this page's own readings.[](https://realuptime.io/outages/discord)<a href="https://realuptime.io/outages/discord"><img src="https://realuptime.io/outages/discord/badge.svg?days=30" alt="Discord uptime by RealUptime's checks" height="20"></a>Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.
To cite this page: RealUptime, "Is Discord down?", https://realuptime.io/outages/discord. The readings change with every check, so give the date you read them.
What we check
What our check can and cannot see
A pass means a public route of the service's API answered our request normally. We do not check what it returned, so it does not show that the data is right, that sign-in works or that the rest of the product works.
Host checked: discord.com