How to Diagnose and Fix Game Server Lag

Lag on a game server is rarely one single thing. Even on good hardware, a setup can slow down, and the cause is often something you changed. The fastest fix is to work through the common causes in order, changing one thing at a time so you know what made the difference.

Almost every case falls into one of five buckets:

1. A bad mod, plugin or script
2. A bad or corrupted save
3. A problem on the player's side
4. A server that has outgrown its plan
5. A poor network route or the wrong location

1. Rule out mods, plugins and scripts

It only takes one badly written mod to drag a whole server down. Many mods and plugins run fine in a local single-player game but were never designed to run on a dedicated server.

How to test

• Add mods one at a time, and play for a while after each one. If performance drops, remove the one you just added.
• To confirm mods are the problem, take a full backup, then remove every mod and see whether the lag stops.
• If the lag returns as you re-add mods, you have found your culprit. Check that mod's page for known issues or updates, or look for a lighter alternative.

If your world requires a mod that only caused trouble later on, the save itself is more likely the problem. That is the next step.

2. Check for a bad save

A server world is a living thing: it changes constantly. If lag appears out of nowhere and won't go away, something in the world may have changed, such as a huge new build, a glitched area of the map, or an object that has broken.

How to test

• Generate a fresh world and try it both with and without your mods. If a fresh world runs well and your old one doesn't, the save is the issue.
• Restore a backup from before the lag started. This often fixes it, unless the thing that caused the problem gets used or built again.
• If your game has a map-cleanup or decay feature, use it. Clearing abandoned structures and items keeps a world lean.

Regular, automatic backups are the best protection here. They let you roll back to a healthy point instead of guessing.

Test on the server, not on your own PC. A save or mod that seems fine in a local game can behave very differently on a dedicated server.

3. Rule out problems on your own end

Not all lag comes from the server. Before blaming your host, check the things you control:

• Close background apps, downloads, streams and cloud-sync tools that use your connection.
• Restart your PC and your router.
• Install pending game, driver and system updates.
• Turn your graphics settings right down. If the stutter disappears, it was your machine, not the server.
• If you can, try a different device or network, or ask another player whether they see the same lag at the same time.

The key clue: if only you lag and everyone else is fine, it is almost certainly on your side. If everyone lags at once, look at the server.

4. Check whether you've outgrown your hardware

Game developers publish minimum and recommended specs for their servers, but those figures are for the vanilla game with no extras. Mods, heavy settings, large maps and bigger player counts all raise the real requirement.

How to test

Run the server with a fresh map and no mods. If it runs smoothly, your normal setup is probably pushing the limits of your plan. In that case:

• Upgrade to a plan with a faster CPU or more RAM. Game servers are usually limited by single-core CPU speed, so a higher clock speed often helps more than extra cores.
• Or trim the load: fewer mods, lower entity or spawn limits, smaller world size or player cap.

One caution: if a bad mod or setting is the real cause, upgrading won't fix it. Rule out steps 1 and 2 first so you don't pay for hardware you don't need.

Sometimes the problem is the host. If a server slows down at the same time for every player and nothing on your side has changed, ask your provider whether other customers on the same machine are seeing it too. A good host will investigate this.

5. Test your route and server location

Distance matters. The closer the server is to you and your players, the lower your ping. Even with the right region, the route between you and the server can be poor in ways no host can predict.

If your players are spread around the world, no single location will suit everyone. Pick the location closest to the majority of your players.

Run a traceroute

A traceroute shows the path your connection takes to the server and how long each step takes. It is the standard way to see where delay is being added. The short version is below; the full walkthrough is in How to Run a Traceroute and Ping Test for a Game Server.

Close anything using your internet connection first, so the result is accurate. You will need the server's IP address or hostname without the port. For example, if your server is 203.0.113.42:28045, use 203.0.113.42.

On Windows

1. Press the Windows key, type cmd and press Enter to open Command Prompt.
2. Type the following and press Enter, replacing the address with your own:

tracert 203.0.113.42

1. Wait up to a minute or two for it to finish.
2. To save the result so you can share it, use:

tracert 203.0.113.42 > C:\trace1.txt

On Mac or Linux

Open Terminal and run:

traceroute 203.0.113.42

A quick ping check

For a simple latency figure, ping the server for a few seconds:

ping 203.0.113.42

Look at the average time in milliseconds. As a rough guide, under 50 ms feels great in most games, 50 to 100 ms is fine for most, and well over 100 ms will be noticeable in fast-paced games.

How to read the results

Each line is one "hop", a router or server between you and the destination.

Two things look worrying but usually aren't:

• An asterisk (*) instead of a time means that hop didn't answer. Many routers deliberately ignore these requests, so this doesn't automatically mean packet loss.
• A missing hostname (just an IP address) is common and doesn't mean anything is wrong.

What to look for instead: a large, sudden jump in time that stays high for every hop after it. That points to where delay is being added. If the jump happens well before the server, the problem is somewhere on the route, not on the server itself.

If you contact your host's support, send the complete traceroute output, every line, so they can see the whole path.

Quick checklist

• Removed all mods and retested
• Tested with a fresh world
• Restored a backup from before the lag started
• Confirmed the lag isn't on your own PC or network
• Compared performance on a vanilla setup against your usual one
• Ran a traceroute and checked the ping to your server
• Considered whether the server location suits most of your players

If you have worked through all of these and lag remains, contact your host's support with your traceroute results, a description of when the lag started, and the list of mods you run.