Elevated API error rate
DegradedThis incident has been resolved.
Discord is up and running. Discord is a chat service with voice, video and communities.
Worked out from the incidents Discord reported, so it is an estimate and not a measurement.
Last incident: “Elevated API error rate”, 14 days ago.
This incident has been resolved.
This incident has been resolved. https://x.com/discord/status/2102964092189475028?s=20
This incident has been resolved.
This incident has been resolved.
This incident has been resolved.
Discord’s official status page says: All Systems Operational. This page checks it again when you load it, at most every 5 minutes.
The most recent incident Discord reported was “Elevated API error rate”, 14 days ago (2026-10-01 19:48 UTC). Its last full outage started 28 days ago.
Discord reports 30 components on its status page, including API, CloudFlare, Desktop, Atlanta, Brazil. Each is checked again whenever this page refreshes.
Use a backup channel for anything urgent, and expect delayed messages or notifications to arrive in a burst after recovery.
Voice is tracked per region (US East, Rotterdam, Japan…) separately from the API and Gateway. 'RTC Connecting' / 'No Route' errors with healthy chat mean a voice-server incident, not a Discord-wide outage.
Push Notifications is its own component, separate from the Gateway and API. A notification-pipeline incident delays alerts while the app itself stays usable.
If the status above is operational but Discord still fails for you, the cause is probably on your side: try another network, clear the cache, or check your own connection. If it shows a degradation or an outage, others are affected too.
OpenUptime checks your site every minute and sends an alert to Slack, Telegram, email or a webhook the moment it stops responding. It is open source and free to start.