When an online game stops connecting, the fastest solution is to establish whether the fault affects everyone or only your setup. This guide provides a repeatable game server status check, explains how to read maintenance notices and error messages, and shows when to troubleshoot your console, PC, or home network instead.
Overview
A failed login, missing friends list, endless matchmaking search, or sudden disconnect does not always mean the game servers are down. The cause could be scheduled maintenance, a wider publisher outage, a problem with PlayStation Network, Xbox services, Nintendo services or PC account infrastructure, a regional routing issue, or a fault with your own connection.
Checking in the right order prevents wasted time. Reinstalling a game, changing DNS settings, opening router ports, or deleting local files will not fix a server-side outage. Conversely, an official status page showing no incident does not prove that your home network is working correctly. Use several types of evidence and compare them with what you are experiencing.
A useful first check is whether the problem affects:
- one game or several online games;
- one account or every account on the device;
- one device or other devices on the same network;
- one region or players in multiple regions; and
- login, matchmaking, voice chat, purchases, or the entire service.
That distinction turns a vague connection error into a more manageable diagnosis.
What to track
Official game and publisher status
Start with the game's official support channels. Look for a server-status dashboard, maintenance notice, service alert, support post, or verified publisher account. The wording matters: a green status indicator may cover the game generally while a separate incident affects login, matchmaking, cloud saves, payments, or a particular platform.
Check the notice's start time, expected end time, affected regions, game modes and platforms. Scheduled maintenance is usually planned, but the published finish time should be treated as an estimate. Services can return gradually, and some features may remain unavailable after the game becomes accessible.
Platform and account services
If the game relies on a console network or a PC launcher, check that platform's official service-status page as well. A platform outage can prevent account authentication, downloads, social features or online play even when the game's own status page reports normal operation.
On console, check the relevant network status page and the console's built-in network test. On PC, check the launcher, account service and any anti-cheat or authentication notices associated with the game. A failed store, friends list or sign-in service can be a useful clue that the issue is broader than one title.
Community reports
Community reports are useful for detecting a developing outage, particularly when an official page has not been updated yet. Search the game's official forum, support community and reputable social channels, then compare reports rather than relying on a single post. Look for a pattern: similar error messages, matching start times and reports from multiple networks or countries.
Third-party outage-reporting sites can show a spike in complaints, but they are not proof of a server failure. A popular game may generate reports whenever a patch, event or login rush begins. Treat community data as an early warning signal and confirm it against official information where possible.
Error codes and symptoms
Record the exact error code and message before restarting repeatedly. A code may identify an authentication failure, timeout, matchmaking problem, version mismatch or corrupted local data. Search the code on the publisher's support site first, because unofficial explanations can be outdated or refer to a different platform.
The symptom is also important. If you can launch the game but cannot join a match, the problem may be matchmaking or session services rather than the whole game. If the game cannot verify your account, focus on platform and publisher sign-in services. If only voice chat fails, the game may otherwise be online.
| What you observe | What to check first | What it may indicate |
|---|---|---|
| Everyone is logged out | Publisher and platform status pages | Authentication outage or maintenance |
| Login works but matchmaking fails | Game incident notices and mode availability | Matchmaking or regional service problem |
| Only one game is affected | That game's support channels and patch notes | Game service, update or account issue |
| Several online games fail | Platform status and home network | Platform outage, router or internet problem |
| Friends list and voice chat disappear | Platform social-service status | Social or account-service interruption |
| Error appears after an update | Version requirements, hotfixes and support posts | Client mismatch or post-patch issue |
Cadence and checkpoints
Use a short sequence rather than making every possible change at once. First, read the exact message and note the time. Second, check the official game status page. Third, check the platform or launcher status. Fourth, compare a community report with at least one additional source. Fifth, test another online game or service on the same device and network.
If an outage or maintenance window is confirmed, stop troubleshooting and wait for the next official update. Check again after the stated window, but allow for a staged recovery. Repeatedly signing in can add noise to an already busy service and rarely speeds up restoration.
If no outage is reported, perform low-risk local checks:
- Close and reopen the game, then install any pending update.
- Restart the console or PC and, if necessary, the router.
- Confirm that other devices can access the internet.
- Use a wired connection or move closer to the wireless access point for a controlled test.
- Check the device's date and time, account login and available storage.
- Run the platform's network test and record its result.
Avoid changing several network settings together. If you alter DNS, firewall rules, port forwarding and router firmware at the same time, it becomes difficult to identify what helped and harder to undo a mistake.
How to interpret changes
Status information can lag behind real player experiences. A publisher may acknowledge an incident before displaying it on a dashboard, or mark a service as operational while a regional cluster is still recovering. Conversely, a spike in community complaints may be caused by a new update, an event launch or a local internet provider issue rather than a global outage.
Look for agreement between signals. An official maintenance notice plus matching reports from multiple regions is strong evidence of a server-side problem. A clean status page, successful tests in another game and failures limited to one device point more strongly towards local troubleshooting. A clean status page combined with reports from players using the same platform or region suggests a partial incident that may not yet be reflected publicly.
Time zones can also cause confusion. Convert a maintenance window to your local UK time and check whether daylight-saving changes apply. If a notice says maintenance ends at a particular time, treat that as the beginning of the possible recovery period rather than a guaranteed moment when every feature will work.
For patch-related problems, compare the installed game version with the required version and read the relevant patch notes. Our guide to reading game patch notes can help separate gameplay changes from technical fixes. If the issue involves cross-progression or account linking, check account settings before assuming that saved data has been lost; see our guide to transferring game saves between consoles and PC.
When to revisit
Return to this checklist whenever you cannot log in, matchmaking stops, a patch introduces connection errors, or a scheduled maintenance period is announced. For regularly played live-service games, bookmark the official status page and support channel rather than relying on search results, which may surface old incidents.
Editors and readers should also revisit the guidance periodically. Status-page addresses, support systems, error-code explanations and maintenance practices can change after a game moves publisher, launches on a new platform or replaces its account infrastructure. A quarterly check is sensible for evergreen links, while major patches and platform-service changes justify an earlier review.
For a practical outage check, follow this final sequence:
- Capture the exact error, affected feature and time it began.
- Check the game's official status and support channels.
- Check the relevant console network or PC launcher status.
- Compare several community reports, noting platform and region.
- Test another online game or device on the same connection.
- Wait if a server incident is confirmed; troubleshoot locally only when the evidence points to your setup.
- Recheck after maintenance or a hotfix, then document what changed if the problem continues.
This approach helps answer the central question—is the game down for everyone, or only for me?—without unnecessary reinstalls or risky network changes.