"Can't keep up! / Skipping ticks" — what does it mean?

Seeing "Can't keep up! Is the server overloaded? Running Xms behind, skipping Y ticks" in your console is a common worry, but the message itself is just a symptom — it tells you the server is overloaded, not why.

What the message means

Minecraft aims to process one tick every 50 milliseconds (20 ticks per second). When a tick takes longer than that, the server falls behind and "skips" ahead to catch up. In other words, your TPS has dropped — something is giving the server more work than it can finish in time.

How to find and fix the cause

Because it's a symptom, the fix is finding what's overloading the server:

1. Run a spark report to see what's eating CPU — usually too many entities or chunks, a heavy plugin/mod, or insufficient CPU.
2. Address the biggest consumer using the standard performance fixes: pre-generate the world, lower view-distance, trim heavy content, or upgrade to a Ryzen tier if you're genuinely CPU-bound.

Tip: Don't chase the message itself — chase what the spark report shows. Once TPS recovers, the "Can't keep up" lines stop on their own.

Frequently asked questions

Is "Can't keep up" dangerous? Not in itself — it's a warning that the server lagged for a moment. Frequent occurrences mean sustained low TPS worth diagnosing.

Why does it happen right after boot? A brief burst at startup (while chunks and content load) can be normal. Persistent messages during play indicate a real overload — profile it with spark.