Status Pages Overview
Status pages are public (or private) web pages that show the real-time health and uptime history of your monitors. Share a single URL with your customers so they can check whether your services are operational without contacting support.
What is a status page?
A status page collects a selection of your monitors into a single branded page and displays:
- Overall status — an "All systems operational" / "Experiencing issues" banner derived from the current state of the assigned monitors.
- Service status — each assigned monitor grouped by its monitor group, with its current up/down state and (optionally) its latest response time.
- Uptime history — a per-day uptime grid for the last 30, 60, 90, 180, or 365 days (configurable).
- Recent incidents — the latest incidents affecting the assigned monitors, with start time and resolution duration.
Live status and uptime are read from VictoriaMetrics, so the page reflects the same data as your dashboard.
Public URL
Every status page has a unique slug and is served at:
https://statusradar.dev/status/{slug}
For example, a page with the slug acme-prod is available at https://statusradar.dev/status/acme-prod.
The public page renders without the dashboard layout and uses the theme you configure (primary color + layout). It is only reachable when the page is marked public — see below.
Public vs. private
| Setting | Behavior |
|---|---|
Public (is_public = 1) |
Anyone with the URL can view the page at /status/{slug}. This is the default. |
Private (is_public = 0) |
The public URL returns 404. The page is still visible and editable inside the dashboard, so you can prepare it before launch or keep an internal-only page. |
What you can configure
- Title and description — shown in the page header.
- Slug — the URL identifier (lowercase letters, numbers, and hyphens). Must be unique across all status pages.
- Assigned monitors — which monitors appear, grouped by their monitor group.
- Theme — a primary brand color and a layout (modern / classic / compact, each in light or dark).
- Uptime history window — 30, 60, 90, 180, or 365 days.
- Language — the locale used to render the public page.
- Custom domain — serve the page from your own hostname (plan-gated).
Plan limits
The number of status pages you can create is capped by your subscription plan (max_status_pages). When you reach the limit, page creation is blocked with a prompt to upgrade. Custom domains are also plan-gated and only available on plans where the feature is enabled.
Permissions
Status pages belong to a team. Within a team:
- Viewing the dashboard list requires being signed in.
- Creating, editing, deleting, and assigning monitors requires the
manage_status_pagesteam permission (owners, admins, and members; viewers are read-only). - Creating a page requires a verified email address.
See Teams for role details.
API access
Status page data is available over the API:
- Public:
GET /api/status/{slug}— read the live status of a public page (no auth). - Authenticated:
GET /api/status-pagesandGET /api/status-pages/{id}— list and inspect your team's status pages (session or Bearer token).
Next Steps
- Setup - Create a page and assign monitors
- Customization - Theming and layout options
- Custom Domains - Serve from your own hostname
- Uptime History - Configure the history window