Why Minecraft Keeps Disconnecting You From Servers

Repeated mid-game drops — you're playing along, then the screen flips to Connection Lost with Timed out underneath — almost always come from a connection that can't keep its keep-alive packets flowing, not from a broken install or a flagged account. While you're in a world, your client and the server quietly trade small keep-alive packets to confirm each other is still there; when enough of those go missing, one side gives up and drops the link. So a server you can join but can't stay on is usually a stability problem on one end of the wire, and that narrows the search a lot.

The difference between this and a failure to connect at all matters, because they send you to different checks. If you never get in — a red error on the multiplayer list before the world ever loads — that's the connect stage, and the connection timed out walkthrough covers it. Getting kicked after you've loaded in is what this is about. Work it cheapest-first: read the exact kick line, steady your own connection, and only then look at the host. And since drops very often arrive on the back of a lag spike, keep the lag-spike guide open alongside this one.

What a mid-session disconnect actually is

Once you're in a world, the connection has to stay open continuously, and the keep-alive exchange is how both ends know it's still alive. The server sends a keep-alive packet on a regular interval and expects your client to echo it back within a window; your client does the same in reverse. Miss too many in a row — because packets are getting lost, or because one side froze long enough to stop answering — and the connection is torn down with a timeout. That's the Timed out you see under Connection Lost.

This is why a single dropped frame of network never disconnects you, but a stretch of packet loss does. A momentary hiccup gets absorbed; a connection that's losing packets steadily, or stalling for several seconds at a time, eventually starves the keep-alive and you're out. None of this touches your single-player worlds or your saved server list — a drop just ends the session and changes nothing else.

Read the disconnect line before you change anything

The text on the disconnect screen tells you which way to look, so read it before touching any setting.

• "Timed out" / "Connection Lost" — the keep-alive exchange stopped landing. This is the connection-stability case, and it points first at your own network and second at an overloaded server.
• "Internal Exception: io.netty.channel.unix.Errors$NativeIoException: ... Connection reset by peer" — the connection was open and then the far side abruptly cut it, often a server crash, restart, or a proxy in front dropping you. That message and its siblings are broken down in what io.netty.channel errors mean.
• "Connection throttled! Please wait before reconnecting." — you reconnected faster than the server's throttle window allows. This shows up most when something is bouncing you and you're hammering the Join button to get back in.
• "Outdated client!" or "Outdated server!" — not a stability drop at all but a version gap, the usual culprit right after one side updates. A newer client can't join an older server, so this is its own fix.

Player-side: steady your own connection

If only you are dropping while others stay on, the problem is the path between your machine and the server, and these are the cheap wins.

A wired connection is the single biggest improvement. Wi-Fi loses packets in bursts — a microwave, a neighbor's channel, distance from the router — and those bursts are exactly what starves a keep-alive. Plugging in over Ethernet, or at least moving closer to the router, removes the most common cause outright.

Next, free up the line. A large download, a cloud backup syncing, a game update in the background, or someone else streaming on the same connection can saturate your upload and delay the keep-alive reply just long enough to get you kicked. Pause that traffic and see if the drops stop. A VPN cuts both ways here too — it can route around a flaky path, but a congested or distant VPN endpoint adds its own packet loss, so test with it off.

When the cheap checks don't settle it, power-cycle the router and modem — unplug, wait a minute, reconnect — to clear a stale route, then try the same server on a phone hotspot. If you stay connected on the hotspot but drop on home Wi-Fi, the fault is your router or ISP, not the server, and that split saves you from blaming the host.

Owner-side: throttles, idle timeouts, and an overloaded box

If the server is dropping people, the levers are on the host's side, and a player can't reach them from the client.

The most common owner-side cause of mass timeouts is the server itself running out of headroom. When the main thread stalls — too many entities, a heavy redstone build, a plugin chewing the tick — the server can't send its keep-alive packets on schedule, and once it falls far enough behind, everyone times out at roughly the same moment. That's a TPS problem showing up as a disconnect, and it's the same root cause the lag-spike guide digs into. A proxy in front of the network, like Velocity or BungeeCord, restarting or losing its backend will drop the whole server at once in the same way.

The "Connection throttled!" message is its own owner setting. The settings.connection-throttle value in bukkit.yml is the minimum gap, in milliseconds, the server allows between connections from the same address; reconnect inside that window and you get refused with that exact line. It's there to blunt connection spam, and it's why mashing Join after a drop makes things worse rather than better — each rapid retry resets the clock.

When it's everyone vs. just you

The fastest way to settle who owns the problem is to find out whether anyone else is dropping. If chat lights up with everyone disconnecting together, or the server vanishes from the live rankings for a stretch, it's the host — wait it out, because there's nothing on your end to change. If you're the only one dropping while the server shows healthy on the full list, the path to your machine is the thing to fix, and the player-side checks above are where to spend your time. Testing against a clearly online, populated server makes that signal trustworthy; a half-dead server will mislead you.

FAQ

Why do I only get dropped during big fights or near a lot of redstone?

Those moments send a burst of packets — entity positions, block updates, particle and sound events — right when the server is also working hardest. On a marginal connection or an overloaded server, that burst is what tips keep-alive over the edge: your reply or the server's gets delayed past the window and the link drops. Steady connections ride through it; the fact that it only happens during the busy moments is a strong hint the margin is thin, either on your upload or on the server's tick rate.

I get kicked after standing still for a few minutes — is the server doing that on purpose?

Probably, and it's a single setting. player-idle-timeout in the server's server.properties kicks anyone who's been idle for that many minutes; it's measured in minutes, defaults to 0 (disabled), and only the owner can change it. If you reliably drop after the same quiet stretch and an active player never does, that's the cause rather than your network. There's nothing to fix client-side beyond moving occasionally, or asking the owner what the value is set to.

Can a resource pack or a mod disconnect me after I'm already in?

Yes. A server-sent resource pack that stalls or fails to download partway can drop you during the load, and retrying once the download completes often just works. On modded setups, a mod that desyncs or sends data the other side rejects can sever an established connection mid-session — worth checking that your mod and loader versions match what the server expects, since a mismatch there behaves like instability rather than a clean "Outdated" message.

None of this helped — will reinstalling Minecraft stop the disconnects?

Almost never. A mid-session drop is about the network path staying open between you and one specific server, and a reinstall changes none of that — not a lossy Wi-Fi link, not a saturated upload, not an overloaded host. Your game clearly works, since you reached the world before it dropped you. Work the connection checks instead, run the hotspot test to prove whether it's local, and if the whole server is dropping everyone, the answer is to wait or pick a steadier community from the same category.