Status page: what it is and why you need one
Updated 29 October 2026 · Læs på dansk
A status page is a public page that shows whether your service is running right now and how it has run lately. It saves you support requests when something goes wrong.
Why have a status page?
When a service is down, customers ask: "Is it me, or is it you?" With a status page they can see the answer without calling or writing. That relieves support and shows that you have operations under control. A status page that also shows historical uptime builds trust, because it does not hide failures.
What should a good status page contain?
- Current status at a glance: is everything running, or is there a disruption?
- Uptime for the last days, preferably as a row of coloured days so the pattern is visible.
- Recent incidents with start, end and duration.
- Planned maintenance, so nobody is surprised.
- A name and an address that are easy to share and remember.
Should it be public?
Yes, in most cases. It has to open even when your own website is down, so it should not live on the same server. Hide only the systems that are internal.
Uptime with and without planned maintenance
If you enter planned maintenance in advance, it should not pull the uptime figure down. Still show both numbers, so nobody can say you hide something. Read more about uptime percentage.
The status page from Tegra Uptime
Every Tegra Uptime account gets a status page with current status, uptime for the last 90 days, upcoming service windows and recent incidents. The address is not guessable and search engines do not see the page unless you share it yourself. You can hide individual systems. See also how to get started with monitoring.