Fix Minecraft "Can't Keep Up! Server Overloaded"

That message means your server can't finish a game tick in the 50ms it has — its TPS (ticks per second) has dropped below 20, and everyone feels it as lag. Here's what drags TPS down and how to bring it back to 20.

Quick answer

"Can't keep up! Is the server overloaded?" means the server could not finish a game tick in 50 ms, so TPS dropped below 20. Make each tick cheaper: switch to Paper, lower simulation and view distance, pre-generate the world and cut entity and redstone load. Low TPS is a CPU problem — a faster per-core CPU helps far more than extra RAM.

What "can't keep up" actually means

Minecraft aims for 20 TPS (a tick every 50ms). When a tick takes longer, the server falls behind and prints this warning. The fix is to make each tick cheaper — less work per tick, or a faster CPU to do it.

The four causes at a glance

Low TPS almost always traces to one of these four. Start at the top — the first two are the biggest, cheapest wins:

Cause 1: vanilla server software

The single biggest win: switch from vanilla to an optimized fork like Paper (or Purpur). They do the same job far more efficiently and add tuning options vanilla doesn't have.

Cause 2: view/simulation distance too high

Every extra chunk is more entities and blocks to tick. Lowering these in server.properties is often an instant fix:

view-distance=8
simulation-distance=6

Cause 3: too many entities (mob/item lag)

Mob farms, dropped items and overloaded chunks eat tick time. Use a profiler to find the hotspot, then cap entities. Install spark and run:

/spark profiler --timeout 60
# or check tick health
/spark tps  /spark health

Cause 4: not enough RAM / bad GC

Too little RAM causes garbage-collection pauses that look like lag spikes. Allocate sensibly and use Aikar's flags:

java -Xms6G -Xmx6G -XX:+UseG1GC -XX:+ParallelRefProcEnabled \
  -XX:MaxGCPauseMillis=200 -jar paper.jar nogui

The clean checklist

1. Switch to Paper/Purpur.
2. Lower view-distance and simulation-distance.
3. Profile with spark and fix the top entity/plugin.
4. Set -Xms = -Xmx with Aikar's flags.
5. Pre-generate the world; remember a fast single-core CPU matters most.

Low TPS is a CPU-per-tick problem. Paper + lower distances + a fast CPU fixes almost every "can't keep up".

Cause 5: plugins or mods doing expensive work every tick

A single poorly-written plugin or mod running heavy logic (pathfinding, database calls, scanning every entity) on every tick can single-handedly cause "Can't keep up! Is the server overloaded?" even with Paper and a fast CPU. This is exactly what the spark profiler above is built to catch — look for one plugin dominating the profile and update, reconfigure or remove it.

How to prevent "Can't keep up" warnings for good

• Pre-generate the world with Chunky so exploration doesn't generate terrain on-demand mid-tick.
• Cap or clear excess item/entity buildup with a plugin like ClearLag, tuned conservatively.
• Re-profile after every plugin or mod update — a previously fine plugin can regress.
• Keep simulation-distance and view-distance as low as your playerbase will accept.
• Schedule backups and heavy tasks (world resets, compaction) for low-population hours.

Related Minecraft performance guides

If the server crashes outright instead of just lagging, see how to read a Minecraft server crash report. For memory-specific issues, read Minecraft out of memory / Java heap space and how to allocate more RAM to a Minecraft server. For more tuning ideas, see best Minecraft server settings to reduce lag.

Minecraft is a trademark of Mojang Synergies AB / Microsoft. ESAGAMES is an independent hosting provider, not affiliated with or endorsed by Mojang or Microsoft.