Status Pages Are Live: Uptime Your Customers Can Verify
Guardr status pages are live on every paid plan: components, incidents, maintenance windows, per-component email subscribers and JSON, RSS and Atom feeds.
Most status pages share one quiet problem: they are the service reporting on itself. The company writes the page, the company updates the page and the reader has no way to check any of it. When everything is on fire, the page that matters most is the one nobody has time to update.
Guardr status pages are live today on every paid plan. They are built the other way around. Your page is generated from the same monitoring that already watches your sites. Every component shows when Guardr last checked it. Outages are confirmed from 3 independent regions before they are recorded. The uptime history on the page is the uptime history we measured - not a number somebody typed in.
Here is what shipped.
A page readers can actually verify
Every component on your page carries a live “Last checked” line, so a reader can see that something is actually looking - and how recently. Before an outage is recorded on your history, Guardr confirms it from 3 separate regions, so a single flaky network path does not become a public black mark on your record.
The history is honest about what it knows. A component monitored for 53 days shows a 90-day bar that says exactly that: “Data covers 53 of 90 days.” No pretending, no backfilled green. If your page says 100%, that number survived every check we ran.
One thing the page never does is flip your public status automatically. The evidence is independent, but the state word is yours: a component changes state only when you publish an incident. Automated pages have a habit of declaring outages during deploys and blips; a page that speaks for your business should not change its story without you.
Components, incidents and maintenance windows
A component is a public label - Website, API, Checkout - covering one or more of the sites Guardr monitors for you. Readers see the label and its state. They never see which domains sit behind it, which matters when the domains are client sites or internal names.
Incidents run on a timeline: investigating, identified, monitoring, resolved. Each update you post is a timestamped entry your readers can follow, so the page shows what you knew and when you knew it.
Maintenance windows are the part we are most pleased with. You schedule a window with a start, an end and a time zone. When the start time passes, the window moves to in progress on its own. When the end time passes, it completes on its own - and your subscribers are emailed at each step. You schedule the work once. The page runs the communication.
Times are shown in the zone you picked, with the zone named next to them, so a reader in another country never has to guess which clock a date is on.
Subscribers who choose what they hear about
A published page carries a subscribe box. A reader enters an email address and picks which components they care about - or picks none and hears about everything. A client who only depends on your API can subscribe to the API component and skip the rest.
Per-component subscriptions are the feature status page users ask for most. Elsewhere in this category they tend to sit behind plans costing hundreds of dollars a month. On Guardr they are on every plan that has pages.
The mechanics are done properly. Subscriptions are double opt-in: nothing is sent until the reader clicks a confirmation link, so a typo or a stranger entering somebody else’s address costs that person exactly nothing. Every message carries a one-click unsubscribe. The form sits behind bot protection, so your sending reputation is not spent on scripted signups. And an incident that affects the whole page reaches every subscriber - including the ones who narrowed to a single component, because somebody who asked about one part of your service still wants to know when all of it is affected.
Fast pages and three feeds
The page itself ships with zero JavaScript of our own. It is server-rendered HTML that loads fast, works with scripting disabled and stays readable on a phone during the exact moment your infrastructure is misbehaving. A status page that needs a working frontend stack to render is a status page with a single point of irony.
Every public page also comes in three machine-readable versions, at the same address with a suffix:
- JSON -
status.guardr.io/your-address.json- the page data for your own dashboards and scripts - RSS -
status.guardr.io/your-address.rss- for any feed reader - Atom -
status.guardr.io/your-address.atom- same items, same order, different standard
All three support conditional requests, so a poller that sends back the ETag gets a 304 with an empty body when nothing changed. Point a feed reader at your page and polling costs you nothing.
Private pages for the readers you choose
On Pro and Agency plans, a page can be private: reachable only at a tokenized link you share, with no accounts for your readers to create and no sign-in to manage. Hand the link to one client. Replace it any time, which cuts off every copy in circulation at once. If you run client sites, this is a status page per client without asking any client to make an account anywhere.
What you get on each plan
| Plan | Status pages | Private pages |
|---|---|---|
| Solo ($7/mo) | 1 | - |
| Starter | 1 | - |
| Pro | 3 | Yes |
| Agency | 10 | Yes |
Every page can carry up to 10 components on every plan that includes pages. Your logo and favicon go on the page at the same flat price - branding is not a higher-tier unlock here. Subscribers, feeds and maintenance automation are included everywhere - there are no per-subscriber packs and no per-page add-ons.
What the same features cost elsewhere
The status page category has a habit of gating its most useful features behind its most expensive tiers. Here is where the features above sit at the incumbents, against where they sit on Guardr. Competitor figures are list prices as of September 2026.
| What you need | Where it sits elsewhere | On Guardr |
|---|---|---|
| A private status page | Statuspage sells private pages as a separate plan ladder starting at $79/mo. Instatus gates them behind Business at $300/mo. Better Stack bills password protection as a per-page add-on. | Included on Pro at $69/mo, alongside 3 pages and 50 monitored sites |
| Subscribers who pick their components | Statuspage gates component-level subscriptions behind Business at $399/mo. | Every plan with pages, starting on Solo at $7/mo |
| Your own branding | Better Stack bills removal of its badge at $250 per page per month. Statuspage gates full customization behind Business at $399/mo. | Logo and favicon included on every plan with pages |
| Monitoring that feeds the page | Statuspage runs no monitors. You bring a separate tool and wire the two together, which is exactly where the delay between detection and communication comes from. | Built in. The page reads the same checks that already watch your sites |
None of this is a stripped-down teaser. The $7 page and the $179 page run on the same engine, show the same evidence and email the same subscribers. The plans differ in how many pages, sites and private links you get - not in how honest the page is.
Set one up in about two minutes
- Go to Dashboard → Status pages and create a page. Pick a title and an address.
- Add components and tick the monitored sites each one covers.
- Publish. Your page is live at
status.guardr.io/your-address.
If Guardr is already monitoring your sites, the history is already there - your page opens with real uptime data on day one, not an empty chart.
Create your status page → - or read the full status pages guide for components, branding, private links and everything else.
Not monitoring with Guardr yet? Start free - security scanning and uptime monitoring for your first site costs nothing. Status pages start on Solo at $7/mo.