hosted status page software
Status page software that hosts and auto-updates your status page
Short answer: status page software is a tool that runs a public page showing whether your service is up, what is broken during an incident, and your uptime history over time. The two real choices are hosted software that a provider runs for you, and open-source software you install and maintain yourself. Hosted wins on one thing that matters most: it stays online when your own servers do not. AlertPing includes hosted status pages on every plan, driven automatically by the same 30-second checks that watch your site, so the page shows real status instead of a number someone edits by hand.
Last updated July 2026 · Hosted status pages on every plan
alertping ▸ run check
live
▸ type a domain and run a real-feel check
▸ probes from 3 regions · FRA · IAD · SIN
▸ waiting…▌
queued probing▌
If ever goes down, you get:
Alert fired ▸ 2 channels · 6.2 s after first failure
AlertPing app
● DOWN : HTTP timeout confirmed from 3/3 regions (FRA, IAD, SIN). Incident opened.
sms · on-call
AlertPing: DOWN. Confirmed 3/3 regions . First fail: Frankfurt.
what it does
What status page software actually does
A status page has one job during the worst hour of your month: answer "is it you or is it me?" in public, once, so your support queue does not fill with the same question a hundred times. Good software makes that page easy to run and, crucially, keeps it truthful without you babysitting it.
Component health
Each part of your service (website, API, dashboard, payments) shown as operational, degraded, or down.
Incident timeline
Open an incident, post short updates as you investigate and resolve, and keep the record public afterward.
Uptime history
A rolling record, often 90 days, that a buyer checks before they trust you with an SLA.
Subscribe and notify
Visitors sign up for email, SMS, Slack or webhook updates so they hear about incidents without refreshing.
your options
Hosted vs open-source vs a page you edit by hand
There are three honest ways to run a status page. Each is a real choice with a real trade, so here they are side by side rather than pretending one is right for everyone.
| Approach | Hosted software | Open-source, self-hosted | Manual page you edit |
|---|---|---|---|
| Examples | AlertPing, Statuspage.io, Better Stack, Instatus | Cachet, Uptime Kuma, Statping-ng | A hand-built HTML page or a pinned banner |
| Stays up in your outage | Yes, hosted off your infra | Only if hosted somewhere separate | Depends where it lives |
| Updates from monitoring | Yes, automatic | Sometimes, with setup | No, all by hand |
| Setup time | Minutes | Hours to days, plus upkeep | Minutes, then constant editing |
| Ongoing cost | A monthly fee | Free software, your server and time | Your time, every incident |
| Best for | Teams that want it reliable and off their plate | Teams with ops time and a control requirement | A one-off or a very early project |
If you have the ops time and a hard requirement to own everything, open-source status page software is a legitimate, genuinely free choice, and Uptime Kuma in particular is excellent. For most teams the deciding factor is the second row: a status page has to survive your bad day, and the free option is the one most likely to be sitting in the same data center as the thing that just went down.
the trap
The mistake that makes a status page useless
The most common status page failure is not a missing feature. It is where the page runs.
Same-server status pages go dark together
Install an open-source status page on the same box, cloud account or Kubernetes cluster as your app, and a real outage takes both down at once. Customers arrive at a status page that will not load, during the exact incident it exists to explain. Hosting the page somewhere fully independent is not a detail, it is the whole point.
Hand-edited pages drift into fiction
A page you update by hand lags reality. During an incident nobody remembers to change it, and a page that shows all green through a real outage teaches customers to ignore it forever. A status page that pulls its state from live monitoring cannot quietly lie, because it is not the one deciding what to show.
AlertPing hosts your status page on our infrastructure, not yours, and drives it from the same checks that watch your service. When a real outage is confirmed across regions, the page and your alerts come from one source of truth, so the public update and your on-call page never disagree.
what to look for
What to look for in status page software
Most tools list the same checkboxes. These are the six that actually decide whether the page does its job when you need it.
-
1
Hosted off your infrastructure
The page must not share the outage. If it lives where your app lives, it is not independent.
-
2
Auto-updates from monitoring
The page should read live check results so component status changes without anyone touching it.
-
3
Your own branded domain
status.yourdomain.com with your logo reads as yours, not as a generic third-party widget.
-
4
Subscriber notifications
Email, SMS, Slack and webhook subscriptions pull people off your support channels during an incident.
-
5
Real uptime history
A published 90-day record, straight from monitoring, is the receipt an SLA buyer checks before signing.
-
6
Public and private views
A public page for customers and a private one for the team, so internal detail never leaks into the plain-language update.
how it works
How AlertPing's status page keeps itself honest
The monitor measures and the page publishes. Because both live in one system, the page reflects reality without a human in the loop deciding what to admit.
1
Checks run every 30 seconds
Your endpoints are checked as often as every 30 seconds on Team and Business plans (60 seconds on Starter), from three regions, so a single flaky path does not flip your page to red.
2
Confirmed outages flip components
When Frankfurt, Virginia and Singapore agree a component is down, its status on the page changes automatically, and the uptime history records the exact window.
3
One source of truth
The same event that updates the page fires your SMS, email, Slack and webhook alerts, so your team and your customers are never told two different stories.
Where we are honest about the limits
AlertPing is uptime monitoring with a hosted status page attached, not a full incident-management suite. If you need heavy on-call scheduling, deep incident retrospectives and log correlation, a tool like Better Stack does more there, and the incumbent Statuspage.io has the most polished incident workflow in the category. What we do is keep the page reliable, hosted off your infrastructure, driven by real checks, and included in a flat plan from $19 rather than sold as a separate per-page add-on.
common questions
Status page software questions, answered
What is status page software?
Status page software runs a public page that shows whether your service is up, what is broken during an incident, and your uptime history over time. It manages component health, an incident timeline, and subscriber notifications. The good ones pull their status from live monitoring so the page updates itself instead of relying on someone to edit it during an outage.
Is there free status page software?
Yes. Open-source options like Uptime Kuma, Cachet and Statping are genuinely free, and several hosted tools have a free tier for a single page. The cost of the free open-source route is not money, it is your time to host, secure and update it, plus the risk that a self-hosted page goes down in the same outage it is meant to explain.
What is open-source status page software?
Open-source status page software is a project you install and run on your own servers, with the source code freely available. Uptime Kuma is the most popular, combining monitoring and a status page in one self-hosted app. You get full control and no per-page fee, and you take on hosting, updates and the job of keeping the page independent of the service it reports on.
How much does status page software cost?
It ranges from free for open-source or a single hosted page, to hundreds of dollars a month for incumbent tools sold per page or per subscriber. AlertPing takes a different route: hosted status pages are included in the plan, one on Starter at $19, five on Team at $59 and twenty on Business, so the page comes bundled with the monitoring that drives it rather than priced as an add-on.
A status page that stays up when you do not
Hosted off your infrastructure, updated automatically from 30-second checks across three regions, with SMS in every plan. Included from $19/mo.