PEAK sold more than 10 million copies on PC within two months of its June 2025 launch, according to its Wikipedia entry, and on October 22 it lands on PlayStation 5, Xbox Series X|S and Switch 2 with crossplay. Landfall’s own PEAK FAQ confirms console players will join the existing Steam crowd, at $9.99 digital. That means a lot of new mixed lobbies: a PC player in Toronto, a cousin on a Switch 2 in Perth, a friend on Xbox over hotel Wi-Fi.
PEAK lag in those lobbies has a specific shape, because of how the game connects you. The questions below cover what that shape is, which parts you can fix, and which parts no setting or service will touch.
How does PEAK actually connect four players?
Not directly to each other. Landfall’s FAQ says it plainly: “We use Photon for server relays.” Photon is a commercial networking cloud common in Unity games, and in a relay setup every player sends their packets to a Photon server, which forwards them to everyone else in the room.
Photon’s region documentation lists where those servers live: Amsterdam (eu), Washington D.C. (us), San José (usw), Dallas (ussc), Montreal (cae), São Paulo (sa), Singapore (asia), Tokyo (jp), Seoul (kr), Sydney (au), Chennai (in), Johannesburg (za) and a few others. Each region “is completely separate from the others,” with its own master and game servers. A room exists in one region, so everyone in your climb is connected to the same box in the same city.
That single fact explains most PEAK lag complaints.
Why does one friend lag while the rest of the group is fine?
Because each player’s ping is their own path to that shared Photon server, not a path to the host. If your room sits in Washington D.C., a player in Virginia might see 15 ms while a player in Sydney sees well over 150 ms.
That Sydney number has a hard floor. Light in fiber covers roughly 200 km per millisecond, which works out to about 5 microseconds per kilometer one way, per M2 Optics’ fiber latency math. Sydney to Washington is around 15,700 km in a straight line, so the round trip cannot drop below roughly 157 ms even on a perfect cable, and real routes are never straight.
Players in a Steam thread on cross-continent co-op describe exactly this: a group spread across North America, South America and Australia reported “a very minimal interact delay (as expected).” PEAK is a co-op climbing game, not a twitch shooter, so 150 ms is playable. Grabbing a friend’s hand at the edge of a cliff is where you feel it.
Which PEAK lag problems are on my side?
More than people expect, and they are free to fix. Landfall’s FAQ lists several that matter specifically for Photon:
- Wi-Fi 7 Multi-Link Operation. Landfall says some players fixed disconnects by disabling MLO on their router. If you bought a Wi-Fi 7 router this year and PEAK keeps dropping you, try this first.
- cFosSpeed. The FAQ says to uninstall it because it can interfere with Photon. It ships bundled with some motherboard and laptop network utilities, so check even if you never installed it yourself.
- Firewall and antivirus. Add PEAK as an exception. Photon Cloud uses UDP ports 5058, 5055 and 5056 by default (27000 to 27002 as alternates), per Photon’s port reference. Because every player connects outward to the relay, you generally don’t need the port forwarding that peer-to-peer games demand.
- Wireless on console. A Switch 2 docked on Wi-Fi in a back bedroom adds jitter that no server choice fixes. The case for Ethernet over Wi-Fi is stronger than any setting in the game.
One pattern from a June 2025 Steam thread on Photon disconnects is worth knowing: a player on a shared LAN kept dropping while a remote friend stayed connected, and they traced it to several clients sharing one public IP. In network operations at a large telecom I saw that failure class constantly; when several devices hide behind one address, anything that keys sessions on the address alone gets confused. If two of your party are in the same house and only those two drop, that is your first suspect.
Your room is in another region and your route there is messy?
Once the local fixes are done, the remaining delay is your path to the Photon server. If your ISP sends that traffic the long way around, a GPN can hand it a more direct path. It can’t shorten the ocean.
Can I choose which Photon region my lobby uses?
Not from an official menu that Landfall documents. Photon’s default behavior is to ping the regions and pick the lowest, and Photon’s own docs warn that this “Best Region” result “may be ‘random’ due to little variations or exact same ping calculations.” Two players in the same house can, in principle, land on different regions that way.
On PC, a third-party guide at ShowGamer documents a Steam launch option, -photonRegion EU or -photonRegion US, set under PEAK, Properties, General, Launch Options. Treat it as unofficial. It is useful for one case: a group where the host keeps landing in a region that is far from everyone else. It does not exist on console, and it changes nothing about your route once you are in that region.
What can rerouting fix in PEAK, and what can’t it?
Here is the honest split.
| Symptom | Where it lives | Does a reroute help? |
|---|---|---|
| Your ping to the room is 60 ms higher than a friend’s in the same city | Your ISP’s path to the Photon region | Yes, often. This is the real case |
| Delay that climbs when you join an overseas friend’s room | Mostly distance, partly route | Partly. The route detour can shrink; the distance floor can’t |
| Loss that shows up on the final hop of a traceroute | Congested transit near the Photon server | Yes, if it persists to the destination |
| One friend on bad Wi-Fi rubberbands for everyone who touches them | Their connection | No. Your route is not their route |
| Two players in one house drop together | Shared public IP or local router | No. Fix it locally |
| Everyone drops on a Tuesday | Steam’s weekly maintenance, which Landfall’s FAQ calls out | No |
To find out which row you’re in, run a traceroute to the relay while you play and look for loss that carries all the way to the last line. Our walkthrough on reading WinMTR shows how to tell real path loss from routers that simply ignore ping requests.
What changes on October 22 for console players?
Three things matter for the network side.
First, the room region gets decided by whoever hosts. Mixed groups are more likely to span continents now that a console friend overseas can join a PC lobby, so the distance floor from earlier will show up in more parties.
Second, console players can’t install a PC client to reroute traffic. The only way to change a console’s path is at the router. Some TP-Link Archer GE models run WTFast in firmware and cover every device behind them; our post on WTFast on TP-Link routers lists which ones.
Third, there is no cross-save, per Landfall. Your PC unlocks do not follow you to a PS5, which has nothing to do with lag but will be the top complaint on launch day regardless.
Testing it costs one climb
Run a session with your normal connection, note your ping, then run the same lobby through a reroute. If the number doesn’t move, your lag was distance or a teammate’s Wi-Fi, and you’ve lost nothing.
So who should host?
The player closest to the middle of the group, geographically. If three of you are in North America and one is in Australia, let a North American host so three people get low ping and one gets the unavoidable long haul, instead of four people paying the trans-Pacific cost. If the group is split evenly, rotate hosts between climbs and see whose room feels best; with a relay in the middle, the best host is often not the person with the fastest internet plan but the person whose region sits closest to everyone else.