Public status pages
Let your users answer “is it down?” without asking you.
Let people answer it themselves
When something breaks, the same question arrives from every direction at once: is it down, or is it me? A status page answers it once, for everyone, so the replies you'd be typing get read off a page instead.
It shows the monitors you choose, each with ninety days of history and the incidents that made the marks. Green when you're up, honest when you're not, without you in the loop to say so.
Backed by the checks you already run
A status page isn't a second thing to keep true. It reads from the same monitors you already have, so what it shows is what actually happened, down to the check.
Pick which monitors are public and which stay internal. An outage on a public one appears on the page as it appears on your dashboard, because it's the same event.
Put it on your own domain
Serve the page from a hostname you own, status.yourcompany.com, instead of an UpCheck subdomain, so it reads as yours and not as a third party's. Point a CNAME at it and the certificate is handled for you.
Choose the monitors, set the title, and share the link. There's nothing to host and nothing to keep running.
Every outage,
written down as it happens.
A failed check opens an incident on its own, and it keeps a timeline: when it broke, what we saw, when it recovered. Nobody has to remember to write the post-mortem's first half.
Planned downtime
shouldn't page anyone.
Schedule a window and the checks keep running, but the alerts stay quiet and the uptime maths doesn't count it against you. One-off or recurring, per monitor.