Half of “is it down?” phone calls vanish the day clients get a status page link. The other half of this guide is what the page honestly is — and is not.
Every outage produces the same flood: calls and messages asking whether the problem is known. Uptime Kuma's status page feature answers before they ask — a public web page showing which services are up, which are down, and what you are doing about it. Setting one up takes ten minutes. Setting one up well means thinking about what the public should see, and being honest about the page's limits.
👆 What a client sees: one clear headline, the services they use, nothing else. Internal device names and IP addresses do not belong here.
/status/support. This becomes the link you share, so keep it short and permanentPublish only client-facing services: the website, the client portal, mail, the booking system. Two reasons. First, relevance — clients do not care that “Printer 2nd Floor” is down. Second, security — a public page listing internal host names, server roles and IP addresses is a free network map for attackers. Group the published monitors under friendly headings (“Our Services”, “Email”) with plain names a non-technical client understands.
The monitor rows update automatically, but the explanation is your job. During an incident, pin a short note: what is affected, since when, and that it is being worked on. Announce planned maintenance in advance the same way — combined with Uptime Kuma's maintenance windows, clients see “planned work on Sunday 2 AM” instead of discovering a mystery outage. Two or three honest lines during an incident buy more goodwill than a perfect uptime record ever will.
A status page nobody knows about changes nothing. Add the link to your email signature, website footer, support page and invoices. If you run your own domain, the page can be served under your own address through a reverse proxy — a nice finishing touch, but get the simple link working and shared first; polish later.
Watch the video to see the Uptime Kuma dashboard and status features working live, then publish your own page from this guide.
▶️ Watch Full VideoYes — anyone who has the link can open it; there is no built-in password. That is why the choice of published monitors matters: list friendly service names only, never internal host names, IP addresses or anything that maps your network for a stranger.
The monitor rows do — they reflect Kuma's live checks and uptime history automatically. The words are yours: incident explanations and maintenance announcements must be posted by a human. Automatic numbers plus human honesty is exactly the right division of labour.
Possibly both. Kuma checks from where Kuma sits; the client checks from their network. Their local internet, DNS or a regional route can be broken while your service is healthy. The page still helps: it turns an argument into a diagnosis, because you now know the service itself is answering.