Discord favicon

Discord outage on 2026-10-30

discord.com
October 2026 30 Major incident

Discord users had trouble establishing voice calls for 59 minutes on 30 October 2026. Discord's status page confirms the fault sat on their side, not yours.

Started

15:23 UTC

Duration

Lasted 59m

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 logged one incident on 30 October 2026, titled "Issues establishing voice calls". It started at 15:23 UTC and ran for 59 minutes, ending with a resolved update at 16:18 UTC. Discord's own timeline shows four updates: investigating at 15:23, identified at 15:43, monitoring at 15:43, and resolved at 16:18. The identified and monitoring updates landed at the same minute, which tells you Discord had a fix ready to deploy as soon as they pinned the cause. No component list was published for this incident, so there is no detail on which specific services or regions of Discord's voice infrastructure were involved. Discord's own text does not explain what caused the problem, only that a fix was implemented and then confirmed through monitoring. No user reports were filed during this window on our side, which is unsurprising given the issue was specifically about establishing voice calls rather than the whole platform going dark. Over the past 90 days, Discord has logged 18 incidents with a median duration of 1 hour 4 minutes, so this one resolved slightly faster than typical. No post-mortem has been published explaining the root cause behind the voice connection failures.

Learning

This incident is a good example of a failure that lives entirely on the provider's side of the connection. Establishing a voice call on Discord depends on signalling and media relay infrastructure that your own monitoring never touches, because your checks watch your product's endpoints, not Discord's internal call-routing layer. That means your dashboards could have stayed green the entire 59 minutes while your users sat there unable to join a voice channel. Discord's status updates show investigation, a fix, and monitoring within the same 20 minute stretch, which suggests a contained problem rather than a sprawling one, but there is no detail on root cause either way. Over the last 30 days, UptimeRobot's own checks against Discord recorded 2 incidents with a median duration of 1h 3m, both resolved, which lines up closely with what Discord itself reports for the 90 day window. That overlap matters: it tells you external, independent monitoring of Discord is catching the same events Discord discloses, rather than missing them or inventing extra ones. Your monitoring covers your half, UptimeRobot now watches the provider's half too, so next time something breaks in a call you know which side to blame 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.