AWS Servers Down: Full List of Games Affected Including Fortnite, ARC Raiders & Rocket League AWS Servers Down: Full List of Games Affected Including Fortnite, ARC Raiders & Rocket League
Fortnite Servers Down Today: What’s Causing the Outage and When Players Can Expect a Fix Fortnite Servers Down Today: What’s Causing the Outage and When Players Can Expect a Fix
When Verizon Went Down, Public Safety Was Put at Risk When Verizon Went Down, Public Safety Was Put at Risk
Who Pays When Verizon Goes Down? Who Pays When Verizon Goes Down?
Users were experience a global Discord outage — as Down Detector peaked at well over 7,500 reports around 8:40 a.m. Pacific.
Users were experience a global Discord outage — as Down Detector peaked at well over 7,500 reports around 8:40 a.m. Pacific.

So far, Discord has not issued any official statement about the issue.

Discord experienced a late-night outage Thursday that disrupted service for thousands of users across the United States, with voice communication and login features among the hardest hit.

According to outage tracker Downdetector, reports began to surge around 11:00 p.m. EDT, quickly spreading across major U.S. regions as users flagged widespread connectivity problems.

Thousands Report Issues, Including Login Failures

New data from multiple reports indicates the scale of the disruption may be larger than initially observed. At its peak, more than 4,500 users reported issues, with complaints spanning several core features of the platform.

Users reported problems including:

  • Failure to log into accounts

  • App instability and loading issues

  • Voice calls not connecting or dropping

The inclusion of login failures suggests the outage extended beyond voice infrastructure, potentially affecting authentication or backend services.

“Awaiting Endpoint” Error Signals Voice Server Problems

A significant portion of users encountered the error message “server awaiting endpoint,” which typically indicates that Discord’s client cannot establish a connection with its voice servers.

Consistent with both current and past incidents:

  • Voice channels failed to connect

  • Calls dropped immediately after joining

  • Streaming and live audio features were unavailable

Data from outage monitoring platforms shows that voice calls accounted for the majority of reported issues, reinforcing the likelihood of a backend voice service disruption.

Pattern Reflects Ongoing Reliability Challenges

The incident follows a series of outages affecting Discord in recent months. In January 2026, for example, over 4,600 users reported similar issues, again largely tied to voice functionality.

Historical outage data shows recurring problems such as:

  • Voice connection failures

  • App loading issues

  • Messaging or login disruptions

A late-February 2026 incident also caused global failures in app loading and voice calls, highlighting persistent vulnerabilities in Discord’s infrastructure.

Signs of Pre-Existing Instability

Discord’s own status history indicates the platform had already been experiencing issues shortly before the outage. On March 19, the company listed an “unresolved incident” involving failures to start new voice calls, suggesting the disruption may have been part of a broader, ongoing problem.

No Official Explanation Yet

As of now, Discord has not released a detailed statement explaining the cause of the outage or confirming whether all services have been fully restored.

Based on similar past events, possible causes include:

  • Server overload or infrastructure failure

  • Cloud service disruptions

  • Network routing or regional latency issues

In some previous outages, Discord’s performance issues have coincided with problems at its underlying cloud providers, which can impact voice and real-time communication systems.

Impact on U.S. Users

The outage occurred during peak evening hours in the U.S., a time when Discord sees heavy usage for:

  • Online gaming sessions

  • Group calls and communities

  • Remote collaboration and classes

Even short disruptions can have immediate effects, particularly for users relying on Discord as a primary communication tool.

What Users Can Expect

While outages of this type are often resolved within hours, the recurrence of similar issues raises concerns about long-term reliability as Discord continues to scale.

For now, users are advised to:

  • Check Discord’s status page for updates

  • Retry connections periodically

  • Use alternative platforms if communication is critical

Who Owns Discord?

Discord is a privately held company owned and operated by Discord Inc., headquartered in San Francisco.

The platform was co-founded in 2015 by Jason Citron and Stan Vishnevskiy, with Citron continuing to serve as CEO.

Unlike many major tech platforms, Discord is not publicly traded, meaning it is not owned by public shareholders. Instead, it is backed by a range of private investors, including venture capital firms such as Index Ventures and Greylock Partners.

In 2021, Microsoft reportedly held acquisition talks with Discord valued at around $10 billion, but the deal was never finalized as Discord chose to remain independent.

Recent Discord Outages and Reliability Issues

The latest outage is part of a broader pattern of service disruptions affecting Discord over the past year, particularly in the United States.

Recurring Voice and Connection Failures

Several recent incidents share similar characteristics:

  • Voice chat failures and “awaiting endpoint” errors

  • Difficulty joining or maintaining calls

  • Partial outages where text chat remains functional

These issues point to ongoing strain in Discord’s real-time communication infrastructure.

Notable Recent Incidents

  • January 2026: Thousands of users reported outages, with voice chat accounting for the majority of complaints.

  • February 2026: A broader disruption affected app loading, login, and voice features globally.

  • March 19, 2026: Discord’s status page flagged an unresolved issue preventing new voice calls, just hours before the latest outage spike.

Across these events, a consistent pattern emerges: voice services are the most vulnerable component, especially during peak usage hours in North America.