Why your status page matters
When your service goes down, users have one question: “Is it down for everyone or just me?” A status page answers that question before they message your support team.
Without a status page, every outage triggers a flood of identical messages. “Is the site down?” “I can’t log in.” “Are you having issues?” Your team spends the first 15 minutes of every incident replying to users instead of fixing the problem.
With a status page, users check the page, see you are aware of the issue, and go back to what they were doing. During an outage, a status page that shows “Investigating: Elevated API errors” converts 50 incoming support messages into zero.
What makes a good status page
A status page is not a marketing page. It is a utility. Keep it simple.
Show current status at a glance. Use clear indicators: green for operational, yellow for degraded, red for outage. Users should understand the state of your service in under 3 seconds.
Show specific services, not one generic “System Status.” “System Status: Down” is useless. “API: Degraded. Dashboard: Operational. Authentication: Operational” tells users exactly what is broken and what still works.
Update during incidents. The worst status page is one that says “All Systems Operational” during an actual outage because nobody updated it. Automate updates from your monitoring data so the page always reflects reality.
Show incident history. Users want to know if you are reliable. A history of incidents with resolution times shows you take uptime seriously. It also gives context when they experience issues. “I had trouble at 2 PM” matched with a 2 PM incident on the status page means “it was them, not me.”
Use your own domain. Status pages at status.yourcompany.com look professional. Status pages at yourcompany.pingwatchdog.com (white-label) or a third-party URL also work. Just make it easy to find and remember.
What to show
At minimum, show these services:
- Website / Dashboard: Your main web application
- API: Your primary API endpoint
- Authentication / Login: If login is separate from the main app
- Background processing: Email delivery, payment processing, data pipelines
Each service gets its own status indicator. If you run a complex product with many independent components, break things down further. Users of your API care about API status. They do not need to see that your internal admin panel is degraded.
What to say during an incident
Your status page updates should follow a simple pattern:
Investigating: “We are investigating reports of elevated API errors affecting some users.” Post this within 2 minutes of detecting the issue. You do not need to know the root cause. You just need to acknowledge you are aware.
Identified: “The issue has been identified as database connection pool exhaustion caused by a misconfigured connection limit. We are rolling out a fix.” Post this once you understand the problem. Be specific. Users trust you more when you show you know what is happening.
Monitoring: “The fix has been deployed. API latency is returning to normal. We are monitoring for stability.” Post this after the fix is live. Do not declare victory until you have confirmed recovery.
Resolved: “API functionality has been fully restored. Incident duration: 23 minutes.” Close the loop. Include the duration. Users appreciate honesty about how long it took.
Do not go silent between these updates. If the investigation is taking longer than expected, say so. “We are still investigating. We have narrowed the issue to our database tier. Next update in 15 minutes.” Silence creates uncertainty. Updates create trust.
Automating your status page
Manually updating a status page during an incident is slow and error-prone. You are already stressed. You are debugging. Updating a web page is the last thing on your mind.
The best status pages update automatically from your monitoring data. When a monitor goes down, the status page reflects it immediately. When the monitor recovers, the page updates back to green.
PingWatchdog status pages do this. You pick which monitors appear on the page. The page updates in real time as monitors go up or down. You can manually post incident updates on top of the automatic status, but the core state is always accurate.
This means your status page is never out of date during an incident. Even if you cannot post an update, the page shows the current state: which services are down, which are operational, and when the issue started.
Learn more about PingWatchdog status pages.
White-label and custom domains
A generic status page URL works. But a status page on your own domain at status.yourcompany.com with your logo and colors looks professional and builds trust.
PingWatchdog includes white-label status pages on Solo ($12/mo) and Team ($29/mo) plans. You get custom branding, custom domain support, and the option to make your status page public or private.
Where to link your status page
Make your status page easy to find:
- App footer: Link to it from every page of your application
- Support documentation: Include it in your “reporting issues” guide
- Error pages: Your 500 error page should link to the status page
- Twitter / social bios: Your support handle should reference it
- Email signatures: Your support team’s email signature can include it
- Onboarding emails: Let new users know where to check for status
The goal is that when a user experiences an issue, their first instinct is to check the status page, not to message you.
Start building trust today
A status page is one of the highest-ROI things you can set up for customer trust. It takes minutes to configure and saves hours of support time during every incident.
Set up your free status page with PingWatchdog. Free plan includes a branded status page. Paid plans add white-label branding and custom domain support.