Checkmate queries game servers over their native protocols, more than 100 game types in all. When the server dies mid-session, the alert beats the complaints thread.
An HTTP check tells you nothing about a Minecraft server. Game monitors speak each game's own query protocol, so the check answers the question that matters: would a player get in right now?
More than 100 game types are supported, from Minecraft and Counter-Strike to the long tail of dedicated servers communities run.
Discord and Telegram are native notification channels, so the admin channel hears about a crash the moment it happens. 11 other channels cover the rest of your setup, webhooks included.
Set the check interval to match how twitchy you want the alerts, and use maintenance windows so a planned wipe or mod update doesn't page anyone.
Give your community a public status page with per-server uptime instead of answering the same question 40 times after every outage.
It runs from your own Checkmate instance with your branding, so it looks like your community, not like a monitoring vendor.
You run the Minecraft or survival server your community depends on. Know it crashed before the complaints thread starts.
Hundreds of customer servers, one dashboard. Tags keep the fleet sorted and there is no per-monitor pricing to outgrow.
Practice servers matter on a schedule. A quick alert means the server is back up before scrim time, not discovered dead at it.
Each game type is checked over the protocol its own clients and tools use. A response means the game process answered, which says more than an open port ever can.
The server can live on a game host, a VPS or the machine under your desk. If your Checkmate instance can reach it, it can be monitored.
Game servers get the same incident timeline, acknowledgements and history as production APIs. Outage patterns across weeks are visible, which is how you catch the mod that leaks memory every Saturday.
Game checks are small queries on an interval you set. A modest instance watches a large fleet without breaking a sweat.
More than 100 game types, each queried over its native protocol. Minecraft and Counter-Strike are the common cases. The list covers most dedicated servers communities run.
Yes. Add a game monitor, pick Minecraft as the type, point it at your server and set the interval. From then on Checkmate queries it like a client would and alerts when it stops answering.
Yes, Discord is a native notification channel. Alerts post to your admin channel through a webhook. Telegram, email and 9 other channels cover whatever else you run.
No. The dashboard tracks whether servers are up and reachable, not who is online. If live player statistics matter to you, pair Checkmate with a game-specific stats tool.
Yes. Put your game servers on a public status page with uptime history, served from your own instance with your branding. One link answers the question forever.
Nothing. Checkmate is open source under AGPL-3.0. Self-host it and monitor as many servers as your community runs.
Websites and APIs checked from 6 continents.
Certificate expiry caught before browsers complain.
CPU, memory, disk and network via the Capture agent.
Container status, health checks and resource usage.
Branded public pages served from your own instance.
12 native channels, from email to PagerDuty.
All featuresCheckmate is open source under AGPL-3.0. Self-host it and this feature ships free, on your servers, with your data.