Direct answer

High ping reflects network round-trip delay. A server can maintain 20 TPS while a remote player still has a poor connection, and low TPS can make interactions sluggish even with a low ping.

How to check it

  1. Check whether every player is affected or only one ISP, country, Wi-Fi network or proxy route.
  2. On a supported spark installation, compare /spark ping, /spark tps and /spark health show --network during the complaint.
  3. Have an affected player test wired vs Wi-Fi and record packet loss and route changes. ICMP ping or traceroute is supporting evidence, not a perfect measure of Minecraft protocol behavior.
  4. If the server tick time is high, collect a spark profile; otherwise look at the network path, upstream congestion or hosting location.
/spark ping
/spark tps
/spark health show --network

What to change

For a network bottleneck, prioritize connection quality, routing or a closer host. For server-side tick pressure, investigate the workload shown by a profiler instead. Do not lower simulation distance merely to reduce a single player’s ping.

Software and version notes

Proxy setups add another network hop; test the player-to-proxy and proxy-to-backend paths separately. spark availability and command aliases differ by platform.

Verify the result

Recheck ping, packet loss and player-visible symptoms at a similar time of day. A better MSPT with unchanged packet loss is not evidence that the network issue was fixed.

Related topic: Network Lag vs Server Tick Lag. Compare the two guides when choosing the right diagnostic or configuration step.

References