FiveM artifact updates keep breaking server queries — and listings

A recurring support ticket on every FiveM listing site reads roughly the same: my server is full, why does your site say it is offline? The answer is almost always the same too, and it is worth understanding whether you run a city or just want to know what a status badge means.

How a listing knows a server is up

Listing sites do not connect to your server as a player. They query it — a small request to a status endpoint that returns player count, max slots and some metadata. That query is what drives every green dot you have ever seen on a server list.

Three things break it:

1. The artifact update changed the response shape. A field moves or an endpoint changes, and a query written against the old shape returns nothing useful.
2. The endpoint is rate limited or firewalled. Perfectly reasonable security hardening that also blocks the listing.
3. The server is behind a proxy that does not forward status requests. Common on setups built for DDoS mitigation.

In all three cases the city is running fine and players connect normally. The listing simply cannot see it.

What responsible listings do about it

The honest behaviour — and what this site does — is to distinguish between three states rather than two:

• Online. A successful query with a plausible player count.
• Offline. A query that reached the host and got a definitive negative.
• Unknown. No usable response. The server may well be running.

Showing unknown instead of guessing matters, because "offline" costs a server joins for a problem that is not theirs. If you see a city listed as unknown, check its Discord status channel before writing it off.

Any listing that only has two states is lying to you in one direction or the other. Query failure is not the same thing as a dead server.

What server owners should check

If your listing shows unknown or offline while you have 200 players:

1. Confirm the artifact version you are on and whether you changed it recently. Correlate the date with when the listing status changed.
2. Test your own status endpoint from outside your network. Not from the box, not from your home connection if it is whitelisted.
3. Check your mitigation provider's rules. Status query traffic looks like scanning traffic, because it technically is.
4. Check your proxy configuration if you run one. Forwarding game traffic but not status traffic is a very common half-configuration.
5. Republish your connect string anywhere it appears. A stale cfx join link is its own separate problem and produces identical symptoms.

What players should check

• The Discord status channel is more reliable than any listing, because it comes from the server itself.
• The connect string rather than the badge. If the direct connect works, the server is up regardless of what any site says.
• The population graph if the community publishes one. A flat line at zero with an active Discord is a query problem, not an empty city.

Why this keeps happening

FiveM's artifact cadence is fast, and server owners update for good reasons — security fixes, script compatibility, performance. Listing sites then chase the change. That cycle is not going away, and the realistic fix is not on either side alone: owners should test their status endpoint after an update, and listings should be honest about uncertainty instead of painting a red dot on a healthy server.

The cities on the FiveM server list all publish a direct connect string in their entry precisely so a query failure never costs you a night of roleplay. If a listing looks wrong, the connect string is the ground truth.