Status pages
Public service-health pages with optional auth and custom branding.
A status page is a public URL that displays the up/down state of a chosen subset of your monitors plus their recent uptime. Think of it as the read-only view of your incident state for customers and stakeholders.
Create one
Dashboard: Dashboard → Status Pages → Create.
| Field | Description |
|---|---|
| Name | Display name shown in the header. |
| Slug | URL path. [a-z0-9]([a-z0-9-]{0,58}[a-z0-9])?. Public URL becomes obzerv.xyz/status/<slug>. |
| Description | One-line tagline under the name. Optional. |
| Display style | bars (system theme), clean (light), or dark. |
| Accent color | Hex like #34C759 — matches up-status indicators. |
| Logo URL | Optional brand logo at the top. |
| Uptime display | bars, line, dots, or solid. |
API equivalent (Business required for API writes):
curl -X POST https://obzerv.xyz/api/status-pages \
-H "Authorization: Bearer $OBZERV_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"slug": "acme-status",
"name": "Acme Status",
"description": "Real-time service health",
"monitor_ids": ["<monitor-id-1>", "<monitor-id-2>"],
"accent_color": "#22C55E",
"uptime_display": "bars"
}'Visibility
| Mode | Available on | How to enable |
|---|---|---|
| Public | All plans | Default (is_public: true, no password, empty ip_allowlist). |
| Password-protected | Business+ | Set password to a non-empty string. Visitors prompted before page renders. |
| IP allowlist | Business+ | ip_allowlist: comma-separated IPs/CIDRs. Requests from other IPs get 403. |
Embeddable badge
Unprotected public status pages expose a one-line badge you can drop into a README, marketing site, or app footer — see Embed a status badge.
Public URL
https://obzerv.xyz/status/<slug>Share this hosted URL with customers or link it from your site. Public pages refresh every 30 seconds and on focus, show the last successful fetch time, and display scheduled maintenance for their selected monitors. Unknown or stale observations are shown explicitly.
Private pages require an authorized owner session. Password and IP protection also apply to the API; protected or private pages do not expose embeddable badges.
When updating a protected page through the API, omit password to keep it, send a new non-empty value to change it, or null to remove protection.
See also
- Embed a status badge —
<iframe>snippet for any page. - Regions — multi-region monitors give cleaner status data.
POST /status-pagesreference.