Status Pages
Public status pages for the services and cron jobs you choose to show — live status, 90-day history, incident updates, and maintenance schedules, served from a durable snapshot that keeps working even when the rest of the platform is down.
Status Pages
A status page is a public page you control, showing the current health of whichever services and cron jobs you pick — nothing more, nothing you haven't explicitly added. Visitors see an overall status banner, each component's live state and 90-day uptime history, the timeline of any incident you've published, and upcoming or active maintenance windows.
Built to survive an outage
Every status page is served from a snapshot — a single document your dashboard writes every time something relevant changes (a check result, a published incident update, a maintenance window). The public page reads only that snapshot, never the live platform, so it keeps serving the last-known state even during a full platform outage. That's the entire point of the feature: it has to be the last thing standing, not the first thing to go down.
What's on the page
- Overall status banner — the worst current state across every component (down and degraded outrank an active maintenance window, which in turn outranks normal operation).
- Groups and components — pick any of your HTTP/ping/DNS/etc. services or cron/heartbeat monitors, name each one for the public, and organize them into named groups in whatever order you like. A component isn't limited to a single monitor: bundle every check that makes up the same user-facing thing — a "Website" component backed by both its HTTP check and its DNS check — and the page shows the worst of them, never double-counted.
- 90-day history strip — a densely-packed tick-per-day strip per component, rendered server-side as inline SVG so it works with no JavaScript.
- Incidents — a manually published timeline (investigating → identified → monitoring → resolved) with a full history of updates, entirely separate from your team's internal notes on the same incident, which never appear on the public page. See Publish incident updates.
- Maintenance — active and upcoming scheduled windows, shown as a banner with their title and description.
- A badge and a feed — an embeddable status badge and an RSS/JSON feed of incident and maintenance announcements — see Badges and feeds.
Availability by plan
| Plan | Public status pages | Custom domain |
|---|---|---|
| Free | 1 | — |
| Pro | 1 | — |
| Team | 1 | ✓ |
| Scale | 3 | ✓ |
| Enterprise | Unlimited | ✓ |
Custom branding — your own colors, your own logo, and hiding the UptimeHunt badge — is a separate, Enterprise-gated capability; see Branding.
Getting started
- Create a page and choose its components, then publish it.
- Customize its branding, if your plan includes it.
- Schedule maintenance windows so planned work doesn't page you or alarm visitors.
- Publish incident updates when something breaks, keeping the messy internal details off the public page.
- Embed a badge or subscribe to the feed.
Related Documentation
Alerting & Integrations
Connect UptimeHunt to notification channels including Slack, Discord, Telegram, Email, Webhook, and more. Configure alert delivery for incidents.
Create and publish a status page
Create a status page, add the services and cron jobs you want to show as components, preview it while unlisted, then publish it at its public URL.