Live check
Is Discord down right now?
Observed from Discord’s public feed by our independent monitor. Always confirm operational decisions on the official status page.
While you wait: the Discord incident checklist
- Scope it by component. Discord's status page separates the API, the real-time gateway, voice, media proxy and third-party (CDN) systems. A gateway incident hits bots and clients differently than a voice-only one — check which component is red before you react.
- Let bots resume, don't reconnect-storm. During a gateway incident your library should RESUME its session, not open a fresh IDENTIFY on a tight loop. Hammering reconnects burns the IDENTIFY rate limit and slows your own recovery — back off with jitter.
- Check your webhook-based alerting. If you page yourself or post ops alerts via Discord webhooks, that channel may be down exactly when you need it. Confirm an out-of-band path (email, SMS, another chat) before you rely on Discord to tell you Discord is broken.
- Expect login and CAPTCHA friction. Sign-in, 'Login with Discord' OAuth and hCaptcha challenges can fail while existing sessions keep working. New user auth is the first thing to wobble and the last thing to notice.
- Separate voice from text. Voice/media runs on regional infrastructure independent of text and the API. A voice-region incident won't touch your bot's REST calls — and vice versa.
What breaks when Discord has issues
For teams that run on Discord, an incident is a coordination and automation outage: community and support servers go quiet, bots that drive deploys, moderation or alerting stall, and webhook-based notifications silently stop. 'Login with Discord' blocks new sign-ins to anything that federates auth through it, and voice incidents drop calls and stage channels. If your incident comms live in Discord, the outage takes your war room with it — which is why the fallback channel has to be agreed in advance.
FAQ
Is it Discord or my bot?
Check discordstatus.com for the gateway and API components. If they're green, look at your own gateway session, token, intents and rate-limit handling — a single bot failing while Discord is healthy is almost always client-side.
Are Discord webhooks and bot alerts affected?
Yes, if the API is degraded. Webhook deliveries and bot messages can fail or lag. If you rely on Discord for on-call alerting, keep an independent out-of-band channel for incidents that hit Discord itself.
Will 'Login with Discord' break during an outage?
New OAuth sign-ins can fail while existing sessions stay valid. If your product federates auth through Discord, expect new logins to be the visible symptom.
Is voice down if text and my bot still work?
It can be. Voice and media run on separate regional infrastructure, so a voice incident is independent of the API and gateway. Check the specific component on the status page.
Put Discord’s status in your toolbar
Is it you — or your vendor? You checked once. The extension watches Discord and the rest of your stack continuously — badge, popup and Side Panel, free for 5 vendors, no account.
Add to Chrome — free, no accountNot an outage? Track API changes before they become incidents.
VendorStatus shows when a dependency is failing now. Breakwater watches official developer changelogs and migration deadlines locally in your browser, so your team can plan the change before the next deploy.
Also on your stack?
Not affiliated with Discord. Status data comes from their public status page.