Run the test above for at least 60 seconds. Here is what each
number means for this game specifically.
Packet loss (the disconnect metric)
Palworld responds to a broken connection by removing you from the session, usually without much explanation. Sustained loss on this chart is the most common reason, and unlike a server problem it will show up here consistently rather than only at the moment you are dropped.
Jitter (combat that lands late)
Capture attempts, pal commands and your own shots are all confirmed by the host. Uneven delivery produces the pattern where a sphere connects visually but the capture resolves a beat later, or where a pal ignores an order and then obeys it twice. That is delivery timing, not the game deciding to ignore you.
Ping (to a specific machine, always)
There is no region to select. In co-op you are connecting to the host player, and on a dedicated server you are connecting to wherever that box physically is. A community server hosted on another continent will read high here and there is nothing local to do about it except choose a nearer one.
What you see in game, and which number on this page explains it.
Palworld's two ways of playing together are not two front ends onto the same system. Invite-code co-op takes a world that lives on one player's machine and lets a small group into it, with that machine doing all the simulation while also running the game for its owner. A dedicated server takes the same world and puts it on a machine whose only job is to be the authority, which is why it can hold far more players.
That distinction decides where your problems come from. In co-op, the host is a home connection with a home router and a household sharing the line, and everything that happens to it happens to the group. On a dedicated server, the host connection is out of the picture and what remains is your own path to a specific machine - which is exactly what this page measures.
The base building adds a second, less obvious load. Pals assigned to work continue doing so as the world runs, and the machine hosting the world is the one calculating all of it. A large base with many pals is real, ongoing processing that has nothing to do with the network, and it produces a distinctive symptom: workers freezing or acting stupidly while players still move and shoot normally.
Keeping those two apart is worth the effort because they need opposite responses. Pals stalling while the chart here is clean means the host needs a better machine or a smaller base, and no amount of network tuning will touch it. Players warping and disconnecting while the chart shows loss means the opposite, and the fix is on the connection rather than in the game.
If the chart above shows packet loss or high jitter, work through
these in order.
Why do I keep getting disconnected from a Palworld server?
Sustained packet loss is the usual cause you can act on. Run this test for a few minutes: consistent red here means your line, while a clean chart during repeated drops points at the host or the server instead.
Is a dedicated server better than co-op?
For anything beyond a small group, yes. It supports far more players, it does not require the world's owner to be online, and it stops one household's connection from being the whole group's bottleneck. The trade is that you have to run and configure it yourself.
Why do my pals stop working at the base?
Base pals are simulated by whichever machine hosts the world. A large base is genuine processing load, and pals stalling while players still move normally is a sign of the host being busy rather than of a network problem.
Can I choose a Palworld server region?
Not in the sense that a game with official servers offers. You connect to a specific machine - a friend's, or a community server at whatever address it has - so the latency you get is a property of that choice.