Apex Legends experienced a significant service disruption on May 22, leaving players across all platforms unable to connect to matches. The outage, which began unexpectedly during the day, has been acknowledged by both Electronic Arts and Respawn Entertainment, with the official Apex Legends Live Comms account confirming that a fix is under investigation. The incident is particularly notable because an initial attempt to resolve a matchmaking problem inadvertently created a new, more severe issue that prevented players from joining games entirely.
Widespread Connection Failures on May 22
Reports of connectivity problems began surfacing on social media and the game’s subreddit in the early hours of May 22. Players on PlayStation, Xbox, and PC all reported similar symptoms: an inability to connect to Apex Legends servers, matchmaking queues that never populate, or error messages when attempting to join a lobby. While some users indicated they were still able to connect intermittently, the vast majority experienced a complete service block. The outage appeared to be global in scope, affecting gamers across multiple regions, with no platform spared. EA’s official status page and the Apex Legends Live Comms X account (formerly Twitter) quickly issued a statement acknowledging the problem: “We are aware players are currently unable to connect to a match. We are aware and are investigating. Thank you for your patience.” This was the first public confirmation that the issue was recognized at the highest levels.
Developer Confirms Fix Caused Unforeseen Issue
As the downtime extended into several hours, Respawn Entertainment provided an update that shed light on the root cause. In a statement titled “Update 1,” the developers explained that a previous patch had introduced a matchmaking outage. Their team had developed a fix for that specific problem, but upon deployment, the fix triggered an adjacent, unforeseen issue that now prevented players from joining matches entirely. The official developer communication stated, “Our fix to resolve the matchmaking outage resulted in an adjacent, unforeseen issue now preventing players from joining matches. Our team is continuing to work on this and is hoping to have it resolved ASAP.” This candid admission highlighted the complexity of live-service game maintenance, where a well-intentioned patch can cascade into a more disruptive failure. For the player base, it meant that what began as a limited matchmaking glitch had escalated into a full-scale server lockout.
Context: The Recent May 13 Patch and Known Issues
The May 22 outage occurred just over a week after Respawn released a substantial patch on May 13, which was intended to address a number of bugs and performance problems. That patch, version 3.10.1.000.124, included fixes for several long-standing complaints, but it also introduced new instabilities. According to the official known issues list published by the studio, the May 13 update left behind a significant roster of unresolved problems. These ranged from graphical glitches to in-game item losses and platform-specific crashes. The timing of the May 22 outage suggests that the team may have been deploying a hotfix for these lingering issues when the matchmaking failure occurred, and then the attempted repair backfired.
Complete List of Issues Still Under Investigation
Respawn has published a structured breakdown of current problems divided into two categories: those actively being investigated and those with a fix already in progress. This transparency is valuable for players trying to understand the broader state of the game. Under the “Investigating” heading, the studio lists six key items. First, graphics and brightness settings resetting after a relaunch of Apex, a minor but irritating bug that the team expects to resolve soon. Second, an issue where players respawned from beacons return to the match without a white backpack, and those respawned from deathboxes lose their weapon hop-ups. This is particularly disruptive for competitive play, as it effectively penalizes respawned teammates. Third, general performance issues on various devices and hardware configurations, which may manifest as stuttering or frame drops. Fourth, a specific problem with Caustic’s traps triggering his other traps, creating unpredictable area denial. Fifth, ongoing audio issues that have plagued the game for several seasons, making it difficult to hear enemy footsteps or ability cues. And sixth, increased FPS drops tied to specific CPUs since the start of the current season, which has likely degraded the experience for a segment of the player base.
Known Fixes in Progress
In addition to the items under investigation, Respawn has also acknowledged five problems for which a fix is already in development. These include an Xbox crash tied to in-game chat, which has led to the chat feature being temporarily disabled on that platform. Another issue, seemingly lighthearted but indicative of broader asset management problems, involves some Nessies (the plush toy easter eggs) missing from the firing range. A visual bug with Valkyrie’s vision being blocked when using a shield cell with specific skins is also listed. More seriously, players on any Xbox platform are currently unable to purchase the Ultimate+ Battle Pass tier, a monetization interruption that likely frustrates both players and the publisher. Finally, a server error occurs when batch-opening 50 Wishlist or upgraded Apex Packs, though the studio has confirmed that the items are still granted to the player’s account even if the error appears. This last bug suggests an inventory or UI layer issue rather than a loss of goods, but it still undermines trust in the game’s economy.
Implications for the Apex Legends Community
The prolonged downtime on May 22, combined with the extensive list of unresolved bugs, raises concerns about the operational stability of Apex Legends. The game has historically been popular across all platforms, but frequent outages and persistent technical problems can erode player retention. The fact that a fix for a matchmaking outage introduced an even more severe connection problem indicates that Respawn’s testing and deployment processes may need review. For the millions of players who log in daily, the unpredictability of server reliability is a significant frustration. Competitive play, ranked ladders, and even casual sessions are all impacted when the servers are down or when in-game glitches compromise fairness. The Caustic trap chain-reaction bug, for instance, can alter the outcome of firefights in unpredictable ways, while the audio issues make it harder to react to threats.
Historical Context of Apex Server Issues
This is not the first time Apex Legends has suffered from extended server problems. Since its launch in 2019, the game has experienced periodic outages, often coinciding with major updates, season launches, or special events. The May 22 event is particularly reminiscent of incidents in 2022 and 2024, where matchmaking services failed for several hours and required emergency patches. However, the current situation is compounded by the unusually large number of active known issues. The May 13 patch was supposed to be a stabilizing update, but it instead introduced new bugs while failing to resolve older ones. The audio issues, for example, have been a recurring complaint for years, and players have grown skeptical of promises that a fix is incoming. Similarly, the performance drops tied to specific CPUs appear to be a regression that should have been caught in internal testing.
What Players Can Do While Servers Are Down
For those waiting for the servers to come back online, Respawn has not provided an estimated restoration time. The developers have only stated that they are working on the issue and hope to have it resolved as soon as possible. In the meantime, players are advised to follow the official Apex Legends Live Comms account on X and the game’s subreddit for real-time updates. Some users have reported that they can connect sporadically, but these instances appear to be rare and may depend on regional server load. The company has also encouraged players to report their platform and location when commenting on social media, which helps engineers pinpoint geographic scope. It is worth noting that the May 13 patch included a note about server error when batch-opening packs, so players should avoid bulk opening their Apex Packs until that bug is officially resolved, even if they are able to log in after the current outage ends.
Long-Term Outlook for Stability
The May 22 downtime serves as a reminder that even mature live-service games face infrastructure challenges. Respawn’s transparency in admitting that a fix caused an unforeseen issue is commendable, but the community’s patience is finite. The company has a history of eventually resolving major outages, but the cumulative effect of bugs, crashes, and performance degradation can drive players to competing titles. With the battle royale genre remaining highly competitive, reliable servers and polished gameplay are baseline expectations. The next few days will be critical for Respawn as they deploy the correct fix and then work through the backlog of other known issues. Players will be watching closely to see if the promised “fix in progress” items actually ship in a timely manner, or if new problems continue to emerge from each patch.
Final Notes for Affected Players
If you are still unable to connect to Apex Legends on May 22, you are not alone. The outage is widespread and acknowledged by both EA and Respawn. The official communication channels remain the best source for updates. The game’s subreddit is also a useful resource for community discussions and workaround tips. As the developers continue to work on the matchmaking fix that went wrong, it is likely that a new update or hotfix will be pushed in the coming hours. Once service is restored, players should check for any patch notes or announcements regarding additional fixes. In the interim, consider revisiting the list of known issues to be aware of potential bugs that may persist even after the server connectivity is restored. The situation is evolving, and this article will be updated as new information becomes available.
