Public Status Pages
Status Pages let you create a public page showing your services’ health. Users can check status without registration.
Features
A public address, open to anyone
Each status page gets its own address, like pingzen.dev/status/your-slug. It needs no registration and no login — the link works for whoever you give it to. If you change the slug later, the old address stops opening, so update the links you have shared.
You pick which monitors appear
Add only the monitors whose status you want to show publicly. Everything else stays visible to you alone.
Uptime and SLA
Uptime percentages over 24 hours, 7, 30 and 90 days, plus a per-monitor uptime bar. The day boundaries in that bar follow the display timezone below.
It updates itself
The status changes on the page without a reload, so a tab left open keeps showing the truth.
Your title, your description, your theme
Set the title and the description, and pick a light or a dark theme for the page.
Search engines, on your terms
The allow_indexing switch decides whether the page can turn up in search results. Turn it off when the page is only meant for the people you sent the link to.
Page language
English or Russian: the language your texts are written in. It sets the title, the description and the link preview that messengers (Telegram, VK, Slack) and search engines show for the page; without a description of your own, the preview gets a short standard one in this language. A new page starts in your interface language.
Visitors switch the page between RU and EN at the top. The switch changes the interface — statuses, headings, dates — while your title, description and monitor names stay as written. The choice is remembered for the next status page the visitor opens. Without a choice, the page opens in the visitor's language only when it has texts in that language, otherwise in the page language; your texts are in one language, so for now that is the page language. To share the page in the other language, add ?lang=en or ?lang=ru to the link, for example pingzen.dev/status/your-slug?lang=en. The SLA report downloads in the language the page is shown in.
Display timezone
Choose how times are shown to visitors. Auto (the default) renders every timestamp in each visitor's own browser timezone — best for a global audience. Pinning a specific IANA timezone (for example Europe/Moscow) shows every visitor the same time, with a label in the page footer (Times shown in Europe/Moscow (MSK)). See Timezones for the full model.
How to Create
- Go to “Status Pages” in the sidebar
- Click “Create Status Page”
- Enter a title and unique slug (URL path)
- Select monitors to display
- Save and copy the public URL
Report Link and Branding
Report a problem link (every plan). Put your own support channel on the page: an https:// address (a Telegram chat, a help desk) or a mailto: address. The button names what it opens: Telegram, email or a plain link. Leave the field empty and the page shows no button at all.
Back link. The link back to the app above the page title appears only to a visitor signed in to PingZen. Anonymous visitors do not see it.
Branding (Pro, Business and Enterprise plans):
- Hide PingZen: a white-label page. No “Powered by PingZen” at the bottom, and no PingZen in the browser tab title, in the site name of link previews or in the credit line of the SLA report. The page address stays
pingzen.dev/status/..., so previews and the report still show it. A link preview then shows your logo, or no image when there is no logo or it is an SVG. - Header links: up to 5 quick links (text up to 40 characters, an
https://ormailto:address) in a bar at the top of the page, with your logo on the left. - Brand color: the background of that bar, as
#rrggbb. The text on it turns black or white, whichever reads better. Status colors never change.
On the Free plan the branding block is locked. When a plan ends, the page goes back to PingZen branding; the saved settings work again once the plan allows them.
Incidents on the Page
An incident PingZen opens by itself reads Detected automatically until someone on your team acts on it: acknowledges it (visitors then see Team investigating), posts an update, sets the status to Identified or Monitoring, changes the severity, or edits the title. After that, while the severity is still the one PingZen set, it shows Auto in the severity’s place. The title names the service the way this page does.
- Recovered: the checks saw the service come back. The line says when, and how long it was down.
- Closed: PingZen closed it without seeing a recovery. The monitor was paused, deleted or switched to another check type, its statistics were reset, or the incident was closed automatically after 7 days.
- Resolved: a person closed it.
While no one has named the cause, the card shows a likely cause as one broad category (“TLS connection cut”, “DNS problem”, “Server error” and so on). It never names a particular network, provider or checker, nor a filtering method: “TLS connection cut” says where the connection broke, not who broke it, and “No connection” cannot tell an IP block from a host that is down. “Blocked by the internet provider” shows only when the check it comes from carries its own evidence: a block page or its address, or the site’s name dropped while the same server answered without it; or when that check’s own checker found such evidence earlier in the same outage and the check stopped at the same step (see how PingZen tells a block from an outage). While the incident is open, the cause follows the latest failed check, read that way, and says when it ran (“latest check at 14:05”); that check’s error is the last line of the card, in the page’s language, and its own row in the timeline, above the error the incident opened with. A click or Enter on the last line shows the timeline and the full error texts as the checker wrote them.
SLA Reports (PDF)
Every public status page has a Download SLA report button in the header. Any visitor — no account required — gets a PDF snapshot of the page, ready to attach to an SLA review, a postmortem, or a client email.
The report covers the last 90 days and contains only what the public page already shows — no monitor IDs, internal error details, or latency internals leak into it:
- Current status and overall 90-day uptime across actively monitored services
- Per-service uptime for the 24h / 7d / 30d / 90d windows
- A 90-day daily uptime strip for every monitor
- Incident history (the 50 most recent) and scheduled maintenance windows
Numbers in the PDF match the page exactly — both are built from the same data snapshot:
- Timestamps follow the page’s display timezone setting.
- Language follows the page as the visitor sees it: the RU / EN switch or the
?lang=link, else the page language. - Paused monitors are listed as
PausedwithN/Ain windows that have no data, and are excluded from the overall uptime average. - Partial (regional) outages earn half uptime credit — the same rule the SLA formula uses everywhere else in PingZen.
- The report is generated on the fly, so it always reflects the current state of the page. Unicode content (Cyrillic titles, monitor names) is fully supported.
No setup is needed — the button appears on every public status page automatically.
Sharing
Share your status page URL with users via:
- A link in your website footer
- Email notifications about maintenance
- Social media
- Internal documentation
- The downloadable SLA report (PDF) for formal reviews
Status Pages API
Manage status pages via REST API.
List status pages
Create status page
Update status page
Delete status page
Add monitors to page
Download the SLA report PDF (public, no authentication). ?lang=en or ?lang=ru picks its language; the page language by default