Server status with Statusboard
The page is set up for a small fleet: a main server, a mirror and a game or community server. Each is checked over HTTPS from outside your network, so it shows what your users actually see.
- Point each component at an HTTPS URL served by that server.
- Save; checks start within 5 minutes.
- Post an incident for planned restarts or maintenance.
- Share the page with your users, community or team.
What to know
A check from inside your own network cannot tell you that the server is unreachable from outside: DNS, certificates, firewalls and the hosting provider's network all sit between your users and your machine. Statusboard checks every URL from the public internet, the same way your users reach it.
Checks are HTTP GET requests with a 10 second timeout. A server that does not speak HTTP, such as a game server on a custom port, can be represented by a small health page on the same machine or listed without a URL and updated through incidents.
Private addresses, localhost and internal ranges are refused, both to protect your network and to keep the checks honest. If a server should be private, monitor a public endpoint that depends on it instead.
Updated · Cosmovex
Questions
Can it ping a server by IP?
It checks HTTPS or HTTP URLs, not ICMP ping. Serve a small health page on the server and check that.
Can I monitor a game server?
If it exposes a web page or status endpoint, yes. Otherwise list it without a URL and use incidents.
How quickly does a failure show?
Within 5 minutes: the next check marks the component down.
Is Statusboard free?
Yes: one page with 3 components, checks every 5 minutes, incidents and 30 days of uptime bars, with a small "Powered by Statusboard" footer. Pro is $9 a month for 5 pages, 25 components, 90 days of history, no footer and email alerts.
The free plan covers everything on this page. Statusboard Pro ($9/mo, billed monthly) is described on the Statusboard page.
