When your SaaS goes down, users don't know whether it's their internet, their account, or your infrastructure. They guess, they refresh, they email support, or worse, they just churn.
A public status page fixes this. It gives users one URL to check. It shows them that you know about the problem and you're on it. And it reduces support volume during incidents because users aren't emailing you in the dark.
Here's how to set one up.
What a status page shows
A good status page shows:
- Current status, is the service operational right now?
- Uptime history, a visual timeline of past uptime and incidents
- Active incidents, what's wrong and what you're doing about it
- Past incidents, a record of previous outages for transparency
You don't need to build this yourself. Tools like PingVault generate status pages directly from your monitor data, so the uptime history is always accurate and updated automatically.
Step 1: Create your monitors
Before setting up a status page, you need monitors for the services you want to show. These are the URLs PingVault will check, your homepage, API, dashboard, auth endpoint, etc.
Add each one as a separate monitor. This matters because your status page can show per-service status ("API, Operational", "Dashboard, Degraded Performance") rather than one vague "system status".
Step 2: Create the status page
In PingVault, go to Status Pages → New Status Page. Give it a name (this will be shown to users), add the monitors you want to display, and save.
PingVault will give you a hosted URL like yourname.pingvault.live that's immediately live.
Step 3: Point your own domain to it
Having your status page at status.yourdomain.com looks far more professional than a generic URL, and it keeps users in your brand during incidents, which is when trust matters most.
To set this up:
- In PingVault, go to your status page settings and enter your custom domain (e.g.
status.yourapp.com) - In your DNS provider, add a CNAME record pointing
status.yourapp.comto the target PingVault gives you - Wait for DNS to propagate (usually 5–30 minutes)
That's it. SSL is handled automatically.
Step 4: Share the URL with your users
A status page only helps if users know where to find it. Put the link:
- In your app's footer
- In your onboarding emails
- In your support docs
- In your Twitter/X bio
When an incident happens, you can tweet "we're aware of the issue, follow status.yourapp.com for updates" and users have somewhere to go.
What to do during an incident
Your status page will automatically reflect downtime as PingVault detects it through your monitors. But you should also post manual incident updates, a short note saying what's wrong and what you're investigating.
Users don't need a full technical breakdown. They just need to know: you know about it, and you're working on it.
Something like "We're investigating elevated error rates on the API. Updates every 30 minutes." is enough to keep users calm and reduce support tickets.
Why this matters for trust
A status page is a signal that you take reliability seriously. It says you monitor your own service, you're transparent about problems, and you don't hide incidents.
For B2B SaaS especially, this matters to buyers. Procurement teams, enterprise customers, and security reviewers often ask "do you have a status page?" as a baseline check.
Setting this up takes under 10 minutes with PingVault. Start with the free plan to set up your monitors, then upgrade to Pro to unlock status pages and your custom domain.