Home › Guides › How to Fix "Server Not Responding" / Lag on a Minecraft Server
How to Fix "Server Not Responding" / Lag on a Minecraft Server
"Server Not Responding" and general lag almost always trace to one of four things: TPS (the server can't keep up), RAM starvation, CPU per-tick load, or the network. Fixing it starts with knowing which one you have — throwing random settings at the wall wastes an evening. Here's how to diagnose and fix.
First: figure out which kind of lag you have
Two different problems get called 'lag'. Server-side lag is low TPS — the world's clock is running slow, mobs stutter, blocks break with delay. Client/network lag is high ping — the world runs fine but you rubber-band. Type /tps (Paper) or check your host's performance graph to tell them apart.
| What you see | Likely cause | Where to look next |
|---|---|---|
| TPS below 20, everyone lags equally | Server can't keep up | "TPS / CPU" section below |
| "Server Not Responding", then recovers | Tick freeze (GC pause or overload) | "RAM" + "TPS" sections |
| Only you rubber-band, others fine | Your connection | Your internet / Wi-Fi |
| Everyone pings high | Network / server distance | "Network" section below |
If it's RAM (out-of-memory / freezes)
- Symptoms: periodic full-freezes, 'Server Not Responding' that clears after a few seconds, or hard crashes with 'OutOfMemoryError' in the log.
- Fix: allocate enough RAM for your server type and player count — a heavy modpack on 4 GB will do exactly this.
- Don't over-allocate either: an oversized heap makes garbage-collection pauses longer, which itself reads as a freeze. Right-size it.
- MineXEngine tunes the JVM heap and GC to your plan's RAM automatically, which removes the most common misconfiguration.
If it's TPS / CPU (steady slow ticks)
Low TPS with RAM to spare means the server is doing too much work per tick on a single core. These are the highest-impact levers, roughly in order:
| Lever | Effect |
|---|---|
| Lower simulation-distance (to 4–6) | Biggest single win — fewer entities/redstone ticking |
| Lower view-distance (to 6–8) | Fewer loaded chunks per player |
| Cap mob spawn limits | Fewer entities to tick each cycle |
| Limit always-on chunk loaders | Stops idle machines eating CPU 24/7 |
| Pre-generate the world | Removes world-gen stutter as players explore |
| Find laggy chunks (/spark or timings) | Pinpoints the one farm/build causing it |
If it's the network (ping, not TPS)
- If TPS is healthy (20) but everyone pings high, the server itself is fine — it's the path between players and the server.
- Server location matters: closer to your players = lower ping.
- Under a DDoS attack a server can appear to 'stop responding' entirely — enterprise DDoS protection (MineXHost uses OVH's) absorbs that.
- A single player rubber-banding while others are smooth is that player's own connection, not the server.
The modded-server special case
On modpacks, a single mod or one player's mega-farm can tank TPS by itself. Use a profiler (Spark) to find the worst offender rather than guessing. And a crash-looping mod can masquerade as 'not responding' — MineXEngine auto-recovers from those crash loops so the server comes back instead of sitting dead.
MineXHost runs your Minecraft server on MineXEngine — our launcher auto-detects the modpack, picks the right Minecraft loader and Java version, tunes the JVM for your RAM, and auto-recovers from the crashes that normally end a modded server's evening. Pick your RAM, paste the pack, and play.
See hosting plansFrequently asked questions
Why does my Minecraft server say "Server Not Responding"?
The server stopped ticking long enough for your client to time out — usually a garbage-collection pause from RAM issues, a per-tick overload (too many entities/chunks), or a crash-looping mod. Check TPS and the RAM graph to tell which; if it recovers after a few seconds it's most often a GC pause.
How do I fix low TPS on my server?
Lower simulation-distance to 4–6 and view-distance to 6–8, cap mob spawn limits, limit always-on chunk loaders, and pre-generate the world. If TPS stays low with RAM to spare, the bottleneck is CPU per-tick — a faster single-thread CPU is the durable fix.
Is my server lag or my internet?
Check TPS. If TPS is 20 but you rubber-band, it's the network/your connection. If TPS is below 20, the server can't keep up and it's a server-side (CPU or RAM) problem. If only you lag while others are fine, it's your connection.
Will more RAM fix my server lag?
Only if you were memory-starved (out-of-memory errors, long GC freezes). For steady low TPS with free RAM, more memory won't help — the fix is lowering simulation/view distance, capping entities, and faster CPU.