Discord Voice Calls Were Disrupted for 6 Hours on Oct. 31

Discord recorded a voice-call connection issue on Oct. 31 that lasted 6 hours 17 minutes, according to the incident’s start and resolution times. The company marked it resolved at 2:43 p.m. Pacific. The incident followed a shorter, similar disruption on Oct. 30. Discord’s status history

What happened

Discord opened an incident titled “Issues establishing voice call” at 8:26 a.m. PDT on Oct. 31, then posted that a fix was being monitored at 12:40 p.m. and marked the incident resolved at 2:43 p.m. Those timestamps span 6 hours 17 minutes. Discord’s status page did not publish a cause or a more detailed account of the impact.

The day before, Discord logged a separate voice-call incident from 8:23 to 9:18 a.m. PDT, a 55-minute window. The back-to-back entries make the Oct. 31 event notable, but the status record does not establish that the two incidents had the same cause.

RealUptime’s incident history independently mirrors Discord’s reported Oct. 31 start and resolution times, calculating the same 6-hour-17-minute interval. Its record distinguishes Discord’s status declarations from its own checks.

Current status and what to do

Discord’s status page currently lists its systems, including Voice, as operational. If voice calls fail to connect again, check Discord Status before troubleshooting your device or network; an active service incident can look like a local connection problem.

Sources

Discord Status incident history

RealUptime Discord incident history

Timeline checked Nov. 1, 2026. The reported duration is calculated from Discord’s published start and resolution times; Discord did not state a cause.