Discord favicon

Discord outage on 2026-10-31

discord.com
October 2026 31 Major incident

Discord had trouble with voice calls for 6 hours and 17 minutes on 31 October 2026. If you or people in your server couldn't get a voice call to connect, the fault was on Discord's side.

Started

15:26 UTC

Duration

Lasted 6h 17m

Source

IsDown

Next time

Discord is degraded. Is your product working?

An incident on their side does not always mean an outage on yours, and the only way to know is to already be watching your own endpoints. Set that up in under a minute and you will be notified the next time your own site is affected. And there will be a next time.

50 monitors for your own websites. No card.

What happened?

Discord's status page logged a single incident on 31 October 2026, titled "Issues establishing voice call", starting at 15:26 UTC. The company filed three updates in total. The first, at 15:26 UTC, said only that the issue was under investigation. It took over four hours for the next update: at 19:40 UTC, Discord said a fix had been implemented and they were monitoring the results. The incident was marked resolved at 21:43 UTC, 6 hours and 17 minutes after it started. Discord's status page lists no components as affected for this incident, so there's no breakdown of which part of voice infrastructure was involved. No post-mortem has been published, and Discord's own updates do not say what caused the problem or what the fix actually changed. No user reports were filed during this window on the record available, which doesn't mean nobody was affected, only that none were logged here. Over the past 90 days Discord has logged 19 incidents with a median duration of 1 hour and 6 minutes, so this outage ran roughly six times longer than Discord's typical recent incident.

Learning

Voice call setup is a layer that sits deep inside Discord's own infrastructure, the kind of thing an external uptime check pinging Discord's main domain or API would not catch. A product's own monitoring, watching its own servers and its own integration with Discord's API, can stay green the entire time because the fault never touches your code, it touches the handshake Discord's servers do to connect a call. That's exactly the shape of failure to expect from a dependency like this: your systems report fine, your users report broken calls, and the two are not in conflict. UptimeRobot's own 30 day data for Discord shows 3 incidents with a median duration of 1 hour and 7 minutes, which gives you a baseline for how often and how long these things normally run, against which this 6 hour 17 minute incident stands out. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time you know which side broke without guessing.

4.7
stars out of 5
284+ reviews on

Start monitoring in 30 seconds.

There's nothing to install. No credit card required. 50 monitors for free.