Discord outage history

Discord experienced a global outage that prevented users and bots from sending messages, and soon affected all Discord interactions including loading channels and logging in. The issue began around Aug 7, 2026 10:22 PM UTC as the API faltered, with a sharp surge in user reports indicating widespread disruption across regions. StatusGator flagged the issue earlier at Aug 7, 2026 10:17 PM UTC, roughly 4 minutes before the provider acknowledged the problem. The impact was broad and user experiences included messages failing to send, conversations not loading, and broader connectivity problems across devices.

The provider confirmed the scope expanded to all Discord interactions, and the primary affected component was the API. Recovery began around Aug 7, 2026 10:47 PM UTC, with services returning to normal in the minutes that followed. The outage appeared global in reach, evidenced by a wide pattern of reports from many regions and devices.

Discord experienced a global messaging outage beginning around 6:52 PM UTC, blocking message sends and causing app experiences to fail to load for many users. The disruption affected mobile and desktop clients across regions, with delays and failed deliveries reported widely as the API faced degradation. StatusGator flagged the issue earlier through an Early Warning Signal when the app and website were not loading or messages failed to send, noted at Aug 4, 2026 5:52 PM UTC, roughly one hour before Discord publicly acknowledged the problem.

A brief Discord outage disrupted direct message delivery and login for some users. Reports of DM and login issues began around 5:45 PM UTC, and Discord’s status page documented a transition from up to down at 5:52 PM UTC with notes that session starts and DM delivery were down. The service returned to normal after about fourteen minutes, with a resolution by 6:07 PM UTC. During the window, users attempting to send or receive DMs or log in may have experienced delays or failures.

Discord users faced an outage in voice chat as calls could not connect and screensharing stopped functioning. The disruption affected real-time communication and screen sharing for many users, with reports describing pervasive voice connection failures and intermittent screenshare issues.

Impact began around 11:27 PM UTC as an Early Warning Signal appeared from user reports, with activity intensifying by 11:30 PM UTC. Discord's status page acknowledged the issue at 11:34 PM UTC, noting an inability to establish voice connections and that teams were investigating the cause.

StatusGator detected the issue at Jul 22, 2026 11:27 PM UTC, about 6 minutes before official acknowledgment. The service began recovering, with voice services and screensharing returning to normal by 11:52 PM UTC. The outage was relatively brief but widely disruptive for those relying on Discord for voice communication during that window.

Discord users worldwide were unable to load the mobile app or website during an outage that began at 1:36 AM UTC and was resolved by 2:55 AM UTC. StatusGator detected the issue from user reports before Discord publicly acknowledged it, signaling an early warning. The outage affected both mobile and desktop access, with widespread loading failures reported across regions.

Across Europe, North America, and beyond, users described endless loading loops, timeouts, or complete inability to reach Discord services. The pattern of reports indicated a global disruption rather than a localized incident.

Discord did not publish an official status update during the incident window. The service appeared to recover following the resolution time window.

Discord users worldwide faced a service disruption beginning at 12:52 AM UTC when the Discord status page flagged API Errors. The issue prevented core operations such as joining servers, inviting friends, sending messages, and making voice calls. Across the globe, users reported delays and failures spanning the US, Canada, UK, Europe, and Asia-Pacific. A noticeable uptick in user reports mirrored the spread of the outage as the problem persisted.

Official updates from Discord described ongoing API errors and an upstream latency issue, with engineers working to mitigate the impact. The service began recovering and was reported as restored by 3:52 AM UTC, marking the end of the outage after roughly three hours. Users gradually regained access to invites, messaging, and voice features as API responsiveness returned to normal.

Discord users began experiencing intermittent chat issues around 6:47 PM UTC, with the API component showing degraded performance and messages occasionally failing to send. By 7:30 PM UTC reports indicated that users were unable to send messages in several regions as the issue persisted. The status page documented an ongoing investigation and later noted that chat functionality was intermittently affected while the API remained degraded.

The issue began to ease after 8:27 PM UTC when the API component returned to up, and Discord indicated the incident was resolved.

Users across regions reported that the Discord app could not load messages, with some seeing offline indicators or being unable to send messages in both mobile and desktop clients. The issue began to surface in the early evening, with an uptick in reports around 7:30 PM UTC and earlier activity around 6:15 PM UTC, including users in the United Kingdom, Ireland, and Germany, and later observations from other regions. StatusGator flagged an Early Warning Signal at 7:14 PM UTC due to messaging issues in the Discord app, and the alert remained active through 7:47 PM UTC.

Discord users around the world were unable to sign in, load messages, or connect to servers as the Discord API experienced general errors. The outage began around 8:27 PM UTC when an Early Warning Signal flagged widespread loading issues across devices (the signal ended 9:38 PM UTC). The Discord status page described the incident as General API errors, with the API component moving to a degraded state and affecting both mobile and desktop experiences.

Official updates show a fix being implemented around 9:32 PM UTC and monitoring of results, with services gradually restored by 9:47 PM UTC. The outage drew a large wave of user reports spanning many regions, with people reporting sign-in failures, chats not loading, or messages not sending during the peak between 9:15 PM UTC and 9:30 PM UTC.

An outage on Discord affected voice calls, direct messages, and screensharing across mobile and desktop clients. Users spanning multiple regions reported being unable to connect, dropping from calls, or having screensharing fail, with activity peaking in the evening. The disruption began at 6:28 PM UTC and reports intensified through the next hour, including accounts from Australia, India, the United Kingdom, and the United States.