Discord’s voice server ran into trouble on September 10, leaving users unable to establish voice calls while the company said it was investigating the problem. By 12:21am ET, Discord’s Status Page had acknowledged the issue, and Downdetector had already logged over 14,000 people facing problems with the app.
The scale of the complaints shows why the search term Discord Waiting For Voice Server spiked so quickly. On Downdetector, 90% of reports were tied to voice calls, which made the outage feel less like a broad app slowdown and more like a break in the feature many people were using at that moment.
That mattered because voice is where the service becomes immediate. The problem was centered on establishing voice calls, and the outage was visible on the Downdetector map, which showed Houston and New York with the highest spike in Discord issues. Discord did not provide a timeline for when services would be back up, leaving users with no clear sense of how long the disruption would last.
For some users, the problem appeared to ease on its own. Others said they were still dealing with failures, and some reported streaming problems even after voice calls seemed to come back. That split experience left the outage looking partially resolved for one group while continuing to block others, which is often what makes these incidents harder to pin down in real time.
The Waiting for Voice Server or Awaiting Endpoint error can appear during a server-side outage, a temporary network glitch, or a blocked regional connection, and users were pointed toward a few basic steps while the issue was being worked on: restarting Discord completely, changing the Voice Region, switching the network, or flushing the DNS. But with Discord still investigating and no restoration timeline in place, the unanswered question is how quickly voice services will return for everyone, not just the first users who saw them come back.
