Start your 3-day free trial
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.


When a game friends list shows everyone offline, your friends almost never disconnected at once: the game is failing to load presence because of a service incident, the wrong account, your own status set to Offline, or a stale client session. Compare the platform list with the in-game list, verify the signed-in identities, and rebuild the smallest possible session before touching invitations or network settings.
Key Takeaways
- Record whether the platform list, publisher list, and in-game list disagree.
- Confirm the correct account and friend system before removing or relinking anything.
- Check Online, Invisible, Appear Offline, and privacy visibility on both sides.
- Update and restart one layer at a time so a successful change remains explainable.
- Treat invitation delivery, cross-play support, and matchmaking as separate problems.
The Entertainment troubleshooting overview maps social, account, and connection failures. If people appear online but an invitation never arrives, move to the multiplayer invite checklist. If only a mixed-platform relationship fails, use the cross-play compatibility guide. This article stops at presence and list population.
Start with a two-column record: what the platform sees and what the game sees. Ask one known friend to confirm that they are signed in, visible, and at the game’s main social screen. Do not use an old chat message or a streaming status as proof that the current game session is online.
Record these details:
| Check | Useful evidence | What it isolates |
|---|---|---|
| Platform friend list | Online, away, invisible, or offline | Platform presence service |
| Publisher social list | Friend present, missing, or blocked | Publisher account graph |
| In-game list | Everyone offline or only one group | Game client/session |
| Second device or web list | Same account, different display | One-device cache or UI |
| Known friend’s view | Whether they see you online | Directional visibility |
If one friend alone is wrong, investigate that relationship. If every friend changes at once, prioritize your account, session, client version, and service status. Stop before testing invitations: a list that reports the wrong state has not yet demonstrated an invite-delivery failure.
Presence may depend on several services: platform identity, publisher sign-in, friends, game sessions, and sometimes a separate social backend. A green marketing website does not prove those authenticated services are healthy. Check the official status page for the platform and the game, then note the time and affected component. Epic’s status page, for example, lists Friends, Presence, and Sessions as separate Epic Online Services components, plus a Parties, Friends, and Messaging component for games such as Fortnite.[4]
Compare one control path. If the platform friend list is current while only the game list is stale, a platform-wide outage is less likely. If the platform list, messages, and game list all fail, the issue may sit higher in the identity service.
Avoid repeated reinstalls during an active incident. They erase local context without repairing a remote presence service. Save the status result and continue only if the relevant components are reported normal or if you need evidence for support.
Games do not all read the same friend database. Some use only the console or PC platform list; others use a publisher account; cross-platform games may show both. Display names can also differ from durable account IDs.
Open the official account or social panel for each layer and confirm:
Do not remove every friend or unlink accounts as a first test. Those actions can create a second problem and may affect purchases or progression. If the relationship is missing only in the publisher graph, repair that specific relationship through the official account path.
A launcher can be online under one account while the game loads another publisher profile. On shared consoles, family PCs, and devices with quick account switching, the avatar or display name may look familiar even when the durable identity differs.
Write down the redacted platform ID and publisher ID shown in the current session. Compare them with the IDs your known friend sees. If account linking is part of the design, check the official account page rather than disconnecting and reconnecting experimentally.
Also check whether the game was launched from a test, legacy, or alternate regional account. A friend list associated with another edition can be valid but empty. If the launcher itself reports Offline or cannot authenticate, pause this workflow and follow the launcher-offline diagnosis.
Presence is a setting as well as a service result. Steam distinguishes Online, Away, Invisible, Offline, and Do Not Disturb; Invisible shows you as offline to other players while preserving many community functions, whereas Offline signs out of community features.[2] PlayStation likewise lets a player choose Appear Offline and separately control who can see online status.[3]
Ask both people to check their own status, not just each other’s card. Then compare:
Do not make the profile public as a blanket fix. Use the narrowest audience that still includes the intended friend. A person can intentionally appear offline and still be able to receive some invitations, so presence alone does not prove party eligibility.
Fully quit the game instead of suspending it, then close the official launcher or sign out of the console profile only if you know the credentials and recovery method. Sign back in, open the social panel, and wait for it to populate before entering a match.
Next, power-cycle the device normally. On a handheld or console, a suspended process may retain an old social connection. Epic’s Nintendo Switch guidance for an all-offline friend list includes updating the game and platform, synchronizing the clock, clearing the console cache, power-cycling, and restarting; reinstalling appears later in that platform-specific sequence.[1]
Use only the device maker’s documented cache procedure. Do not delete saves, profiles, or cloud data. Reinstall only after you can restore sign-in details, saved data, optional content, and accessibility settings.
Bring the game, launcher, and device software to supported versions. If one side has a pending hotfix, the social panel may connect to a different session environment even though both clients can reach the internet. Confirm automatic date, time, and time zone because authentication tokens and service sessions can depend on a valid clock.
Only now test the basic network path:
Do not open every port, disable the firewall, or place a device permanently in a DMZ to repair a presence display. NAT and peer reachability matter more after a join attempt begins; they do not explain a friend relationship missing from the account graph.
After one controlled pass, capture evidence instead of repeating changes. Include the game and client build, device, redacted account IDs, affected friend count, platform-list result, publisher-list result, your presence setting, the known friend’s result, service-status time, and every reversible test.
Route a missing platform relationship to platform support. Route a correct platform list but stale publisher list to the publisher. Route a correct social panel but broken invitation to the invitation workflow. This ownership split prevents each team from receiving evidence for a layer it does not control.
Do not post a full friend list, child-account details, email address, IP address, or authentication token in a public forum. A cropped screenshot can preserve the symptom, but redact unrelated identities.
The game may be reading a publisher social graph, holding a stale session, or failing to refresh presence. Verify the publisher account and restart the game before changing the platform relationship.
Your own status mainly changes how others see you, but privacy and presence settings can also alter what social features load. Check both sides and use the intended audience rather than making the profile fully public.
Check your own status first. On Steam, Invisible shows you as offline to other players, and Offline signs you out of community features entirely.[2] PlayStation notes that you might still appear online inside a game even when your platform status is Appear Offline, so game and platform presence can disagree.[3] If your status is Online and the audience includes that friend, continue with the account checks in section 4.
No. First identify whether the platform relationship, publisher relationship, or client display is wrong. Remove and re-add only one proven-bad relationship through the official path.
No. Presence describes who appears available; an invite has a sender, delivery path, party state, and join step. Move to invite troubleshooting only after the lists display correctly.
NAT can affect peer connections and joins, but it is not the first explanation for an account graph or presence feed that fails to populate. Check identity, visibility, sessions, and service status first.
That result points toward this device’s client version, suspended session, local cache, or clock. Protect saves and settings, then use documented cache or reinstall steps only if ordinary restart and update fail.
No. Reinstalling cannot change a remote block, wrong account, privacy rule, or service outage. It is a late device-specific test, not a universal reset.
Send redacted account IDs, device and build, exact affected scope, list results at each identity layer, status-page time, and tests already performed. Avoid exposing unrelated friends or security information.
Sources:
Sources checked 4 October 2026.
Related articles:
Sign up to experience all premium features at no cost.
*Available only to new users. Each user is limited to one trial.