Most popular Minecraft server versions, measured live

Most Minecraft servers run the newest release or the one just before it, and a large share of them answer through a Velocity proxy. Right now 35 of the 94 servers that are playable on our list advertise 26.3, released 34 days ago, and 26 more top out at the release before it.

Data from our own pinger, all times UTC. The live figures are recalculated from our latest pings, and sections marked "first look" are dated analyses of the 26.3 release that do not change.

Headline

Right now 35 of the 94 playable servers on our list name 26.3 as the newest version they accept, 34 days after it came out.

35Playable servers advertising the newest Java release right now

Measured 19 Oct 2026, 22:55 UTCHow we measure

Compare the share of players with the share of servers: big servers tend to be current, so the newest version usually holds more of the players than of the servers.

Newest version supported

1. 26.33535%
2. 26.22626%
3. 26.177%
4. 1.21.x1414%
5. Older66%
6. No version number1212%

35 of 100 playable servers advertise 26.3, the newest Java release.

Measured 19 Oct 2026, 22:55 UTCHow we measure

"Newest version" is the top of what a server says it accepts: 26.2 for Paper 26.2, 26.3 for Velocity 1.7.2-26.3. The chart counts every playable server, including the few that answer only on their Bedrock port, so its total can be a little higher than the Java count in the table above.

• Big servers are current. Networks have staff for updates, and their proxy can take a new client before the game servers behind it move.
• 1.21.11 does not move. 20 playable servers top out at 1.21.11 or older right now. 1.21.11 was the last release with the old numbering and the last Paper version on Java 21: PaperMC's requirements table lists Java 25 for 26.1 and later. Leaving 1.21.11 means a new Java runtime and a check of every plugin at once.
• Some servers do not say. Some send a server name, a made-up counter or no Java answer at all, for example because they only answer on their Bedrock port.

The protocol number shows how wide the door is

Every ping answer also carries a protocol number, which your game compares with its own: when they differ, the server row shows the version text in red. Our pinger introduces itself as a 1.21.1 client, so a server that answers with the 1.21.1 number says 1.21.1 players can join.

First look, 00:54 UTC on 18 October 2026: 18 of the 26 running servers that named Paper or a Paper fork answered with the 1.21.1 number. 11 of those ran 26.1.2 or newer, so they take a 1.21.1 player only by translating between versions, the job of the ViaBackwards plugin. 7 answered with their own number, and 1 with -1, a trick some plugins use to show custom text. Every proxy answered with our number, as Velocity and BungeeCord do for any version in their range. So most servers accept more versions than their text admits, and your multiplayer menu is the honest test. How to join a Minecraft server explains the row and how to switch versions.

On the Bedrock side

Bedrock numbers the same content differently from Java. On a Geyser server the Bedrock version in the ping is the newest Bedrock version its Geyser build supports, so it shows how recently the owner updated Geyser. Live: 53 of 59 servers answering on Bedrock report a version from the same drop as Java 26.3.

Bedrock has less room to lag. Phones and consoles usually update the game on their own and most Bedrock players cannot choose an older version, so a Geyser server that falls behind turns new clients away until the owner updates Geyser. The player side is in how to join a server on Bedrock.

How fast servers update to the latest drop

0%50%100%

Peak 36.6%, Thu 15 Oct

21 Sep28 Sep5 Oct12 Oct

33 days after 26.3 came out on 15 September 2026, 37 of 101 playable servers advertised it.

Measured 19 Oct 2026, 22:55 UTCHow we measure

There is no rush after a release: servers move a few at a time, and the curve above climbs slowly for weeks. The daily count mixes updates with servers that come and go, so for 26.3 we also followed the servers that were running both before and after the release.

First look, 18 October 2026. Java 26.3 came out on 15 September 2026, and the first proxy on our list advertised it that evening. Of the 77 servers that were running on both 14 September and 17 October:

• 43 were on 26.2 the day before release. 23 of them (53%) had moved to 26.3 a month later.
• Proxies moved first. 18 of the 33 Velocity-family proxies on 26.2 moved. On 17 October, 24 of all 46 Velocity-family proxies advertised 26.3, against 5 of the 26 Paper-family backends, and the first Paper-family backend got there five days after release.
• 1.21.11 stayed put. 8 of the 10 servers on 1.21.11 in September still were in October, among them all 6 Paper-family backends.

Proxies lead because a proxy is one jar with no world in it. Updating it lets players on the new version in at once, and a translation plugin on the proxy or the backends bridges them to game servers still on the older release until their plugins are ready.

Proxies and backend software

1. Velocity family4742%
2. Paper2018%
3. Custom text1816%
4. Version number only98%
5. No version text87.1%
6. Purpur43.6%
7. Leaf32.7%
8. BungeeCord family21.8%
9. Folia10.9%

Version text of the 112 servers that answered the latest ping. 49 answer through a proxy, so their text describes the proxy and not the game server behind it.

Measured 19 Oct 2026, 22:55 UTCHow we measure

• Players sit behind proxies. Most of the players on the list are on servers that answer as a proxy, 49 playable servers right now. Backend names show up on small single servers, and of a network you only see the front door.
• Spigot has all but disappeared. 0 playable servers name Spigot or CraftBukkit right now, against 28 naming Paper or a Paper fork.
• Ranges describe the proxy. 46 of the 53 advertised ranges start at 1.7.2, Velocity's own minimum. That is not a promise that a 1.7 client gets anywhere, because what old clients can do depends on what runs behind the proxy.

What each project is good for, and how to switch, is in Paper, Purpur, Folia or Velocity: what servers really run.

Servers that stay on old versions on purpose

Old does not always mean late. Many servers on versions older than 1.21.11 are modded. Porting a large modpack takes far longer than updating a plugin server, so modding settles on a version for years: 1.12.2 and 1.20.1 for many Forge packs, 1.21.1 for many NeoForge packs. The pack's launcher installs the right version for you, and the modded server list shows which packs run now. Others are plugin servers, such as kit PvP and minigames servers, that stay where their plugins work.

"1.8 PvP" is still a selling point, but in our first look on 18 October 2026 no server advertised 1.8 as its newest version, and only two of the 51 advertised ranges started at exactly 1.8. PvP servers that want the old combat run a current version, let old clients in through the proxy and translation plugins, and restore the old combat rules with plugins. 1.8 PvP against modern combat explains the split, and the PvP server list shows who runs what.

When to update, and which version to play

If you play, use the newest release. Servers advertising it hold 65% of the players right now, and many others accept it through translation. When a row turns red, make a launcher installation with the version the server names. The Java server list can be filtered by version.

If you run a server:

1. Update the proxy first, once your proxy plugins load on the new build. New clients can connect right away.
2. Update backends when your plugins are ready. Two weeks after 26.3 came out, more than three quarters of the servers on our list had not advertised it yet. Players forgive a slow update far more readily than a broken economy.
3. Treat 1.21.11 to 26.x as a project: Java 25, a plugin audit and a full backup, tested on a copy of the world first.
4. Add a translation plugin while you stay behind. The launcher defaults to the latest release, so a server that only accepts an older release shows a red row to every player who kept that default. ViaVersion lets newer clients join an older server.

How we measured, and what pings cannot tell us

• Pings. Every public listing gets a Java status ping, and crossplay listings also a Bedrock ping, every minute. Before 17 October 2026 the interval was 70 to 90 seconds.
• Which servers count. Live figures count servers whose latest ping was playable: an answer with more than zero player slots and no placeholder text. The first looks counted a server on a day when it was playable for at least an hour, because a free host's front proxy can answer as playable for a few minutes while the server behind it sleeps.
• Newest version. The highest version number in the version text, so a range counts by its upper end.
• Exclusions. Listings that sit on a shared hosting lobby or point at another network's address are left out, 4 of 216 public listings right now. The first looks of 18 October 2026 also counted duplicate listings of one server once.
• Blind spots. A proxy answers for its network, so its range describes the proxy. Velocity's ping-passthrough setting can pass parts of a backend's answer through, and it is off by default. Version text can be anything a plugin writes there. The protocol check shows what a server accepts for the one version we ping as. And these are public servers that want players, so private servers and Realms are not in it.

The ping method and the playable rule are on the methodology page. Which modes these servers run is in Minecraft game modes by the numbers.