Free status page tool
Give your users one uptime status page to check whether you're up: real, live-computed uptime for every service you monitor, a clear incident timeline when something breaks, and automatic email or RSS updates for anyone who wants to follow along.
How a status page stays true, from the check to the subscriber
Turn the checks HostTracker is already running into a branded page your customers can check themselves, instead of emailing you to ask "is it down?"
Every component shows real, live-computed status, not a badge someone forgot to update. HostTracker tells "no data yet" apart from "confirmed down," so a quiet monitor is never miscounted as an outage.
A 90-day heatmap with hover popovers and a response-time chart give visitors the history behind today's status, not just a single up/down badge.
Add any of your existing monitored checks as a component, reorder them, and group related ones under a shared name - API, Website, Checkout - however your users think about your product.
Declare an incident - Investigating → Identified → Monitoring → Resolved - tag the affected components, and post a running update timeline, kept separate from the auto-derived downtime the heatmap already shows.
Visitors subscribe by email with double opt-in, get a message on every incident update, and can unsubscribe from the link in any email - or skip email and just follow the RSS feed, no mailing list to maintain by hand.
Add your logo, an accent color and an announcement banner, and password-protect the whole page if it's private.
The same product, watching the same service you are reading about.
Each row is a monitor: its state now, a 90-day heatmap and its uptime for 24 hours, 7 and 30 days.
Declared incidents with their update timeline sit above the automatically derived downtime, kept apart on purpose.
View HostTracker's live status page ↗Most pages are live within minutes. Only the name and the address are required; everything else can change later.
Websites, servers, APIs, certificates. One check type per page, the same locations, alerts and reports behind all of them.
"I've worked with this monitoring service for a long time, and my daily routine is no longer a problem. It quietly watches all my sites and lets me respond the moment something goes wrong."
Trusted by teams at
Every chapter opens in place, so the page stays short.
A public status page shows, on a site hosted apart from your own, whether each part of your service works right now and what you are doing about anything that doesn't. It is where people look first when something seems wrong, instead of your support inbox.
During an outage, every customer who can't tell whether the problem is theirs or yours opens a ticket. A page that answers "is it down, and since when?" turns those questions into one link, and an incident already posted tells visitors you are on it. Over time its history becomes the record a prospective customer checks before signing up.
For a product-neutral explanation, read what a status page is and what belongs on one.
A useful page answers three questions fast: what is affected, how bad it is, and when visitors will hear more.
| Element | How HostTracker fills it |
|---|---|
| Components | One row per monitor you choose, with live status, under group names you set |
| Overall status | Worked out from every row and open incident: All Systems Operational, Degraded Performance, Partial Outage, Major Outage or Under Maintenance |
| Incidents | Posts you write, with a status, an impact level, the affected rows and a timeline of updates |
| Maintenance | Scheduled windows, shown before they start |
| History | A 90-day uptime bar per row, uptime percentages, a response-time chart and past incidents |
Name components the way customers think: "Checkout" means something to a visitor, "web-03" doesn't. A service you rely on but don't monitor, such as a payment provider, can be a third-party row whose status you set by hand.
Post as soon as a problem is confirmed, even if all you can say is that you are looking into it. Then move the incident through four stages:
Promise a time for the next update and keep it, even when nothing has changed. Each update lands on the incident's timeline and goes to your subscribers. Repeat announcements can be saved as templates, and a resolved incident can get a postmortem on its own page.
Schedule a maintenance window with a start, an end and the components it covers, and visitors see it as upcoming before the work begins and as in progress while it runs. Failures inside the window are marked as maintenance and not counted against the uptime on the page, so a planned migration doesn't look like an outage in your 90-day history.
The header shows Under Maintenance only when nothing else needs reporting: an open incident or a failing check always outranks it, so a window never hides an outage. Maintenance windows you already set for your monitors can appear on the page automatically through their "Show on status page" switch.
The choice comes down to what you want to own.
| Question | Hosted status page | Self-hosted status page |
|---|---|---|
| Who keeps it running | The provider | You: updates, backups, security patches |
| How status changes | Usually from the provider's monitoring, automatically | From scripts or a tool you connect, or by hand |
| Survives your outage | Yes, if the provider is independent of your hosting | Only if it shares nothing with what failed: network, DNS, cloud account |
| Control | Within the provider's options | Full control of code, data and design |
| Cost | A subscription or a free tier | No license, but server time and staff time |
Both share one rule: a status page that goes down with your product is worse than none. That is the main reason most teams choose a hosted status page. Self-hosting makes sense when the page must live inside a private network, keep every byte on your own servers, or run code you want to change. For a public page whose job is to stay reachable while your systems are not, a page run by an independent monitoring service is usually simpler.
Many teams run monitoring that alerts them plus status page software someone updates by hand. In HostTracker it is one system. Each component is a monitor you already run, so the page changes on the same confirmed results that send your alerts, and nobody has to flip a switch at 3 a.m.
Times are shown in each visitor's own time zone. Every status-page operation is also in the REST API v2, the command-line client and the MCP server, so a script or an AI assistant can post an incident for you.
Choosing your first page, or a status page alternative to a tool you have outgrown? Ask:
A public status page is a web page that shows whether each part of your service is working right now, with current incidents, planned maintenance and recent uptime. Customers check it before contacting support, so it cuts tickets during an outage and shows you are already on the problem.
Yes. HostTracker's permanent free plan covers monitoring two sites, and any monitor you're already running can become a status page component at no extra cost - there's no separate "status page" subscription to buy. A 30-day full-feature trial also unlocks every check type and up to 100 monitors if you want to test a larger setup first, with no credit card required. Paid plans, needed once you outgrow the free monitor limit, start at around $5 a month.
Sign up for a free HostTracker account, add a check for each service you want visitors to see - your website, your API, checkout, whatever matters to your users - then open Status Pages from your dashboard, pick those monitors as components, set a title and accent color, and publish. Your page goes live immediately at its own status.host-tracker.com URL, no separate hosting or DNS work required.
A hosted status page runs on the provider's infrastructure, so it stays reachable when your own servers or DNS fail, and there is nothing to patch. A self-hosted page gives you full control of code and data, but you run it, feed it status yourself, and must keep it apart from the product it reports on.
Not with HostTracker. Every component on your status page is one of the monitors you already run, so its status changes automatically from the same confirmed checks that trigger your alerts, with no second tool to connect.
Yes. Schedule a window with a start, an end and the affected components, and visitors see it before the work begins. Failures inside the window are shown as maintenance and not counted against your uptime, and maintenance windows you already set for your monitors can appear on the page automatically.
Yes. Anyone can subscribe by email with a double opt-in, and they'll get a message whenever you post or update a real incident. They can unsubscribe at any time from the link in every email, or skip email entirely and follow your page's RSS feed instead.
You set the name, logo (plus one for the dark theme), favicon, accent and header colors, light or dark theme, layout density, logo position, grouping, and which sections visitors see. A small "Powered by HostTracker" credit stays in the footer.
It's live-computed from HostTracker's own checks against your monitored URL, not a manually set badge. The page shows current up/down status, a staleness indicator if a check hasn't reported recently, 24-hour/7-day/30-day uptime percentages, a 90-day heatmap with hover detail, and a response-time chart - and it correctly distinguishes "no data yet" from "confirmed down" rather than treating both the same.
You declare a real incident - Investigating, then Identified, Monitoring, and finally Resolved - tag which components are affected, and post updates as you learn more. Subscribers are notified on every update, and the incident gets its own page with a full timeline, distinct from the automatically derived downtime the heatmap already shows on its own.
Every page can optionally be password-protected end to end, so only visitors who know the password can view it.
Yes. Status pages are part of HostTracker's REST API v2, so you can create pages, set components, post incidents and updates, and manage subscribers with a scoped token, or do the same from the CLI, the SDKs or the MCP server.
Create a free HostTracker account and publish your status page today - no credit card required.
