Discord users found themselves unable to join voice calls for much of October 31, 2026, after the chat platform ran into a problem with establishing voice connections. The disruption, which Discord listed on its official status page as “Issues establishing voice call,” began in the afternoon UTC and was not marked resolved until later that evening, leaving gamers, study groups, work teams and online communities searching for another way to talk.
Voice chat is at the centre of how many people use Discord. Servers built around games, hobbies, classes and friend groups often run voice channels all day, and private calls are a routine way for people to stay in touch. When those calls would not connect, the outage was felt immediately, even though the platform did not appear to have shut down completely.
Key Takeaways
- Discord listed an “Issues establishing voice call” incident on October 31, 2026, starting at 3:26 p.m. UTC.
- Users reported being unable to join voice channels and private calls, with some seeing a “server awaiting endpoint” error.
- Discord later said a fix had been implemented and was being monitored, before marking the incident resolved at 9:43 p.m. UTC.
What Went Wrong for Voice Calls
According to Discord’s status timeline, engineers began investigating the issue at 3:26 p.m. UTC on October 31. The incident was titled “Issues establishing voice call,” which points to the connection step itself: users could often open the app, but the call would not start.
Reports collected during the day described the same pattern. People trying to join a server voice channel or a private call were left waiting, and many reported a “server awaiting endpoint” error. Others said servers loaded slowly, messages were slow to send, or performance felt sluggish overall. The bulk of the complaints, however, centred on voice, which suggests the problem hit real-time communication hardest rather than taking the whole service offline.
Outage-tracking site Downdetector recorded reports rising to 1,565 on October 31 as complaints spread across the United States and beyond. Downdetector figures are based on user reports, not on Discord’s own measurements, so they show how widely people noticed a problem rather than giving an exact count of affected accounts. Even so, the spike, together with Discord’s own status listing, confirms that this was a widespread incident, not a handful of isolated connection failures.
How the Day Unfolded
The timeline matters because it explains why the outage felt so long for people trying to use Discord in the evening. After the investigation began at 3:26 p.m. UTC, Discord said at 7:40 p.m. UTC that a fix had been implemented and that it was monitoring the results. The incident was then marked resolved at 9:43 p.m. UTC, about six hours and seventeen minutes after it began.
That long window covered prime evening hours in Europe and afternoon hours in the Americas, when many gaming sessions, community events and group calls are usually under way. For people who had planned a call around that time, the practical effect was simple: the call either had to move elsewhere or wait.
Discord had not given a cause for the incident in the initial status updates reviewed for this report. That is common during a live incident, when the priority is restoring service, but it also means users should treat any claimed technical explanation circulating on social media with caution unless Discord itself confirms it.
- Incident listed: “Issues establishing voice call”
- Investigation began: 3:26 p.m. UTC, October 31, 2026
- Fix implemented and monitored: 7:40 p.m. UTC
- Marked resolved: 9:43 p.m. UTC
- Downdetector reports: rose to 1,565 on October 31
Why a Voice Outage Hits So Hard
Discord began as a voice tool for gamers, and voice remains one of its defining features. Text channels can carry a conversation slowly, but a live call is how a team coordinates in a game, how a study group talks through a problem, or how friends simply spend time together online. When voice fails, the replacement is not always obvious, especially if the whole group is already gathered in one server.
When those calls would not connect, the outage was felt immediately, even though the platform did not appear to have shut down completely.
The incident also arrived a day after a separate, shorter voice incident on October 30, which Discord listed as resolved after 55 minutes. The two incidents were listed separately on the status page, and they should not be merged into a single outage. The October 31 incident was longer, lasted into the evening UTC, and is the one covered here.
For users, the most useful first step during an outage like this is to check the official status page rather than reinstalling the app or changing settings repeatedly. If the status page shows a known voice issue, the problem is on the service side, and local troubleshooting is unlikely to fix it. Keeping a backup channel, such as a group chat in another app or a phone call, can also help a group stay in touch until voice returns.
Related technology coverage on NightLust includes a report on a tampered coding extension that raised security concerns and a report on Apple Intelligence coming to China in December, both published on October 31.
What to Watch Next
Discord has marked the October 31 voice incident resolved, and its status page showed all systems operational afterwards. What remains to be seen is whether Discord publishes any further detail about what caused the voice connection failure, and whether voice performance stays stable in the days that follow. For now, the confirmed picture is the one in the status timeline: a voice-call problem that began in the afternoon UTC, a fix later that evening, and a resolution before the night was over.