How to Monitor FiveM Server Uptime and Get Alerted When It Goes Down

Add your server to CFXR's watchlist and it checks status on a schedule, keeps a history of player counts, and sends an alert the moment the server goes offline, comes back online, or crosses a player-count threshold you set — no separate monitoring service or script required.

For a FiveM server, uptime is not the same question as "is the process running." A server process can be alive while its actual gameplay endpoint is unreachable, stuck at a loading screen, or answering the Cfx.re server API but rejecting every join attempt. What players and server owners actually care about is whether the server is joinable and actively holding players — which is a slightly different, and more useful, signal than a raw process check.

That is why a meaningful uptime check has to query the server the same way a player or the public server list would: resolving the join code, hitting the live status endpoint, and confirming it responds with a valid player count, not just that something answered on a port.

On the watchlist page, add a server by its join code or cfx.re link. CFXR checks it on a recurring schedule and records whether it was online, how many players it had, and when its details last changed. Once a server is on your watchlist, you can configure alerts for it without writing any code.

Watchlist alerts can be delivered to a Discord webhook, a generic JSON webhook for your own automation, or email — whichever fits how your team already communicates. Discord is the most common choice for community servers since staff are usually already watching a Discord server around the clock.

You can choose which events actually trigger a notification: a server going offline or coming back online, the player count crossing a threshold you set (useful for catching an unexpected mass disconnect, not just a full outage), or a change to the server's reported details, such as its name or resource list. Turning on only the alert types that matter to you keeps the channel useful instead of noisy.

Every server tracked on CFXR gets a rolling uptime percentage over the last 24h, 7d and 30d windows on its server page, along with a weekly activity heatmap showing player counts by day and hour. The uptime percentage tells you how reliable the server has been recently; the heatmap tells you when players are actually online, which is useful for spotting whether a dip in activity lines up with a downtime window or is simply a quiet time of day for your playerbase.

If outages cluster around a specific time of day or day of the week, that is usually a stronger signal than a single isolated outage — it points toward a scheduled process (a backup job, a restart script, a resource that leaks memory over hours) rather than random infrastructure failure. Cross-reference the pattern against your own server logs and hosting provider status page before assuming it is a hosting issue, and use the watchlist's history as the record you point to when raising it with your host or a resource developer.