Uptime and heartbeats
Know whether the release held with availability checks.
Custom domainWidgetAtom feedSubscribers
Branded status pages, on your own domain.
Publish one or many public status pages, each on its own custom domain, rendered by a dedicated edge app. Embed a widget, offer an Atom feed, collect confirmed subscribers, and keep the content under review — all from the monitors you already run.
status.acme.comverified
Acme Status
SubscribeAll systems operational
- APIoperational
- Dashboardoperational
- Webhooksdegraded
90-day historyAtom feed
Your status page is how reliability faces the world.
One connected loop, held on the stage this capability serves. The other stages stay as context so you can see what feeds in and what comes next.
BD
Discovery
Feedback
Product
Engineering
Release
Reliability
Evidence
Reliability
Know whether it held.
Available now
Incidents and status pages
Keep incident response and customer-facing status context together.
Web performance
Review Lighthouse report evidence against configured targets.
Test intelligence
Investigate test outcomes and flakiness evidence across runs.
Publish a whole fleet of status pages.
One organization can stand up many branded pages — a public page, a partner page, an internal page — each with its own name, slug, enabled state, and its own custom domain, all from the monitors you already run.
status pages
3 / 10- Acme Statusenabled
/acme🔒 status.acme.com
- Partner APIenabled
/partners🔒 status.partner.io
- Internal Platformdisabled
/platform-internal
A managed custom domain that verifies itself.
Request a domain and lube provisions it through Vercel, ramping through hostname verification — provisioning, pending verification, verifying, verified — and issuing TLS, so the page your customers see is yours.
status.acme.com
managed- provisioning
- pending_verification
- verifying
- verified
CNAMEcname.lube.work
TLS certificateready
Publish once, reach every channel.
Drop status into your own app.
An embeddable widget renders a summary, the component list, or incident history — off by default, gated by an origin allowlist so it only loads where you say. Prefer to pull? There is an Atom feed.
summary / components / incident_historyorigin allowlistAtom feed
widget
summarycomponentsincident_history
All systems operational
origin allowlist
- app.acme.comallowed
- docs.acme.comallowed
/feed.atomAtom feed
Only people who opted in get mail.
Email subscriptions use double opt-in — enroll, then confirm — before anything is sent, with crypto-signed tokens and a per-subscriber target of all components, a single monitor, or a group.
double opt-insigned tokensall / monitor / group
double opt-in
- enroll
- confirm
- notified
target scope
all componentsmonitorgroup
- sre@acme.comconfirmed
→ all components
- ops@partner.iopending
→ checkout-api
- status@acme.comconfirmed
→ payments group
The record customers can scroll back through.
Each component carries its own history and daily stats, so a page shows how the service has held over time — illustrative here, drawn from your real checks in the product.
per-component historydaily statsincident archive
checkout-api
live up degraded down
Nothing goes public unreviewed.
Page copy lives as immutable content revisions, scoped per locale and audience, moving through draft, approved, published, and withdrawn with a content hash and optimistic concurrency.
locale + audiencedraft → approved → published → withdrawncontent-hash
revision lifecycle
- draft
- approved
- published
- withdrawn
- en · publicpublished
sha256:9f21…c4
- fr · publicapproved
sha256:1a08…7e
- en · access_tokendraft
sha256:b7dd…20
A dedicated renderer that never hides how current it is.
Public pages are served by a separate edge app that reads from versioned snapshots with cache headers — and every response is stamped with a data-freshness signal (fresh, stale, or unknown), a last-known flag, and a reason code when live data lags.
- monitors
- snapshot
- edge app
- public
data freshness
freshstaleunknown
public reads
/:slug/history/daily-stats/incidents/:id/feed.atom
versioned snapshotsETag · s-maxage · 304
One view for domains, quota, and snapshot health.
A delivery overview shows how many bound domains are healthy, per-scope quota against your limits, snapshot health (ready versus invalidated, stored bytes, pending invalidations), and the managed-domain outbox — the enterprise plumbing, made legible.
delivery overview
3/3 domains healthyquota
- organization3 / 10
- custom domains2 / 5
12
snapshots ready
1
invalidated
18.4 MB
stored
0
pending invalidations
managed-domain outbox
pending 0leased 1failed 0
What this is not
Custom CSS is a distinct, policy-gated control — not a skin or theme picker. There is no built-in visitor or traffic analytics on the public page. And no number here is a measured availability figure: the histories are illustrative, and the real page renders from the checks your monitors run.
Enterprise-grade, quietly.
A dedicated edge renderer with snapshot caching sits behind every public page, and each of these is a real, first-class control.
Reach
How people follow along.
custom domainembeddable widgetAtom feedemail subscribers
States
Everything moves through a lifecycle.
provisioningpending_verificationverifyingverifiedpending → confirmedfresh / stale / unknown
Governance
Reviewed before it ships.
draftapprovedpublishedwithdrawnlocale + audience
Delivery
How it reaches the edge.
edge rendererversioned snapshotsfreshness signalquota + outboxAtom + 304
The signals behind the page.
Put your status where everyone can see it.
Start free
Publish a page from the monitors you already run.