Is Discord Down? How to Check Discord Status Right Now

Discord serves over 500 million registered users — gamers, developer communities, creator audiences, and businesses running everything from customer support to internal team communication. When Discord goes down, the impact is immediate and loud. Voice chats drop mid-raid, communities go dark, and bots stop responding.

Here's how to figure out what's broken, why, and how to make sure you're never caught flat-footed again.

Is Discord Down Right Now?

Check these sources in order:

1. Statusfield — Discord status — real-time monitoring, updated continuously.
2. Discord's official status page — discordstatus.com shows component-level status, but often lags real incidents.
3. Twitter/X — search Discord down sorted by Latest. Discord's massive user base floods social media within minutes of any outage.
4. Discord's own server — if you're part of the official Discord Developers server, incidents are often discussed there early.

Voice vs. Text vs. API — What's Actually Broken

Discord's architecture separates concerns in ways that matter for diagnosis. Not all Discord outages are equal.

A Gateway outage is particularly disruptive because it affects both the client (your app freezes or goes offline) and bots (they disconnect and miss events). A Voice outage, by contrast, might leave text channels fully functional.

Common Discord Error Codes and Messages

Key distinction: Discord's Gateway errors (4000-4999) are connection-level errors. HTTP 5xx errors are REST API errors. Both can occur during an outage, but they have different causes and recovery paths.

Why Discord Goes Down

Discord handles a uniquely spiky traffic profile — usage surges when major game releases drop, esports events go live, or popular streamers start broadcasting. A few patterns drive most outages:

Event-driven traffic spikes. When a major game drops (think a Call of Duty season launch or a Minecraft update), millions of players flood Discord simultaneously to coordinate. These spikes are hard to provision for.

DDoS attacks. Discord is a high-visibility target. The platform has historically been subject to significant DDoS campaigns, particularly during gaming events.

Bot-driven load. There are millions of bots on Discord. A popular bot library release or a viral bot feature can cause unexpected API load. Discord's rate limiting exists specifically to manage this, but coordinated bursts can still stress infrastructure.

Voice infrastructure complexity. Discord's voice system uses WebRTC with a global network of voice servers. Regional voice server issues can affect voice without touching text at all — and they happen more frequently than full outages.

Media proxy load. Discord proxies all external images and embeds through its own CDN to prevent IP exposure. This proxy layer has its own failure modes, independent of core messaging.

Developer Impact: Bots and the Discord API

If you're building on the Discord API, outages hit differently than they do for regular users.

Handling Gateway Disconnects

Your bot will disconnect during a Gateway outage. All major Discord libraries (discord.js, discord.py, JDA) handle reconnection automatically, but you should understand what happens:

1. Gateway closes with a code (4000, 1001, etc.)
2. Your library attempts to resume the session using the RESUME payload
3. If the session is expired or invalid, the library does a full reconnect with IDENTIFY
4. Events that occurred while disconnected are missed unless you have resume logic

// discord.js handles reconnection automatically, but you can hook into events:
client.on('disconnect', (event) => {
  console.log(`Disconnected with code ${event.code}: ${event.reason}`);
  // discord.js will attempt to reconnect — log but don't manually reconnect
});
 
client.on('reconnecting', () => {
  console.log('Attempting to reconnect to Discord Gateway...');
});
 
client.on('resume', (replayed) => {
  console.log(`Resumed. ${replayed} events replayed.`);
});

Handling REST API Errors

import discord
from discord.ext import commands
import asyncio
 
async def safe_send(channel, content, retries=3):
    for attempt in range(retries):
        try:
            await channel.send(content)
            return
        except discord.errors.HTTPException as e:
            if e.status == 500 or e.status == 503:
                # Discord server error — retry with backoff
                wait = 2 ** attempt
                await asyncio.sleep(wait)
            elif e.status == 429:
                # Rate limited — discord.py handles this automatically
                # but if you're hitting it here, something is wrong
                await asyncio.sleep(e.retry_after)
            else:
                raise
    raise Exception(f"Failed to send message after {retries} attempts")

Monitoring Your Bot's Health

Track Gateway disconnect rates and REST error rates in your bot. A sudden increase in 5xx errors or Gateway closes is often your first signal that something is wrong with Discord — before the status page updates.

# Track metrics when errors occur
except discord.errors.HTTPException as e:
    metrics.increment('discord.http_error', tags={
        'status': e.status,
        'endpoint': endpoint_name
    })

How to Get Instant Discord Outage Alerts

Discord communities depend on uptime. Whether you're a server admin managing thousands of members or a developer with bots in production, you need to know about Discord issues the moment they happen — not when your users start complaining.

Monitor Discord on Statusfield and get alerted the moment any Discord component changes status. Route alerts to email, webhooks, or a backup communication channel — because you won't be able to send the alert through Discord if Discord is the thing that's down.

Start monitoring Discord →

Frequently Asked Questions

Is Discord down for everyone or just me?

Check discordstatus.com or Statusfield. If both show operational, your issue is likely local — try the browser version at discord.com/app, check your network, or restart the app. If your friends in the same server are also having issues, it's almost certainly Discord's infrastructure.

Why does Discord say "RTC Connecting" and never connect to voice?

"RTC Connecting" means Discord's WebRTC negotiation is failing. This can be caused by Discord's Voice component being degraded, firewall or NAT issues on your network blocking WebRTC UDP traffic, or a regional voice server problem. Check the Voice component on Statusfield. If it shows healthy, the issue is likely your network configuration.

My Discord bot keeps disconnecting — is Discord down?

Check the Gateway component specifically. Frequent disconnects during a Gateway incident are expected and will resolve when Discord recovers. If the Gateway shows healthy, look at your bot's code — unhandled promise rejections in discord.js or uncaught exceptions can cause the bot process to crash.

Discord is showing messages but voice won't work — what's happening?

Discord's Voice and messaging infrastructure are separate. A Voice-only outage is common — text channels can be fully functional while voice servers have regional issues. Check the Voice component on discordstatus.com or Statusfield.

Why does Discord load but images and attachments don't?

Discord proxies all media through its media proxy layer. When this component is degraded, messages load fine but images, video previews, and file attachments won't display. Check the Media Proxy component on the status page.

How do I get alerted when Discord goes down?

Set up Discord monitoring on Statusfield. You'll get alerts via email or webhooks the moment Discord reports an incident. Since Discord itself will be down, routing alerts to email ensures you actually receive them.

How often does Discord have outages?

Discord publishes its full incident history at discordstatus.com. Minor incidents (degraded performance, partial component failures) occur multiple times per month. Broader outages affecting core functionality happen less frequently. Discord's voice infrastructure tends to have more incidents than the core messaging layer.

Can Discord bots miss events during an outage?

Yes. If your bot disconnects from the Gateway and the session expires before it can resume, events that occurred during the disconnection are lost. For critical workflows, design your bot to be idempotent and to re-query state on reconnection rather than relying on receiving every event.