TF2 server monitoring
KeenCrow asks your Team Fortress 2 server for its status the same way the in-game server browser does, and tells you when it stops answering. You see the server name, the map and how many players are on.
Setting it up
- Create an account with your email address. One server is free.
- Choose "Game server (Steam query)" and enter the public IP address or hostname and the port, for example
203.0.113.10:27015. 27015 is the usual TF2 port. - The first check runs within a minute. On any paid plan, add a Discord webhook so the alert lands in your community's channel.
Why TF2 servers go quiet
- A game update. When Valve updates TF2, servers that have not updated turn players away until they are updated through SteamCMD. A monitor tells you it happened before your regulars do.
- A crash. A plugin error or a bad map can take the server process down. If nothing restarts it, it stays down.
- The machine or host. A reboot, a full disk or a network problem at the host looks the same from outside: no answer.
One missed answer never alerts. KeenCrow asks again after about 20 seconds and again 30 seconds later, and only three misses in a row count as an outage. You get one message when it is confirmed and one when the server is back.
Before an update or a restart
Press Pause on the server's page in your dashboard so planned work does not count as an outage, and Resume when you are done.
The free plan checks one server every 5 minutes with email alerts. Starter checks 3 servers every minute and posts to Discord for $2 a month. See everything game server monitoring does.