Status pages
A public page your customers read for themselves. Each tracked row carries its uptime strip and response time, and a mail, certificate or domain row a day by day health strip. Incidents you write sit beside the ones the checks raise, with planned maintenance, a feed, a JSON any status reader speaks and a badge for the README.
Included on every plan.
| What breaks | hostnag |
|---|---|
| A host goes downwebsite, API, VPN, mail, gateway | Yes |
| A certificate expiresdays-before thresholds, daily inside the last window | Yes |
On the board
The page as a visitor sees it, over sample data: hover a cell. The badges beneath are the SVGs the page serves.Degraded performance
Updated just nowThe storefront, checkout and the services behind them.
Monitors
Last 24 hours, UTC- Up
- Blip
- Down
- No runs
- Healthy
- Needs attention
- At risk
- Not checked
- StorefrontUp99.98%00:0006:0012:0018:00
- CheckoutUp99.91%00:0006:0012:0018:00
Behind the scenes
3 monitors- Card payments (vendor)Up99.72%00:0006:0012:0018:00
- Storefront certificateExpiring soon11d left
- MailHealthy22/ 24 h healthy00:0006:0012:0018:00
Incidents
- Mon 28 SeptDownCheckoutRaised28 Sept, 08:00Acked28 Sept, 08:04Cleared28 Sept, 08:05after5 minResolvedCard payments slow at checkoutMinor impactOpened28 Sept, 02:00Resolved28 Sept, 03:00after1 hCheckout, Card payments (vendor)
- Resolved28 Sept, 03:00Response times are back to normal and every queued payment went through.
DownCard payments (vendor)Raised28 Sept, 02:00Cleared28 Sept, 03:00after1 h - Sun 27 SeptNo incidents
- Sat 26 SeptNo incidents
- Fri 25 SeptNo incidents
- Thu 24 SeptNo incidents
- Wed 23 SeptNo incidents
- Tue 22 SeptNo incidents
Planned maintenance
- 01 Oct 2026, 02:00for1 h 30 minSundaysEurope/London · Database maintenance
Monitored by hostnag
/status/sample/badge.svg/status/sample/m/p1/badge.svg/status/sample/m/p2/badge.svg/status/sample/m/p3/badge.svg/status/sample/m/p4/badge.svg/status/sample/m/p5/badge.svg
How it works
- 01
Publish a page for a group
One page per group, at hostnag.com/status/<slug>: 1 on Free, 10 on Pro, as many as you like on Business. Pick which monitors it shows, the name each wears in public (each row in the editor still names the monitor behind it, with a reset to its own name) and the group or sub-group it sits under, or let the page mirror the zone's own sub-zones; a target or an error string never appears. Every page in the organization is listed in one Status pages room.
- 02
Show uptime, health and where it was seen from
Each tracked row carries its 30 day figure and a typical response time, and, switched on, a cell per hour or day coloured up, blip or down; its p95 chart opens with a click on the row, or stays open, or never shows, as you choose. A row that is down says where: "from Frankfurt and Sydney, 2 of 3", or "from inside" when a Beacon in your own network saw it. A certificate or domain row draws its runway, and a mail, certificate or domain row a health strip of its own: each day Healthy, Needs attention or At risk, with "29 / 30 d healthy" beside it, never the findings themselves.
- 03
Write an incident, or let the checks raise one
Open an incident with a title, an impact and the rows it touches, walk it through Investigating, Identified, Monitoring and Resolved with a timestamped update at each step, and write the postmortem once it is over. Each step mails the subscribers. A deploy pipeline can post the same through one token URL. The episodes the checks confirm on their own are listed beside them, with when they were raised, acknowledged and cleared.
- 04
Maintenance, subscribers, feed and JSON
A maintenance window you schedule is listed ahead of time, holds the page at Planned maintenance while it runs, and is mailed to subscribers a day ahead and again when it starts. Every page has an Atom feed of its incidents and a summary.json in the shape Statuspage made standard, so any status reader, hostnag's own vendor watch included, reads a hostnag page as it would any other.
- 05
Make it yours
Your logo, alone in the header or beside the page's name, a light or dark enamel, one accent colour, a home link and a support link, a line of your own at the foot, a switch to keep the page out of search engines, and, on Pro and Business, a passphrase that keeps the whole page private. The layout is yours too: a headline band tinted by how things stand or a plain card, groups as cards of their own or nested, simple or detailed figures, the incident list day by day over 7, 14 or 30 days, and strips that start at a monitor's first check or show every day.
What you'll be told
What you get told
- HTTP
[Critical] https://www.example.com/ is down
Down from 2 of 3 locations (US East, Frankfurt). Last error: unexpected_status: 503.
- Cert
[Recovered] api.example.com certificate renewed
The certificate for api.example.com is healthy again and now expires 10 Dec 2026.
Sample alerts, rendered by the same code that writes your email and Slack messages.
Settings
- Pages
- 1 on Free, 10 on Pro, unlimited on Business
- Rows and groups
- any monitors of the zone, each under a public name of your choosing, grouped under groups and sub-groups you name or mirrored from the zone's own sub-zones
- Figures
- simple: 30 d uptime and a typical response time; detailed: uptime over 24 h and 7 d, p50 and p95; where a failure was seen from
- Response time
- the p95 chart always shown, a click away on each row, or never
- Health strips
- Mail health, Certificate and Domain rows: each day Healthy, Needs attention, At risk or Not checked, never the findings
- Layout
- headline band or plain; groups as cards or nested; incident history by day over 7, 14 or 30 days, or a plain list; strips from the first check or every day; the page name beside the logo or the logo alone
- Strips
- 24 h and 7 d by the hour, 30 d and 90 d by the day; 90 d on Pro and Business
- Incidents
- written: title, impact, affected rows, the four-step ladder, postmortem, a permalink each, twelve months of history; automatic: every confirmed episode
- Incident door
- POST /api/incident/<token> with title, status, impact, message and rows, as a query string or JSON; 20 a minute
- Subscribers
- email, double opt-in, unsubscribe in every message; down and back, every incident step, maintenance a day ahead and at the start
- Feed and JSON
- /status/<slug>/feed.atom and /status/<slug>/api/v2/summary.json, cached a minute
- Badges
- /status/<slug>/badge.svg for the page, one per monitor, SVG
- Look and links
- logo on every plan; light or dark; an accent colour; home and support links; a footer note; noindex
- Private page
- a passphrase, entered once per browser, on Pro and Business; badges, feed and JSON go off while it is set
- Branding
- the hostnag byline off on Pro and Business
- Custom domain
- coming soon: status.yourcompany.com pointed at hostnag with one CNAME
Questions
Does the page show my targets or error messages?
No. A row shows the public name you give it, its word (Up, Down, Degraded, Expiring soon and so on), where a failure was seen from by place, its figures and its strip. Hostnames, URLs, error strings and the names of your Beacons stay inside the app.
What is the difference between a written incident and an automatic one?
An automatic incident is an episode the checks confirmed. It opens itself when a row goes down and closes when it comes back, and nobody can edit it. A written incident is yours: you open it, name the rows, walk it through the four steps with a note at each, and write the postmortem. While one is open its title is the page's headline.
Can I change how the page is laid out?
Yes, from the Layout plate on the Look tab, each switch on its own: a headline band tinted green, amber or red or a plain card; groups as cards of their own or nested in one; the simple figures or the full 24 h, 7 d, p50 and p95 line; the response time chart always, a click away or never; the incident list day by day over 7, 14 or 30 days or as a plain list; strips that start at the first check or show every day; and the page name beside your logo or the logo alone.
What does a mail or certificate row show?
Its word (Healthy, Needs attention, At risk; Valid or Expiring soon for a date), a certificate's or domain's runway to expiry, and a strip of days, each graded by that day's worst finding, with how many were healthy. What a finding says stays in the app, where the same strip names it; a status page never shows it.
Can a script open an incident?
Yes. Every page has a token URL. One POST with a title, a status, an impact and a message opens an incident; the same title again updates it; status=resolved closes it. Rotate the token from the editor if it leaks.
Can other tools read my page?
Every public page serves /api/v2/summary.json in the shape Statuspage made standard, with your sections as component groups and your incidents with their updates, and an Atom feed of incidents. Paste your page into hostnag's own vendor status monitor, or into any tool that reads status pages, and it is recognised.
Can I use my own domain?
Coming soon. Pages live at hostnag.com/status/<slug> today; a custom domain such as status.yourcompany.com, pointed at hostnag with one CNAME, is next on the list. The hostnag byline at the foot can already be switched off on Pro and Business.
How fresh is the page?
It is rebuilt within a minute of a change, and at once when you post an incident update; so are the badges, the feed and the JSON.
What does a private page hide?
Everything. A private page shows its title and a passphrase field and nothing else until the passphrase is given, once per browser; its badges, feed and JSON answer 404 while it is set. Setting one needs Pro or Business; one already set stays in force on any plan.
Related
Read
Add a host. Hear about it first.
Start free