Discord outage history

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.

Discord users saw some servers disappear or become inaccessible in the client starting at Sep 3, 2026 9:32 PM UTC. The issue affected a subset of servers, with affected users unable to access or view those servers while others remained functional. The disruption persisted for about 35 minutes before the issue was resolved.

Discord's status page confirmed the problem, noting that some servers were unavailable in the client. The incident was marked resolved by Sep 3, 2026 10:07 PM UTC as services returned to normal.

Discord experienced a brief partial outage starting at 2:37 PM UTC when a subset of its servers became unavailable in the client. The Discord status page indicated that the issue had been identified and a fix was being implemented at 2:57 PM UTC. Services were restored by 3:02 PM UTC. For users, this meant intermittent access to specific servers and channels during the event, with normal operation resuming after the fix was deployed.

Discord users faced a global outage affecting voice calls as the voice endpoint selection service failed, preventing calls from starting or connecting to endpoints. The impact appeared around 11:15 PM UTC, with a wave of user reports from across regions indicating calls could not connect or audio was unavailable. Discord’s status updates described an issue with voice endpoint selection, noting that calls may fail to start or fail to obtain an endpoint. StatusGator detected the issue at Sep 2, 2026 11:18 PM UTC, about 9 minutes and 41 seconds before official acknowledgment, illustrating rapid user-reported impact.

Users across Discord reported widespread server unavailability and degraded voice experiences as the outage unfolded. The disruption began at 4:17 PM UTC with many servers offline, affecting both text and voice features and causing missing servers or temporary connection issues for users around the world. The impact was felt across regions, with reports from North America and Europe and other areas indicating broad disruption.

Discord's status updates confirmed ongoing investigation and degraded experiences on some servers, with messages at 5:07 PM UTC and 5:52 PM UTC. The service was restored by 6:22 PM UTC, marking the end of the incident after a little over two hours of disruption.

An outage began at 10:57 PM UTC when Discord reported that some servers were not available for some users. The issue appeared to extend to other services, with voice calls and activities impacted for affected accounts. Discord posted follow-up updates indicating remediation steps were underway as the impact persisted into the early hours, with the situation still evolving by 11:42 PM UTC.

The service recovered over the next couple of hours and was restored by 12:52 AM UTC. Overall, the disruption lasted roughly two hours, during which a subset of users experienced inability to access certain servers and related features.

Discord users reported the app would not load and voice chat connections were unusable. Many described being unable to log in, load messages, or join servers, with screens stuck on loading indicators and errors about checking for updates. The disruption affected both desktop and mobile experiences and interrupted ongoing voice conversations. The incident appears to have begun around 6:06 AM UTC and continued for several minutes, with activity in reports stretching through 6:53 AM UTC.

Discord did not publish official status updates during the window. StatusGator detected the issue at Aug 26, 2026 6:06 AM UTC, indicating an Early Warning Signal ahead of any acknowledgement. A surge of user reports began around 6:00 AM UTC and pointed to a broad disruption affecting loading, message access, and voice chat, including mentions of RTC-related problems. The signal ended at 6:53 AM UTC.

Discord users worldwide experienced a brief disruption when attempting to establish voice calls. The Discord Status page logged an issue with establishing a call and noted that the team was investigating. The outage began at 6:12 AM UTC and was resolved about five minutes later, by 6:17 AM UTC, with voice and call features returning to normal. Some users also reported related delays and voice server wait times during the incident.

An Early Warning Signal from StatusGator captured widespread reports of app loading issues starting at 12:57 AM UTC (ending 1:57 AM UTC). This early signal preceded the official acknowledgement by several days, which occurred at 6:12 AM UTC. Reports spanned multiple regions and suggested broader app loading and voice-related issues during that period, indicating a global pattern of impact.

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.