Is the Game Down? A Multiplayer Outage and Connection Troubleshooting Checklist
When matchmaking fails, this checklist helps you determine whether the game is experiencing a wider outage, your platform is having problems, or your home connection needs attention. It also shows what to record before contacting support, so you do not waste time repeating fixes that cannot resolve a server-side issue.
Overview
The quickest way to answer “is the game down?” is to compare several signals instead of relying on a single outage report. A game may be unavailable because its own servers are offline, because PlayStation Network, Xbox services, Nintendo services, Steam, or another account provider is having trouble, or because a local network issue is blocking the connection.
Start by identifying the exact failure. “The game will not launch,” “I cannot sign in,” “matchmaking is not working,” and “I disconnect during matches” point to different parts of the online service. A failed sign-in can indicate an account or authentication problem, while repeated matchmaking errors may involve regional capacity, cross-play settings, NAT behavior, or a temporary service disruption.
Use this order of operations:
- Check the game’s official server-status page, support account, or maintenance notice.
- Check your platform’s official network-status page.
- Look up the exact error code and read the developer’s recommended steps.
- Test another online game or service on the same device and connection.
- Only then restart equipment or change network settings.
This approach prevents a common mistake: changing DNS settings, forwarding ports, or reinstalling a game when the underlying service is offline for everyone.
What to track
Official service status
Check the developer’s official status page first. Look for terms such as operational, degraded performance, partial outage, maintenance, and investigating. These labels are not interchangeable. A service can be online while a specific feature, region, platform, or login system is impaired.
Also check the game’s verified social channels and support site, but treat user posts as reports rather than confirmation. A large number of similar reports can show that a problem is widespread, while a lack of reports does not prove that your connection is at fault.
Platform and account dependencies
Online games often depend on more than their own servers. Check the official network-status page for your console or PC platform, then consider connected services such as account authentication, cloud saves, voice chat, cross-play, or a game launcher. If a platform sign-in service is impaired, the game may display a generic connection error even when the game servers themselves are operating.
Confirm that you are using the intended account and that the account can access online multiplayer. Subscription access, parental controls, privacy settings, suspensions, expired sessions, and two-factor authentication problems can all look like a server error. Do not attempt to bypass an account restriction; use the platform or publisher’s official support process.
Error codes and symptoms
Write down the exact error code, message, time, platform, region, and game mode affected. “Unable to connect to server” is less useful than a complete code copied from the screen. Search the developer’s official support documentation before using community fixes, because error codes can change meaning after a patch or account-system update.
Track whether the problem affects every mode or only one feature. If solo play works but matchmaking does not, the issue may be limited to online services or party formation. If the game disconnects only after several minutes, local packet loss, wireless interference, router behavior, or an unstable connection becomes more plausible.
Local network conditions
Test another online game or service on the same device. If everything fails, inspect the home network. If other games work but one title does not, focus first on that game’s status, patch notes, account services, and known issues.
Record whether you are using Wi-Fi, Ethernet, a mobile hotspot, or a shared network. A temporary hotspot test can help separate a home-router problem from a game or platform outage, although mobile networks may have their own latency or data limits. Check NAT status where the platform provides it. Strict or unavailable NAT can interfere with party joining and peer connections, but it is not proof that the game servers are down.
Cadence and checkpoints
Use a short diagnostic window rather than repeatedly retrying without a plan. Check the official game status, platform status, and error-code documentation at the start. If a maintenance notice gives an end time, allow for the possibility that services return gradually rather than all at once.
For a suspected outage, recheck after a reasonable interval and compare the result with reports from players on the same platform or region. Avoid treating one successful login as a complete recovery; matchmaking, parties, purchases, and progression services may return at different times.
For a suspected local issue, make one change at a time:
- Close the game fully and sign out and back in if the support documentation recommends it.
- Restart the console or PC.
- Restart the router and modem by following the manufacturer’s instructions.
- Prefer a wired connection for testing, if available.
- Pause downloads, streaming, and other high-bandwidth activity.
- Check for a pending game, launcher, or platform update.
- Try the game again and record whether the symptom changed.
DNS changes should be treated as a diagnostic step, not a universal fix. A different DNS resolver may help with name-resolution problems, but it cannot restore an offline game server or repair packet loss. Port forwarding should also be approached carefully: use only official instructions for the specific game or platform, and do not expose unnecessary services on your network.
How to interpret changes
A problem is more likely to be widespread when the official status page shows an incident, multiple players report the same error at the same time, several devices on different networks fail, or the issue begins immediately after scheduled maintenance or a major patch.
A problem is more likely to be local when only one device fails, other players can access the same mode, another network works, or the issue changes when you switch from Wi-Fi to Ethernet. This is a probability check, not a guarantee. Regional routing problems and platform-specific outages can affect some players without appearing as a complete global outage.
Patch notes can provide useful context when a connection problem begins after an update. Look for changes involving account linking, cross-play, authentication, matchmaking, required client versions, or network infrastructure. Our patch notes checklist explains how to separate player-facing changes from fixes that may affect online access.
Cross-play settings deserve a specific check. If you can play alone but cannot join friends on another platform, verify that cross-play, cross-progression, privacy, and account-linking settings match the game’s requirements. See our cross-play and cross-progression guide for a platform-by-platform checklist.
When to revisit
Return to this checklist whenever a new patch, season, platform update, or account-system change affects the game. Live-service launches and season resets are especially useful checkpoints because maintenance windows, login queues, matchmaking changes, and required client updates can overlap. Our live-service season reset checklist can help you prepare before a scheduled transition.
Revisit the article monthly or quarterly if you regularly play a multiplayer game, and update your own notes when the developer changes its status page, support links, error-code terminology, or escalation process. Keep a small record containing the official status URL, your platform, recurring error codes, NAT result, connection type, and the last troubleshooting step that worked. That record is more useful than relying on memory during the next outage.
Before contacting support, gather a screenshot of the error, the time it occurred, your platform and game version, account or region details requested by the support form, and the tests you have already completed. Do not share passwords, authentication codes, or unnecessary personal information.
Practical final check: if the official status page reports an active incident, stop changing local settings and wait for the service update. If official services are operational, test another game, restart your network once, check NAT and account access, and then escalate with the recorded error details. This simple split—server evidence first, local troubleshooting second—usually identifies where the problem belongs without turning a temporary outage into a longer troubleshooting session.