Set Up a Professional Status Page in 60 Seconds

Why you need a status page

Your users need to know when your service is down — and more importantly, what you're doing about it. A status page builds trust by showing transparency. It reduces support tickets during outages and gives your users a single place to check instead of flooding your inbox with "is it down?" emails.

Step 1: Create your account

Sign up free with GitHub or a magic link email. No credit card required. You get 1 monitor and a public status page on the free plan.

Step 2: Add your first monitor

Go to the dashboard and click Add monitor. Enter your URL — we auto-detect the hostname as the display name. Choose your monitor type:

• HTTP — for websites and API endpoints. Supports custom headers for authenticated endpoints and JSON path matching.
• PostgreSQL / MySQL — connects to your database and runs SELECT 1 to verify it's responding.
• TCP — checks if a port is open (Redis, MongoDB, custom services).
• Ping — ICMP ping to verify server reachability.

Pick your check regions (up to 10 globally on Pro) and click Create monitor. The first check runs immediately — you'll see results within seconds.

Step 3: Configure your status page

Go to Status Page in the sidebar. Set your:

• URL slug — your page lives at onepagestatus.com/s/your-slug
• Title and description — what visitors see at the top
• Monitors to display — pick which monitors appear on the page
• Uptime history — toggle the 30-day uptime bars
• Subscriber notifications — let visitors sign up for email alerts

Click save and your status page is live.

Step 4: Organise with component groups

If you have multiple services, create Component Groups(e.g. "Core Services", "Infrastructure"). Assign monitors to groups, and they'll appear as collapsible sections on your status page — just like Atlassian Statuspage, but included free on Pro.

Step 5: Set up alerts

Go to Alerts and add your notification channels:

• Email — to any address
• SMS — text message alerts to your phone
• Slack — formatted messages with incident details (Team plan)
• Webhook — POST to any URL with HMAC signature

Step 6: Optional — custom domain

On Pro, you can serve your status page from your own domain (e.g. status.yourdomain.com). Add a CNAME record pointing to cname.vercel-dns.com and configure it in your status page settings. SSL is provisioned automatically.

What happens when something goes down?

1. Our monitoring detects the failure from multiple regions (false positive prevention)
2. An incident is auto-created with the affected monitors
3. You get alerted via email, SMS, Slack, or webhook
4. Your subscribers get notified
5. The incident appears on your status page with a timeline
6. You post updates as you investigate
7. When the service recovers, the incident auto-resolves and subscribers are notified

Ready to start?