For most independent Minecraft servers, listing sites are the top of the acquisition funnel — and they are ruthless about uptime. Every list runs its own crawler that pings your server on a schedule, and when those pings fail, you get flagged offline, sorted to the bottom, and eventually delisted. The cruel part: the crawler's view of you is not your view of you. Servers lose their ranking while the owner sees everything working.
How list crawlers see your server ¶
List sites do the same thing any player's client does: a Server List Ping against the address you registered, on their schedule, from their IPs. Each site keeps its own uptime score from those pings; the score drives your sort position, and sustained failures trigger "offline" badges and removal. Some also verify ownership and engagement through Votifier — the plugin that receives vote notifications — and a broken Votifier port quietly kills your vote flow even while pings pass.
The usual ways owners fail the crawl without noticing ¶
- Restart windows that line up with the crawl. A nightly restart at 04:00 looks like daily downtime to a crawler that happens to ping at 04:01. Enough of those and your uptime score sinks. Stagger restarts, or at least keep them short.
- DDoS filters eating the crawler. Game-host DDoS mitigation and over-eager firewall rules rate-limit or block unfamiliar IPs — which is exactly what a list's crawler is. Players connect fine; the crawler times out; the list marks you offline. If your listing flaps while players never complain, suspect this first.
- You moved hosts and DNS lagged. After an IP change, old DNS answers keep circulating until TTLs expire — crawlers with long caches ping the corpse of your old host. The mechanics are the same as any DNS propagation story; the fix is lowering TTL before a move, not after.
- A dead or wrong SRV record. Java clients and crawlers both honor
_minecraft._tcpSRV records. If the record points at a stale port or a decommissioned proxy node, everyone following it bounces — and listings registered with the bare domain fail even though the direct IP works. - Registered the wrong address. A listing created with a numeric IP breaks the day you migrate; a listing with your domain survives moves. Always list the domain.
- The proxy is up, the backend isn't. On BungeeCord/Velocity networks the proxy answers pings even when the lobby behind it is dead — some crawlers now attempt deeper checks, and players who join and get kicked will downvote you anyway.
Find out before the list does ¶
The structural problem is observational: the crawler watches you from outside, and you watch from inside. Close that gap by watching yourself from outside too. A Minecraft monitor pings your public address on a schedule from an external vantage point — the same view a list crawler has — and emails you on the first failed pattern, with a public status page you can link from your listing so players can verify outages themselves. If your monitor shows clean uptime while a list shows you offline, you've isolated the problem to the crawler path (their IPs being filtered) rather than your server, which is exactly the evidence to bring to the list's support and to your host's firewall settings.
Getting relisted ¶
- Fix the reachability first and verify from outside — not from your own machine, which may bypass the broken path.
- Whitelist crawler traffic in your host's firewall/mitigation panel where the list publishes its IP ranges; several major lists do.
- Re-verify the listing (address, port, SRV) and test Votifier end-to-end with the list's own test-vote button.
- Then let the score recover. Most lists compute uptime over a rolling window — days of clean pings, not an appeal, is what restores position. Meanwhile your monitor's history tells you the streak is actually intact.
FAQ ¶
The list says offline but players are connected. Who's right?
Both, about different paths. Players reach you through one route; the crawler's route is blocked or throttled. Treat it as a real problem anyway — the same filter is turning away some fraction of new players, and your listing rank is paying for it.
Does in-game lag hurt my listing?
Not directly — crawlers measure ping success, not tick rate. It hurts indirectly through votes and reviews. Lag and downtime are different diseases; this post separates them.
How fast should I find out about downtime?
Faster than a crawler's next visit. A monitor checking every five minutes with alerts after two consecutive failures gives you roughly a ten-minute detection bound — usually well inside a list's flagging window, and always before a day of lost ranking.