ARK server not showing on the unofficial list

Why your server is missing

There are far more ARK servers in the world than any browser can ask about at once. Both the Steam server browser and the in-game unofficial list work through a query batch, and there are three ways to end up outside it.

Query limits

Steam and the in-game browser can only query somewhere around 5,000 servers at a time. If yours is not in that batch, it does not appear. Nothing is wrong with it.

Listing delay

External sites such as ArkServers.net cover a far wider range than the in-game browser, but registration is not instant. It takes a few hours and sometimes up to 48.

Uptime

Servers that have been online continuously are more likely to show up in Steam and in-game results. A new server, or one that restarts often, keeps losing the standing it accumulates.

Read together, those three explain the pattern most owners report: the server was visible once, then vanished, then came back on its own. That is a batch you are moving in and out of, not a setting that keeps unsetting itself.

Check your server settings first

Before doing anything clever, rule out the two configuration mistakes that keep a server hidden regardless of everything else.

Set bIsLANMatch to false. If your server is flagged as a local network match it will not be publicly listed at all. In GameUserSettings.ini:

[SessionSettings]
bIsLANMatch=false

Confirm the query port is open and correctly forwarded. The query port is separate from the game port, and a server can be perfectly joinable by direct connect while being completely invisible to the browser, because the browser talks to the query port and players talk to the game port. If one is reachable and the other is not, that is exactly the symptom you get.

A2S query caching

A2S is the protocol Steam and the in-game browser use to ask a server for its name, player count, map and ping. Every entry you see in a server list is an answer to one of those queries.

A2S caching stores and forwards those answers. Instead of every query travelling all the way to your server and back, it is answered from a cache at the edge of the network, close to whoever asked. That does two useful things:

• Queries get answered quickly and reliably, so your server is far less likely to be dropped from a batch for being slow to respond or timing out under load.
• The ping shown in the browser reflects the distance to the cache rather than to the server, which on our network typically displays as around 10 to 30ms.

Our caching runs across more than 50 locations globally. The practical effect is that a server in the UK does not look like a distant, slow-responding server to a player browsing from elsewhere, and it stays in the query results rather than falling out of them.

Register on external listing sites

Sites like ArkServers.net are not bound by the in-game browser's batch limit, which makes them a far more reliable route for players trying to find a specific server.

1. Visit the listing site

   Go to ArkServers.net and find the add-a-server option.

2. Submit your IP and query port

   The query port, not the game port. Getting this wrong is why a submitted server never appears.

3. Wait for detection

   Usually a few hours. Allow up to 48 before treating it as a failure.

Uptime and why it matters

Stability is not just good practice here, it is a ranking input. Servers that stay online are more likely to be included in query results, and every restart resets some of the standing the server has built up.

Two things follow from that. Avoid unnecessary restarts, particularly in the first few days of a new server when it is most fragile in the listings. And if you are experimenting with seeds, world sizes or mod stacks, get that settled before you start advertising, because each of those changes means another restart at exactly the point where you least want one.

Direct connect as a fallback

While you are waiting to be listed, direct connect always works. Give your community the IP and port and they can join regardless of what the browser is doing.

Example address format:

123.45.67.89:27015

1. Open Steam

   The client itself, not the game.

2. Go to View, then Servers

   From the menu bar at the top of the Steam window.

3. Favourites, then Add a Server

   The button sits at the bottom of the window.

4. Enter the IP and port, then find games at this address

   Once it resolves, the server stays in your favourites and can be joined from the in-game Favourited tab.

Getting found once you are listed

Being visible and being found are different problems. Once the technical side is handled, what moves the needle is activity.

• Get your players to favourite the server. Favourited servers are reachable from the in-game Favourited tab regardless of the browser's mood, which means your regulars stop depending on search entirely.
• Keep an eye on your listing status. Check the external sites periodically rather than assuming a successful registration stays successful.
• Promote outside the game. Social media, forums and ARK communities all bring players who then join by direct connect, and a server with players on it is much more likely to stay in query results than an empty one.

That last point is the uncomfortable circularity of server browsers: the servers that get listed are the ones that already have players. Breaking into that loop is done from outside the browser, not inside it.