A server that was in the list yesterday is not in it today. The machine is up, players are on it, nothing was changed. This happens constantly, and there are about six causes — none of which is the one people assume.
First: is it actually gone
Before diagnosing anything, connect directly. In most Source games that is connect ip:port in console; Minecraft has Direct Connection in the multiplayer menu; FiveM takes connect from F8.
If the direct connection works, the server is fine and you are debugging a listing problem. That is a completely different investigation from a server problem, and conflating the two is why people spend an evening reinstalling something that was never broken. The same split is described in the difference between the game port and the query port, and it is the single most useful distinction in this whole area.
Cause one: the query stopped being answered
The most common. Something is now refusing or dropping the query packets while the game port carries on working.
Usually one of:
- A firewall rule added for something unrelated that narrowed UDP
- A host migration where the query port mapping was not carried over
- Query rate limiting tightened by a panel update
- The server binary updated and reset a query-related setting to its default
The tell is that every list loses you at once. If one directory shows you and four do not, it is not this.
Cause two: rate limiting caught the directories
Source servers ship with sv_max_queries_sec and friends, which exist so your machine cannot be used to amplify a denial-of-service attack against somebody else. That is a good default and worth keeping.
Set too tight, it drops legitimate query traffic along with the abuse. Directories query on a schedule; several of them querying near the same minute looks, to a strict limiter, like a small burst of identical requests from different addresses — which is exactly the shape it was configured to refuse.
The symptom is distinctive: you flicker. Present on some sweeps, missing on others, with no pattern that maps to anything happening on the server. If your listing's uptime figure is lower than you know it should be, this is the first thing to check, because a dropped query and a down server are indistinguishable to whoever is asking.
Cause three: the address changed and nothing was told
A dynamic IP that rotated. A host that moved you between machines. A DNS record repointed while every directory still holds the old address.
Directories store what they were given. If you were listed by IP and the IP moved, the list is now querying an address that belongs to somebody else — which either times out or, occasionally and confusingly, answers as a completely different server.
This is the argument for being listed by hostname rather than raw IP wherever the game supports it, and for claiming your listing so you can correct the address yourself rather than waiting for a sweep to notice.
Cause four: the version moved out from under you
A game updates, the server updates, and the protocol number changes. Clients on the old version can no longer see or join you; clients on the new one can.
In Minecraft this shows as a red X and an incompatible-version message. In Source games it is usually a straightforward failure to connect. Either way, half your regulars report the server as "gone" and the other half are playing on it, which is a confusing enough signal that operators often chase the wrong cause for a day.
The reverse also happens: the client updated and the server did not, because it is pinned to a branch. That case is covered in SteamCMD and app IDs, and it is worth checking the branch before anything else when a fleet empties within an hour of a patch.
Cause five: the browser is filtering you out
Not every disappearance is technical. In-game browsers apply filters, and players forget they set them.
- An empty-server filter hides you the moment you drop to zero
- A version filter hides you after an update
- A region filter hides you if the list's geolocation of your address changed
- A "not full" filter hides you at peak
Server browsers also cache aggressively. A stale local cache can show a server that is gone and hide one that is present, and the fix is a refresh rather than an investigation.
Cause six: the directory decided
Every list has rules. Some delist servers that have been offline for a fortnight. Some remove listings whose hostnames breach content rules. Some prune anything that has not answered a query in a month.
These are usually reversible and rarely announced. If a single directory has dropped you and the others have not, this is the likeliest explanation and the fix is asking them rather than changing anything on the server.
The diagnostic order
Work down this list and stop when something is true:
| Check | If it fails |
|---|---|
| Direct connect works? | No — it is a server problem, not a listing one |
| Missing from all lists? | Yes — query side: firewall, port, rate limit |
| Missing from one list? | That list's rules, or its own outage |
| Flickering on and off? | Query rate limiting, almost always |
| Started after a game update? | Version or branch mismatch |
| Only you cannot see it? | Your own browser filters and cache |
The first two rows resolve the large majority of cases and take about two minutes between them.
What operators should not do
Do not reinstall. Nothing in this list is fixed by reinstalling, and a reinstall introduces a fresh config that may reintroduce the original cause.
Do not change the hostname to attract attention. Renaming during an outage means that when the listing does come back, it comes back under a name nobody recognises, and you have converted a technical problem into a continuity problem.
Do not assume malice. Directories are not withholding your listing. The overwhelming majority of vanishings are a UDP packet not getting somewhere, and the second largest category is a filter in the reader's own client.
For players
If a server you like has disappeared, it has very likely not closed. Try the direct connection before concluding anything — the address is usually still in your recent servers or your Discord history.
This is doubly true for games that are older or less popular, where the query infrastructure around the game has decayed further than the community has. A lot of what looks like a dead scene is a live scene with a broken index.
The short version
Direct connect first. It splits the problem in half in thirty seconds. Missing everywhere is a query-side fault on your machine; missing in one place is that place's decision; flickering is rate limiting; and vanishing right after a patch is a version mismatch.
Almost none of it means the server is broken, and none of it is fixed by reinstalling.
- Tags
- troubleshootinglisting
- Share
Published · 6 min read