Discord Outage History

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.

Discord users worldwide faced an outage starting at 7:22 PM UTC that blocked connections to the service and disrupted voice and video features. The disruption hit core components API and Gateway, preventing sign-in, joining calls, and voice traffic. StatusGator detected the issue earlier at 7:15 PM UTC, about 7 minutes before Discord officially acknowledged the problem.

Discord's status page indicated ongoing investigation throughout the evening. At 8:07 PM UTC the team said they had identified the issue and were taking action to restore voice traffic. By 9:27 PM UTC the page noted that voice and video should have recovered while API issues persisted. Services gradually recovered, with API and Gateway coming back up by 10:42 PM UTC. The outage lasted roughly three hours.

Discord users experienced degraded performance affecting streaming and messaging due to a networking issue impacting Discord's cloud connectivity. Impact began around 2:53 PM UTC, with early user reports arriving from around 2:15 PM UTC through 3:15 PM UTC. Users reported voice calls failing or experiencing delays and features such as streaming and messaging were impacted. The service status indicated elevated errors starting at Mar 25, 2026 3:22 PM UTC as the team investigated with their cloud provider; a later update at Mar 25, 2026 3:47 PM UTC said the source was identified and recovery was being monitored. By 3:52 PM UTC, API and Push Notifications had returned to normal. A report from North York, Canada at 3:23 PM UTC described voice calls awaiting endpoint.

Discord users faced a major outage affecting voice calls, with new calls failing to be created and users unable to connect to voice channels. The disruption appeared global, with reports from across North America, Europe, and other regions indicating degraded or unusable voice chat. Impact began around 2:52 AM UTC, and users reported that calls could not start and endpoints appeared unavailable. StatusGator recorded an Early Warning Signal earlier at Mar 20, 2026 2:14 AM UTC, about 37 minutes before Discord acknowledged the outage, suggesting a period of user-reported issues ahead of the official page update. Symptoms described in user reports included calls failing to connect and messages like Awaiting endpoint, consistent with a voice service disruption.

Discord users across the United States faced an outage that prevented the app and website from loading. The disruption affected the desktop and mobile apps as well as the web experience, leaving many stuck on launch or loading screens and some reporting sign-in issues. The outage began at 11:42 PM UTC and was resolved by 4:52 AM UTC.

Discord experienced a brief outage in which applications returned 503 errors, with bot traffic potentially affected. The incident began at Mar 12, 2026 8:52 PM UTC and lasted about 15 minutes, as UK-based users (including Swadlincote, England) reported issues starting around 8:45 PM UTC and again near 9:00 PM UTC. During the disruption, typical user experiences such as sending messages, joining servers, and interacting with bots were impacted. The interruption appeared to be contained and resolved once services were restored at the end of the window.

Discord experienced a partial outage that affected the Gateway component, causing some servers to be unavailable for roughly 30 minutes. The issue began at Mar 11, 2026 11:07 PM UTC and was resolved by Mar 11, 2026 11:37 PM UTC. During the window, a small number of users reported connectivity issues, consistent with a degraded gateway path rather than a full service outage. Discord noted that a fix had been implemented and they were monitoring the results as the Gateway returned to normal, with traffic restored shortly after. The incident appears to be scoped to a subset of servers and did not indicate broader platform disruption.

Discord faced a multi-phase outage in early March 2026 that affected guild access, messaging, and voice connections. The incident began with A/V E2EE enforcement updates for non-stage voice calls, with warnings issued starting Mar 2, 2026 8:07 PM UTC that older clients could have voice connections rejected. The first clear service impact followed on 1:37 AM UTC as some guilds became unavailable, and mitigation efforts continued through the next day.

The disruption broadened over the next days, with ongoing enforcement-related changes and age-verification issues in the UK/AU reported around Mar 6, 2026 3:27 AM UTC to Mar 6, 2026 3:52 AM UTC. On 5:12 PM UTC, users began reporting problems sending and loading messages, and the issue intensified, peaking with a surge in reports around 5:15 PM UTC to 5:30 PM UTC. A fix was rolled out by 5:32 PM UTC, with API and client components gradually recovering over the next hours.

By Mar 11, 2026 5:27 PM UTC Discord had resumed normal operation, marking the end of the outage. Across Web, Desktop, Android, and iOS clients, users experienced outages and degraded performance in guild access, messaging, and voice during the peak of the incident, with the heaviest impact concentrated during the late UTC window on March 9.

Discord users faced degraded presence indicators and direct message delivery failures, affecting how people see friends and send messages. The disruption began with user reports around 9:15 PM UTC and Discord flagged an investigation around 9:57 PM UTC as the Gateway component came under scrutiny. Updates described continued issues with presence and DM delivery, with a fix in progress and monitoring ongoing.

Over the next hour, remediation efforts led to a fix around 10:52 PM UTC and monitoring of results, with the service returning to normal by 10:57 PM UTC. This was a partial outage affecting presence updates and DM delivery rather than a complete service outage.