Discord outage history

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.

Discord users attempting to buy Nitro subscriptions or Shop items in the Android app could not complete payments due to an outage affecting Google Play. Purchases on iOS, web, and desktop were unaffected, and existing subscriptions remained active. The issue began at 4:17 PM UTC and was resolved by 4:47 PM UTC, lasting roughly 30 minutes.

Discord's status page attributed the disruption to an ongoing Google Play outage and noted that Google was monitoring the situation, with an update to follow when service was restored.

Users across the globe were affected by a session unavailability that left many stuck on loading screens, with profiles not loading, images failing to send, and reactions or voice features intermittently not working. The disruption spanned multiple core experiences, including loading, messaging, media uploads, and bot or API interactions, causing a noticeable decline in daily usage for about forty-five minutes. Discord first flagged the issue as an investigation around Sep 15, 2026 2:27 PM UTC, with an update at Sep 15, 2026 2:47 PM UTC saying the issue had been identified and that restoration work was underway, and service was restored by 3:02 PM UTC.

Users attempting to open Discord on desktop or via the web experienced loading failures beginning around 12:10 AM UTC. Reports described apps getting stuck on startup, white screens, and repeated update checks, with mobile clients largely unaffected. The disruption affected desktop and web access for users across North America for several hours, hampering conversations and server access as logins and channel loads failed.

Discord experienced degraded image downloads due to latency spikes in its Media Proxy. The issue began at 4:27 PM UTC and affected users across the service, with images taking longer to load and some downloads failing. A fix was implemented by 4:32 PM UTC and monitoring continued as adjustments were made; a further fix was deployed by 5:42 PM UTC and the service returned to normal at 5:47 PM UTC, after a little over an hour of degraded performance.

Discord users across the globe were unable to start or join voice calls and connect to voice servers, while text chat remained generally available. The outage began around 4:24 AM UTC when Discord's status page reported an investigation into an issue with establishing voice calls, and affected users across multiple regions.

StatusGator detected an Early Warning Signal at Sep 11, 2026 3:58 AM UTC, about 25 minutes before Discord acknowledged the issue on the status page. The provider's updates indicated ongoing investigation and then restoration as services recovered, with many users reporting voice connectivity returning by 6:22 AM UTC.