How to set up a status page

A complete guide to setting up a status page — brand it, link components to monitors, add a custom domain, and publish incidents, using Servor.

A status page is the public page that tells your users, honestly and in one place, whether your service is working. This guide takes you from nothing to a live, branded status page on your own domain — with components that update themselves and incidents your users can follow.

New to the idea? Start with what is a status page for the why. This guide is the how.

What you'll end up with

A branded public pageYour logo and color, on your own domain.Self-updating componentsLinked to monitors, so status is always current.Incidents & maintenanceA public timeline when things break or change.SubscribersUsers who get notified automatically.

Before you start

Your status page is most useful when it reflects real monitoring. If you haven't yet, create a monitor for each service you'll show — that's what lets components update automatically. See how to monitor a Linux server if you're setting up monitoring from scratch. Open your monitors in Servor

Set up your status page

Create the page

Create a status page and give it a name. Add your branding — logo and color — so it looks like part of your product, not a generic dashboard. Create a status page in Servor

Add components linked to monitors

Add components for each service you want to show (for example "Website", "API", "Database"). Link each component to the matching monitor so its status — and uptime history — updates automatically. No manual toggling.

Choose who can see it

Decide the visibility: fully public, or password-protected for an internal or customer-only audience.

Point your custom domain

Serve the page from your own domain (e.g. status.yourcompany.com) by adding a custom domain and pointing a CNAME at Servor's target. See the Cloudflare note below — it's the most common snag.

Let people subscribe

Enable subscribers so users can opt in to email or webhook updates and hear about incidents without checking the page.

Embed a status badge

Drop a status badge (an SVG) into your README, docs or site footer for an at-a-glance indicator that links back to the full page.

Cloudflare: turn the orange cloud OFF

If your DNS is on Cloudflare, the CNAME record for your status page must be DNS-only (grey cloud), not proxied (orange cloud). With the orange-cloud proxy on, certificate issuance and serving break and the page won't load correctly. Toggle the record to grey cloud and give DNS a few minutes. This is by far the most common cause of a custom domain that won't come up — see custom domain for the full walkthrough.

Keep it honest during incidents

A status page earns trust only if it's accurate when things go wrong. When there's a problem:

Report an incident with a title, status, impact and a clear message, tied to the affected page and components — report an incident in Servor.
Or let automatic incidents open from a monitor's down transition, so the page reflects reality the moment a check fails.
Post updates over time and resolve when it's fixed. The timeline is public and subscribers are notified.

Schedule maintenance in advance

Planned work doesn't have to look like an outage. Announce scheduled maintenance ahead of time so users expect the window and don't file tickets during it.

A few tips for a status page people trust

Name components in your users' language. "Checkout", not "svc-payments-3".
Link every component to a monitor. A page you have to update by hand goes stale exactly when you're busiest — during an outage.
Write updates for humans. Say what's affected, what you're doing, and when you'll next post. Even "still investigating" beats silence.
Publish the uptime history. Showing real uptime % builds more trust than a page that's always green.

Next steps

Create a status pageStart here and add your branding.Custom domainServe it from your own domain.Incidents & maintenanceCommunicate during outages and planned work.What is a status pageThe why behind the how.