What we ask the server
FXServer publishes /info.json and /dynamic.json over HTTP on the same port players connect to (30120 by default). We read the server name, player count and max clients from those.
See whether an FXServer answers from the internet, how many players are on, the slot count and the response time.
Checked from our server on the public internet. We don't store the addresses you check or any player names. Private and local addresses are refused.
FXServer publishes /info.json and /dynamic.json over HTTP on the same port players connect to (30120 by default). We read the server name, player count and max clients from those.
Online or not, players and sv_maxclients, the server name as plain text and the response time. We never show the player list, even though /players.json can expose it.
RedM runs on FXServer as well: choose RedM in the list.
More on query ports and what a status check can and can't tell you in the basic mode guide, and everything ServerStats tracks on FiveM servers.
Enter its IP or hostname and port (30120 by default). We read the same public info endpoints the server list uses, from outside your network.
Most often TCP 30120 is closed in a firewall, the server is still starting, or the address is the txAdmin panel's port instead of the game port.
No. We only show counts. Names aren't displayed or stored.
Status checks can't see inside the server. The ServerStats resource measures server-thread time and hitch warnings; see the FiveM CPU guide.
Basic mode runs this check continuously for one server, keeps the history and alerts you in Discord when it goes down.