Having trouble with Discord? Check for an active Discord incident first, then compare the web app, desktop or mobile app, devices and networks to identify whether the problem is service-wide, account-specific or local.
Site Administrator
Last reviewed: September 25, 2026
LATEST RECORDED STATUS
Up Discord’s website appeared to be up and responding normally at the last check.
| Endpoint | Status | Observed |
|---|---|---|
| discord.com | Operational | 2026-11-09 11:55 UTC |
Is it working for you?
0 recent reports — more reports are needed for a useful trend.
For the full picture, including partial or regional outages a single external check may miss, see Discord’s official status page. official status page.

Discord can be partially unavailable without the entire service being offline. The website or app may fail to load, messages may not send, servers or channels may be inaccessible, or voice and video may fail while text chat continues to work.
Check the official Discord status page for active incidents, affected components and recovery updates. A clear status page does not completely exclude a brief, regional or account-specific problem, so compare the same action across another device or network when possible.
The pattern of the failure is useful:
Open the official Discord status page and compare active incidents or degraded components with your symptom. Login, messaging, server access, voice and video can be affected differently. If Discord reports an incident, avoid repeatedly changing local settings and retry after a recovery update.
If the status page is clear, continue testing: a short-lived, regional or limited problem may not be represented immediately.
If Discord works in the browser but not in the app, the problem is more likely to be local to the app, its stored data, the device or security software than a complete Discord outage.
A timeout, connection refusal or endlessly loading screen can originate with the local network, DNS, VPN, proxy or firewall. Try another network, such as mobile data, and temporarily bypass a VPN or proxy if your network policy allows it. If Discord works elsewhere, investigate the affected router, connection and security software rather than treating the symptom as a Discord-wide outage.
Restart a router or network connection only when you are authorized to do so and when doing so will not interrupt other users or critical services.
If other Discord users can connect but you cannot, determine whether the problem follows your account or login session. If only one server or channel fails while the rest of Discord works, the issue is less consistent with a platform-wide outage and may relate to access, permissions or that location.
Avoid repeatedly attempting to log in when Discord is reporting authentication problems. Wait for the incident or access condition to change, then try again.
Record the exact symptom, affected device, app or browser, network used and approximate start time. These details help you compare your experience with a status incident or provide useful information through Discord's normal support channels. Do not share passwords, authentication codes or private account information while troubleshooting.
For account, app and connection-specific diagnosis, consult Discord's current support documentation for the affected feature and platform. Use the status page to confirm service incidents, not as a guarantee that every regional or account-specific problem will be listed.
Every time this page loads, our server makes its own request to discord.com (and its API domain, when applicable) and reports what it got back — a real HTTP response, a timeout, or a connection failure. That result is cached for up to 2 minutes.
This confirms external reachability; it does not test every feature, region, account, or network path. Cross-check the official status page when one is available.
No. This is a live, one-off connectivity check run from our own server, not Discord's own incident reporting. Their official status page can show partial, regional, or component-level issues our single external check cannot detect.
A basic reachability check confirms that the server responded to our request. It does not test every feature, region, ISP, browser, or account-specific issue.
A check is refreshed after the two-minute cache expires. The displayed check time shows when the observation was made.
Not necessarily. Many services split their website and API onto separate infrastructure, so one can fail while the other keeps working.
Check the official Discord status page for current incidents and degraded components. If it shows no incident, test Discord on another device or network because the problem may be local, regional or account-specific.
That pattern usually points to the desktop app, its local data or the device environment rather than a complete Discord outage. Fully close the app, retry it and compare the result after checking for updates or interference from security software.
Voice and video can fail independently of messaging or server browsing. Check whether the problem affects more than one device, compare another network and look for a related component incident on the official status page.
First determine whether the failure affects all servers and channels or only one location. Then compare the web and app versions and switch networks. A single-server or single-channel problem is less consistent with a platform-wide outage than failure across multiple devices and networks.
Try another browser, device and network, and temporarily disable a VPN or proxy if appropriate. If the failure follows your account across otherwise working connections, investigate an account or access issue rather than assuming the public status page has captured every problem.
This is a live connectivity check from our server, not an official statement from Discord. A down result may also reflect a regional or partial outage.