Your users shouldn't have to ask you whether your service is up. And you shouldn't have to build a status page from scratch — or pay Statuspage.io prices — to give them that answer.
Today we shipped public status pages in Observare.
What it does
You create a status page from the dashboard under Tools → Status Pages. Pick which monitors to show, add your logo, choose your brand colour and theme, and it's live at a unique URL in seconds.
The page updates automatically from the monitors you already have running. No integration, no webhook glue, no separate service. Your uptime, SSL, port, and cron heartbeat monitors feed straight into the status page because they're part of the same system.
What your visitors see
A clean, branded page with three sections:
Overall status banner — All Systems Operational, Degraded Performance, or System Outage. Computed live from the individual monitors, not something you have to manually toggle.
Monitor cards grouped by type — Uptime, SSL Certificates, Port Monitors, Cron Heartbeats. Each card shows the monitor name, current status with a coloured dot, 30-day uptime percentage, and when it was last checked.
14-day incident history — grouped by date, showing what went down, when it started, when it recovered, and the total downtime. If nothing has gone wrong, your visitors see "No incidents in the last 14 days" — which is the best possible thing for a status page to say.
Branding
Every status page has its own visual identity:
- Page title and optional logo (direct URL to your image, displayed at 64px height)
- Accent colour — applied to the status dots and the overall banner
- Dark or light theme — dark matches the Observare aesthetic; light is cleaner for brands that use white backgrounds
- Custom background colour — override the theme default if your brand has a specific background. Cards auto-adjust to maintain contrast.
All changes take effect immediately. No deploy, no cache purge, no waiting.
Password protection
Some teams need a status page that's visible to customers but not the general public. Toggle password protection on, set a password, and visitors see a gate instead of the status page. Correct password sets a 24-hour cookie so they don't have to re-enter it every visit.
The technical choice: server-rendered HTML
The public status page is not a React app. It's server-rendered HTML with inline CSS — no external stylesheets, no JavaScript framework, no client-side bundle. It loads instantly on any browser, caches for 30 seconds, and doesn't require the visitor to download your monitoring dashboard just to check if your API is up.
This was a deliberate choice. A status page is the one part of your infrastructure that absolutely has to work when everything else is broken. The simpler it is, the more reliable it is.
JSON API
Every public status page (without password protection) also exposes a JSON API at the same URL with an prefix. Same data as the HTML page — overall status, monitors, uptime percentages, incidents — in a structured format you can consume from your own tools, Slack bots, or monitoring pipelines.
What it costs
Nothing extra. Status pages are included in the standard £5/month Observare plan alongside everything else — uptime, SSL, port, cron heartbeat monitoring, webhook logging, email, SMS, and webhook alerts. Up to 5 status pages per account.
If you're interested in trying Observare, we're in early access — reach out via the contact page and we'll get you set up.