Discord outage history

Discord experienced a global outage that affected web, desktop, and mobile clients. Users reported being unable to load the app, send or view messages, or load attachments, with many experiencing servers not responding and pages failing to load. The incident appeared worldwide, with reports coming from North America, Europe, and beyond. StatusGator flagged the issue starting at 12:56 PM UTC, ahead of any official Discord acknowledgement, and the outage was reported as resolved by 5:28 PM UTC.

Global Discord users faced a service-wide outage that prevented establishing voice calls and disrupted voice chat, voice servers, and screen sharing. The incident began at 3:26 PM UTC with widespread reports of calls failing to connect, and Discord acknowledged the issue at Oct 31, 2026 3:27 PM UTC while they investigated. StatusGator detected the issue before the official acknowledgment, noting an Early Warning Signal for voice calls unavailable due to connectivity issues. The disruption persisted for about four and a half hours, affecting real-time communication across regions.

Discord experienced a brief disruption affecting voice call setup. The incident began at 3:27 PM UTC when the Discord Status page reported 'Issues establishing voice calls' and said investigators were on it. Some users had already reported problems around 3:15 PM UTC before the official acknowledgement, indicating early activity prior to the update. By 3:47 PM UTC the page showed the issue resolved as Discord restored voice call functionality after updates noted the investigation had concluded. During the outage, users attempting to join voice channels or start calls likely experienced failures or delays, while other features remained accessible. The disruption lasted roughly twenty minutes.

Discord users experienced voice and video issues during a degradation of the Third-party / Tax Calculation Service. The degradation began at 5:07 PM UTC and persisted through 4:17 AM UTC, lasting about 11 hours and affecting voice chat, calls, and video features for many users. Reports from regions including North America, Europe, and Russia described symptoms such as calling not working, unable to connect to voice chat, and video and calls unresponsive.

Discord's status page tracked the Third-party / Tax Calculation Service as degraded during the incident, with the component returning to normal after the final transition to up at 4:17 AM UTC. The incident impacted features that rely on the service, and users began regaining access as the service stabilized.

Discord experienced a brief degradation across its API and Media Proxy components as an elevated API error rate was reported. Users attempting API calls or using media-related features may have encountered failures or delays. The issue began at 8:12 PM UTC and was resolved by 8:57 PM UTC after roughly 45 minutes of degraded operation.

Discord's status page indicated that engineers were investigating the elevated API error rate, with both the API and Media Proxy affected during the incident window. By 8:57 PM UTC, services returned to normal as the components were restored.

Discord experienced a period of degraded service caused by an age group status mismatch across devices. Android users were most affected, with issues loading, sending messages, and general app responsiveness. The problem began at 2:12 AM UTC and led to a broader impact on user experience as the mismatch propagated beyond a single client.

Discord’s status updates indicated a fix was implemented and the team monitored results. The Android component transitioned out of the degraded state and services recovered by 3:37 AM UTC, with users reporting improved messaging and loading behavior afterward. The outage lasted roughly an hour and a half, and affected users across multiple regions who rely on real-time communication.

Discord users worldwide faced an outage where the mobile and desktop apps, and the Discord website, failed to load or were stuck on startup. This prevented login and message sending, affecting both direct messages and server interactions across platforms. The disruption began around 10:45 AM UTC and lasted for most of the afternoon, with reports concentrated in the Philippines and other regions.

StatusGator detected an Early Warning Signal at 10:45 AM UTC ahead of any official Discord status page updates, and there were no official updates published during the event. By 3:55 PM UTC, the early warning signal ended and reports began to ease, suggesting stabilization. The outage affected core login, messaging, and loading across mobile, desktop, and web interfaces, with a global footprint though most reports clustered in the Philippines.

A global outage hit Discord's voice chat service, leaving users worldwide unable to connect to voice calls or join voice channels. Users reported errors such as waiting for voice server and calls failing to connect across regions, signaling a widespread disruption to real-time communication. StatusGator detected voice connectivity issues at 6:18 PM UTC, about one minute before Discord publicly acknowledged the problem at 6:19 PM UTC. The outage began at 6:19 PM UTC and persisted for a little over two hours.

Discord users across the globe were unable to establish voice calls and experienced degraded audio quality for roughly 43 minutes. The incident began around 9:34 PM UTC when the Discord status page reported an issue establishing voice calls. An Early Warning Signal appeared earlier, describing 'Voice calls not connecting or audio not working' and lasting until 9:36 PM UTC. StatusGator detected the issue at Sep 16, 2026 9:28 PM UTC, about 5 minutes 16 seconds before official acknowledgment. Discord updated the incident at 9:47 PM UTC stating that the issue had been identified and a fix was being implemented, with service restored by 10:17 PM UTC.

Impact was felt mainly in voice channels and real-time audio across regions; users could not join or hear others in voice chats, with some reports mentioning issues around screen sharing. The outage was widely discussed on social platforms and reflected in user reports across several regions, indicating broad impact before restoration. Discord’s status page communicated ongoing investigation, acknowledgment, and eventual restoration as the team applied a fix.

Discord experienced a brief API issue that disrupted media rendering for some users. Several reports described GIFs not loading and other API-dependent features behaving inconsistently. The problem began at 7:07 PM UTC and was resolved by 7:22 PM UTC after Discord stated they were investigating the issue and later confirmed services had returned to normal. The disruption was short and limited in scope, with improvements noted as the API errors were addressed.