The page you point at when the phone rings.
A status page is the public (or client-facing) view of your uptime. Component states flip automatically from checks — nobody has to remember to update the page at 04:13 — and you post human updates on top.
Structure
A page is made of sections (“API”, “Website”,
“Background jobs”) containing resources — monitors and scheduled jobs whose live
state renders as the component status. Arrange them via drag & drop in the editor or
PUT /status-pages/{id}/structure. Degraded shows amber,
down shows red, maintenance windows show as maintenance — the page never claims more than the
checks know.
Updates during an incident
Post updates (investigating → identified → resolved) on top of the automatic states; each one goes to subscribers by email. Updates outlive the incident as the public history of the page.
Subscribers
| Double opt-in | Visitors subscribe on the page and confirm by email — nobody gets subscribed to someone else's outages. |
| CSV import | Bring an existing subscriber list; each import can trigger (re-)confirmation. |
| Management | List, resend confirmations, remove — in the editor or via the API. |
Languages
Add translations per page — you provide the wording per language, visitors switch on the page. Useful when your customers span markets, or when your agency serves clients in three countries.
Public URL and custom domains
Every page lives under its slug on a stable up4-hosted URL with HTTPS. That URL never goes away, so links you have already handed out keep working.
You can additionally point your own hostname at a page — status.yourcompany.com.
Add the domain, create the CNAME we show you, and we verify ownership and issue the
certificate; the page reports its own state (pending_dns → provisioning
→ active) while that happens. Team includes one custom domain, Agency ten.
On pay as you go, custom domains are a wallet add-on at €2 per domain per month.
Agencies
Pages scope per client like everything else in agency mode: Lakeside's page shows Lakeside's components, full stop. White-label means your clients see your name, not ours.
Via API
Pages, structure, updates, subscribers and translations are all writable — see the
status-pages reference. The
public page itself is served at
GET /public/status/{slug} as JSON if you want to
render it into your own systems, and
status_page.update_published is available as a
webhook.