Discord Outage History

Discord users worldwide faced an outage that began around 7:22 PM UTC, with the API and Gateway components down, preventing connections and causing voice chat problems for many. An Early Warning Signal was detected when StatusGator observed issues at 7:15 PM UTC, about 7 minutes and 22 seconds before the official acknowledgment. The disruption affected core communication features and was experienced globally, with reports from many regions indicating widespread connectivity and voice-call issues.

Discord's official updates showed the incident evolving: at 7:47 PM UTC they noted continued investigation and impacts to voice connectivity, and at 8:07 PM UTC they said the issue had been identified and actions were underway to restore voice traffic. As of 8:07 PM UTC the outage remained active for many users and recovery was ongoing.

Discord experienced a global outage affecting app loading and voice call functionality. Some servers appeared unavailable and voice calls could not start, causing widespread user disruption. StatusGator detected the issue at Feb 27, 2026 8:36 PM UTC and Discord acknowledged the problem at Feb 27, 2026 9:57 PM UTC, describing it as Unavailable Servers and Voice Calls. This early warning came from user reports, with activity peaking in the 21:15–21:30 UTC window and continuing as the incident progressed. Recovery followed a series of official updates as the service returned to normal by Feb 27, 2026 10:27 PM UTC.

The Discord app experienced a global outage that prevented users from loading the service. Initial user reports began at 7:15 PM UTC UTC, with regions including Brazil and Poland noting the app was not loading. StatusGator detected the issue at Feb 23, 2026 7:20 PM UTC. The outage lasted about 7:45 PM UTC UTC.

Discord did not publish any official status updates during the outage, leaving users without formal guidance until the service stabilized.

Reports indicate a broad geographic footprint, with activity from Europe and South America suggesting a global disruption to messaging and presence features. The reach and brief duration indicate a major incident.

Discord experienced an outage affecting loading and voice call connectivity starting at 3:36 AM UTC. Users reported the Discord client would not load and voice calls would not connect, with additional symptoms including messages failing to send and the app failing to load. The disruption lasted approximately 30 minutes, ending at 4:06 AM UTC.

StatusGator detected the issue at Feb 23, 2026 3:36 AM UTC, about 30 minutes before any official acknowledgement. A noticeable surge in user reports around 03:45 UTC indicates a broad impact across users, and there were no official status updates posted by Discord during the incident.

StatusGator detected an Early Warning Signal for Discord at Feb 10, 2026 8:28 PM UTC, ahead of the provider's official acknowledgment. The outage began at 8:28 PM UTC and caused messages to fail loading across mobile, desktop, and the web. Some users reported login or session issues as well. The incident lasted about 3 hours and 16 minutes, with most services returning to normal by 11:44 PM UTC.

Impact was global, with user reports from the Americas, Europe, and Asia-Pacific indicating widespread disruption to messaging. Users could not load messages, send messages, or access chats on iOS, Android, desktop apps, or the web client. Discord did not publish official status updates during the incident, leaving many users to rely on external reports until services recovered.

Discord users across Europe and North America were unable to load the app or access the website, with login attempts failing and chats not loading across desktop, mobile, and web clients. The outage disrupted core messaging and presence features for several hours, affecting communication for many users.

Discord experienced a partial outage affecting the ability to send messages in direct messages and in server channels. The issue appeared global, with hundreds of user reports across multiple regions and platforms. The outage lasted about 5 hours and 30 minutes, beginning at 12:37 AM UTC and ending by 6:07 AM UTC. Discord's status page documented an ongoing investigation and later recovery, with the API and Search components listed as affected; the provider issued two status updates during the incident.

Discord's voice services experienced a global outage beginning at 9:03 PM UTC, causing voice calls to fail for many users and making it impossible to join or stay in voice channels. Reports described issues such as 'Awaiting endpoint', inability to connect to calls, and general VOIP disruption across numerous regions. The surge in user reports peaked around 9:30 PM UTC and appeared to persist for about 51 minutes, with the early warning signal ending at 9:54 PM UTC.

The Discord app and website experienced a global outage, preventing users from loading the app or accessing the web client. Reports spanned across regions including North America, Europe, the Middle East, and beyond, indicating broad impact. The outage began on 6:05 PM UTC and lasted about 9 hours and 45 minutes, until 3:50 AM UTC.

Discord did not publish official status updates during the incident. StatusGator logged an Early Warning Signal at Jan 10, 2026 6:05 PM UTC based on user reports, indicating issues were observed before any official acknowledgment. The outage affected both mobile and desktop clients, with symptoms including the app not loading and the website being inaccessible, as reported by users across multiple cities globally.

Discord users across the US Northeast experienced an outage where the app and website would not load or connect. Reports from Massachusetts, Connecticut, New York, and Vermont indicated failures to launch the app, load the site, and join voice channels, with the disruption lasting about 28 minutes from Dec 29, 2025 2:09 AM UTC to 2:37 AM UTC. StatusGator recorded an Early Warning Signal based on user reports before Discord posted any public status updates, and there were no official status changes observed during this window. The outage appeared regionally focused rather than global.