"Can't keep up! Is the server overloaded?" — what it means

Sooner or later every server owner sees this in the console:

Can't keep up! Is the server overloaded? Running 2534ms or 50 ticks behind

It looks alarming, but on its own it is just a measurement. It tells you the server fell behind its schedule for a moment. Whether that matters depends on how often you see it and when.

What the numbers mean

A Minecraft server runs the world in ticks — 20 a second, one every 50 milliseconds. In each tick it moves every mob, grows crops, runs redstone, and processes what every player did. If a tick takes longer than 50 ms, the next one starts late.

The server keeps a running total of how late it is. When it is more than two seconds behind, it prints this warning (and at most once every 15 seconds, so one line can stand for a lot of lost time). 2534ms or 50 ticks behind means the world just missed two and a half seconds of game time.

It does not then try to catch up by running ticks twice as fast. It skips the missed ticks and carries on. That is why players see rubber-banding and mobs teleporting: a stretch of game time simply did not happen.

When to ignore it

• Right after startup. Loading the world, and on a modpack loading every mod, is heavy. One or two warnings in the first minute are normal.
• When a player first joins a big modded world, or teleports far away. The server has to load or generate a lot of chunks at once.
• After the computer sleeps or the clock jumps. On a home PC, if the machine suspends, the server wakes up “hours behind” and prints an enormous number. It means nothing.

A single warning after a few minutes of normal play is also nothing to worry about.

When it is a real problem

If the warning appears every minute or two during normal play, or the numbers keep climbing, the server genuinely cannot do its work in 50 ms. Measure it first:

• tick query (Minecraft 1.20.3 and newer, every loader) — the recent tick times.
• mspt and tps on Paper and Purpur.
• forge tps or neoforge tps on modded servers — per dimension, which tells you whether the Overworld, the Nether or a mod dimension is the slow one.

Average tick time (MSPT) under 50 ms means the server is keeping up overall and the warnings are spikes. Over 50 ms means it is falling behind all the time, and TPS will read below 20.

The usual causes

• Chunk generation. If warnings line up with someone exploring — especially with elytra — the server is generating terrain faster than it can. Pre-generating the world is the fix.
• Entities. Thousands of dropped items, a crowded mob farm, a villager trading hall or an enormous animal pen. This is the most common steady cause on survival servers. See Entity lag: farms, items and mobs.
• Redstone clocks. A clock that pulses forever, whether anyone is near it or not, is pure cost. Turn off contraptions nobody is using.
• Too many loaded chunks. High view or simulation distance with players spread out. See View distance vs simulation distance.
• Not enough memory. When the heap is almost full, Java’s garbage collector runs again and again and every tick slows down. Look for long pauses and OutOfMemoryError lines — How much RAM does a Minecraft server need?.
• A heavy mod or plugin. If the problem started after adding something, remove it and compare.

When it becomes a crash

If one tick takes a full 60 seconds, Minecraft’s watchdog assumes the server has frozen and shuts it down on purpose, with A single server tick took 60.00 seconds (should be max 0.05) in the crash report. The report lists what the server was doing at that moment — usually a specific entity, block entity or mod. Why won’t my Minecraft server start? shows how to read it.

On a shared host

Free and budget servers share physical machines with others, so tick times vary a little more than on dedicated hardware. A few warnings a day on a busy evening are part of that. A warning every minute is not, and is almost always one of the causes above.