Status Page That Is Branded, Public, and Included in Every Plan
Give customers a single honest place to check whether you are up. UptimeHub turns your monitors into a polished public status page with your logo, colors, and domain, at no extra charge.
Checked from regions with auto-retry. No single-location false alarms.
All systems operational. Steady pulse across every region.
api.example.com returned no response from all 6 regions. Auto-retry confirmed the outage, then we alerted your team.
api.example.com is back up. The incident is logged to your status page history automatically.
90-day uptime · branded · your domain
Live demo · drive it, no signup needed
In short
A status page is a public web page that shows the current and historical health of your services so customers can check for outages instead of opening support tickets. UptimeHub builds yours automatically from the monitors you already run, so uptime, incidents, and 90-day history stay accurate without any manual updates. You can host it on your own custom domain, add your logo and brand colors, and group services into sections. Unlike Statuspage and other tools that charge separately for this, the branded status page is included in every UptimeHub plan rather than sold as a paid module. Because it is driven by read-only external checks, what visitors see reflects the same experience your real users get.
What you get
Status page for developers, SaaS teams and agencies
Included, not an add-on
A full branded status page ships with every plan, so you never pay a separate line item the way you do with Statuspage.
Your brand, your domain
Host on a custom domain with your logo and colors so the page feels like part of your product, not a third-party widget.
Powered by your monitors
Uptime, incidents, and history populate automatically from your checks, so the page is always current with zero manual work.
90-day uptime history
Visitors see a clear 90-day track record per service, building trust with the same data you use internally.
How it works
From URL to alert in four steps
Add your monitors
Set up the checks for the services you want to display publicly.
We check from 6 regions
UptimeHub verifies each service every minute and records the results.
Brand your page
Add a logo, colors, and a custom domain, then group services into sections.
Publish and share
Your status page goes live and updates itself, showing live status and 90-day history.
On this page
What a status page costs with and without monitoring
Hosted status pages are usually sold as their own subscription, separate from the monitoring that feeds them. Atlassian Statuspage runs from $29 to $1,499 a month per page, and both team members and email subscribers push you up the ladder: the sixth team member forces the $99 plan, exactly as subscriber 251 does. Our Atlassian Statuspage pricing guide finds your tier and annual cost, and Statuspage vs Status.io pricing shows where the cheaper rival wins at 11 to 50 team members.
On UptimeHub the status page is part of the monitoring plan. Starter includes one branded status page at $24 a month on annual billing, and Pro at $49 adds unlimited branded pages on your own custom domain, with no subscriber meter, and Pro carries unlimited team seats. If you are comparing dedicated vendors, status page pricing across 12 vendors lays the plans out side by side, and Statuspage alternatives covers who switches and why.
Incident platforms that bundle a status page meter it in their own way. PagerDuty prices status pages by subscribers, from $89 a month per 1,000, which PagerDuty status page pricing works through, and Jira Service Management only includes one on its Enterprise plan, from $2,500 a year for three agents, as Jira Service Management status page pricing shows. Before you design your own, the status page examples collection compares how 40 companies structure components, incident history and subscriptions.
FAQ
Questions buyers ask about Status page
A status page is a public page showing whether your services are currently working, plus a history of past incidents and uptime. It exists so customers can answer the question is it down for everyone or just me without opening a ticket, which cuts support load sharply during an incident and sets expectations while you fix it.
No, and this is the single most common mistake. If the status page lives on the infrastructure it reports on, it goes down in exactly the outage it exists to explain. Host it independently, on a separate domain or subdomain resolved outside your stack, so it stays reachable when everything else is not.
Post early with what you know, even if that is only that you are investigating. Name the affected service, say what customers will experience, and give a time for the next update rather than an estimated fix. Then keep the update cadence you promised, and publish a short summary once it is resolved.
Yes. When the page is driven by your monitors, a confirmed outage flips the relevant component to degraded or down without anyone logging in, and flips it back on recovery. Automatic updates handle detection, while written incident notes handle explanation, and a good page does both.
A public status page is open to anyone with the link, usually on status.yourapp.com, so any customer can check health without logging in. A private page sits behind a password or login and serves internal teams, one enterprise client or a set of partners. Check whether private pages cost extra before you buy, because several vendors reserve them for a much higher tier.
Monitoring is the machinery that checks your services from several regions, decides what is up or down and pages your team. The status page presents that same signal to customers in plain language. A status page with no monitoring behind it is only as accurate as the last manual update, which is why UptimeHub drives the page from your monitors in every plan.
For customer-facing use, yes. Serving the page on status.yourdomain.com keeps it recognizably yours, which matters when a worried customer is checking whether the page is legitimate. It also lets you point support replies and error pages at a stable address that does not change if you switch monitoring vendors.
More monitor types
Start monitoring in two minutes
Add a URL or endpoint and UptimeHub checks it every minute from 6 global regions, alerts you in seconds, and updates your branded status page. Read-only checks that never touch your servers.