A public status page,
included with your monitoring
Your monitoring already knows what's up. A status page just publishes it — without a second subscription, a second account or another vendor to keep in sync.
Why a separate status page is a pain
The usual setup runs monitoring in one product and a status page in another. The monitoring tool already knows, to the second, whether a service is up. The status page — a different vendor, a different login, a different bill — does not. So someone bridges the gap by hand: an outage starts, the monitoring tool pages the team, and then a human remembers to go and post an incident on the status page. Often a few minutes late, sometimes not at all.
That is two sources of truth for one fact. The data drifts, the status page lags reality, and you pay a second subscription for the privilege. The fix is not a better status page product — it is having the status page read from the monitoring you already trust.
What you get out of the box
The status page is a customer-facing view of monitors you are already running:
- Opt-in per monitor — nothing is published until you choose it. You decide exactly which monitors are public; internal services simply never get surfaced.
- Live status, driven by monitor state — an operational / down badge per published monitor, updated from the same checks that drive your alerts. No manual incident posting.
- Uptime history — rolling 24h / 7d / 30d uptime percentages and a 90-day daily timeline, one bar per day, so visitors can see how the service has actually performed.
- Incident history — current and resolved incidents appear automatically when you enable the toggle, derived from monitor state rather than hand-written.
- Your branding — title, description, logo, a light / dark / auto theme and custom CSS for brand-matching tweaks.
- Custom domain — host the page at
status.yourcompany.cominstead of the default URL. A JSON status feed is served alongside it for pulling status into your own app.
Who it's for
This fits teams that want a clean, honest status page without running a second product to get one. Small and mid-sized SaaS that need to show customers a service is healthy. Internal IT teams publishing the state of shared systems to the rest of the company. Agencies that want a per-client status page without a per-client subscription somewhere else.
It is deliberately not aimed at the enterprise incident-communication niche — SOC 2 attestation pages, layered subscriber segmentation, templated multi-stakeholder comms. That is Atlassian Statuspage's lane, and if you need it, Statuspage is the right tool. This is for the much larger group of teams whose real requirement is "publish whether the service is up, without paying twice."
What it's not
Honesty up front saves everyone a migration later. The status page is not a full incident-communication platform. It does not maintain a public subscriber list with email updates — alerting goes to your team's channels, not to your customers' inboxes. It does not do component hierarchies, subscriber segmentation by region or service, or templated stakeholder comms.
If those are hard requirements, you will outgrow this page, and a dedicated tool is the honest recommendation. For everyone else, "publish monitor state, with uptime history, on your own domain" is the whole job — and that is exactly what is included.
Publish your first status page in 60 seconds
Publishing is UI-driven — no embed code to paste, no SDK to install.
- 1
Enable the status page
In the console, open Settings → Status page and toggle it on. Set a title and description.
- 2
Choose which monitors are public
Opt each monitor in individually. Nothing is exposed until you do, so internal checks stay private by default.
- 3
Share the URL — or your own domain
The page is live immediately at its hosted URL. Point a custom domain at it to serve it from
status.yourcompany.com.
Frequently asked questions
Can I use my own domain for the status page?
Yes. A status page is hosted at uptime.statusharbor.io/<page-id>.html by default, and you can point a custom domain at it — for example status.yourcompany.com. The JSON status feed is then also served from your domain, so anything you build on top of it does not need to know the internal page id.
What gets published on the status page?
Only the monitors you opt in. Nothing is exposed until you explicitly choose it — you pick which monitors are public. For each one the page shows a live operational / down badge, rolling 24h / 7d / 30d uptime, a 90-day daily timeline and, if you enable the toggles, recent response time and incident history.
Are incidents posted automatically?
Incident history on the page is driven by monitor state — when a published monitor fails and recovers, that incident appears in the history without anyone writing a post. The status page is a customer-facing view of monitoring you are already running, not a separate thing to keep in sync by hand.
Does it send email updates to visitor subscribers?
No. The status page is read-only for visitors — there is no public email-subscription list. Alerting is for your team: Status Harbor sends monitor alerts to Slack, Telegram, email or a webhook. If a subscriber-notification list is a hard requirement, a dedicated incident-communication tool is the better fit.
Can I make the status page private?
The page itself is public, but you control exactly what it reveals. Nothing appears until you opt a monitor in, so an internal-only service simply never gets published. The page is read-only — visitors cannot acknowledge or resolve anything; those actions stay in your dashboard. There is no built-in password gate on the page.
How is this different from Statuspage.io?
Atlassian Statuspage is a dedicated incident-communication platform — subscriber segmentation, component hierarchies, templated comms — sold separately and priced accordingly. Status Harbor’s status page is a feature of the monitoring product: it publishes the monitor state you already have, with no second subscription. If you need Statuspage’s enterprise comms features, use Statuspage. If you want a clean public status page bundled with your monitoring, this is it.
One product for monitoring and status
No second subscription, no second account. Publish from the monitoring you already run.
Start with Status HarborRelated
- Uptime monitoring for SRE — the monitoring whose state the status page publishes.
- Kubernetes monitoring — surface cluster health on a public status page.
- Private network monitoring — keep internal checks private; publish only what you choose.