Discord went down hard on Wednesday, knocking out voice and video calls for users worldwide and leaving millions of gamers staring at the dreaded "awaiting endpoint" message with no way into their voice channels.
The platform itself confirmed the severity, labeling it a "major outage" on its official status page. Here's the lowdown on what happened, how long it lasted, and where things stand now.
When voice channels went silent
The outage hit voice and video functionality specifically, leaving text channels largely unaffected. Users attempting to join voice servers were met with a spinning connection indicator and the "awaiting endpoint" message, a sign that Discord's voice routing infrastructure had failed to respond.
According to reports tracked by outage monitoring services, over 14,000 users flagged the issue at peak disruption. The real number affected was almost certainly higher, given that not everyone reports outages through those channels. Discord posted on X that its team was "actively investigating an issue preventing users from connecting to Discord," which at least confirmed this wasn't just a local problem on your end.
The platform's status page posted an update at 1:07 pm PDT stating: "We believe we have identified the issue and are taking action to try and restore voice traffic." That's the kind of message that tells you the engineers are in the room and working, even if it doesn't tell you exactly what broke.
The fix and what's still being tracked
Voice and video service has since been restored. Discord confirmed that "voice and video should have recovered and users should be able to connect to voice calls," as reported by PC Gamer's coverage of the outage.
The restoration took over an hour from the point the outage was publicly acknowledged. That's a meaningful window of downtime for a platform that sits at the center of gaming coordination, from raid callouts in World of Warcraft to real-time squad comms in Valorant.
danger
Discord noted it was still "tracking down issues" with its API even after voice service came back online. If you notice any lingering weirdness with connections or message delivery, that context is worth keeping in mind.
The key here is that voice was the primary casualty. Text messaging continued functioning for most users throughout the incident, which softened the blow somewhat.
What this means for gamers who rely on Discord daily
Outages like this are a sharp reminder of how deeply Discord is woven into the gaming experience. Over 48% of unreleased games have a Discord server, according to previous reporting, and for active gaming communities, a voice outage doesn't just mean inconvenience. It means a raid gets called off, a tournament lobby goes quiet, or a streaming session loses its coordination layer entirely.
The platform has faced infrastructure hiccups before, including a separate bug earlier this year that caused the app itself to take over two minutes to launch. Each incident chips away slightly at the "it just works" reputation that made Discord the default communication tool for gamers in the first place.
Service is back, but Discord still owes its users a proper post-mortem on what caused the voice infrastructure to collapse in the first place. Watch the status page for any follow-up incident report. Make sure to check out more:
