Go-live checklist
Your status page is built. Run through this checklist before you share the URL, so the page your users discover is complete, branded, and the only source of truth from day one.
1. Get services and sections ready
The page is only useful if it shows the services your users actually care about.
- Add your services
Services pull their real-time status from your monitors. Add them from the Sections tab, and use the Gear icon to rename any service whose monitor name would confuse outsiders.
- Organize them into sections
Group services into sections, and into groups within sections, by product area, region, or team. Reorder them so the most important services come first.
- Choose the metrics to display
Each service can show an uptime graph of the past 90 days and a response time graph of the past 24 hours. Toggle them from the Gear icon on the selected service.
2. Put it on your own domain
A status page on your own domain is easier to find and easier to trust. Follow the custom domain guide.
- Configure DNS
For a subdomain like status.acme.com, create a CNAME record pointing to cname.hyperping.io. For an apex domain, create an A record pointing to our IP address.
- Publish and verify HTTPS
Enter the domain in your status page settings and hit Publish. Every status page is served over HTTPS only, with an automatic SSL certificate renewed 30 days before expiry.
- Keep the hyperping.app URL as a fallback
DNS propagation can take up to 24 hours. Your Hyperping-hosted slug (yourname.hyperping.app) is instantly available, so you can test and demo while you wait.
3. Brand it and white label it
Make the page unmistakably yours before anyone sees it. The white labeling guide covers the full setup.
- Apply your visual branding
Set your company logo (with an optional dark mode logo), favicon, accent color, font, and theme from the status page builder. Visual branding is available on all plans.
- Remove Hyperping branding
On the Business plan, hide the "Powered by Hyperping" footer and send subscriber emails from your own domain, so every touchpoint carries your brand.
- Set indexing and analytics
Decide whether search engines should find the page with the "Hide from search engines" toggle, and add your Google Analytics tag if you want traffic data. Both live in the builder's Settings tab.
4. Open subscriber notifications
Subscribers hear about incidents from you, not from Twitter. Set the channels up in the Subscribers tab.
- Pick the channels
Offer up to 4 channels: email, Slack, Microsoft Teams, and SMS. SMS requires connecting your own Twilio account, so only enable it if you use Twilio.
- Bring your existing subscribers over
Manually add email subscribers from your previous tool, up to 500 addresses at once, or use the Subscribers API. Slack, Teams and SMS subscribers must subscribe through their own channels, so invite them to re-subscribe on the new page.
5. Decide who can see it
Leave the page public, or restrict it before the URL starts circulating.
- Public page
Nothing to do. Anyone with the URL can view it, which is what most customer-facing status pages want.
- Private page
Go to Settings → Page Access and protect it with a password, Google SSO, email access codes, or SAML SSO. The private status pages guide compares the four options.
6. Announce it and switch over
The final step is making the new page the only one your users ever see.
- Import your incident history
Coming from StatusPage.io? Import your historical incidents and maintenances first, so the new page launches with your track record instead of an empty history.
- Communicate the new URL and update your links
Share the new address with your users, then update every link that pointed to the old page: your website, your emails, and your docs. Add the footer badge to your site so real-time status is one click away.
- Turn off the old status page
Once the new page is live and linked, shut the old one down. Running two pages means posting every update twice, and the stale one will eventually contradict the real one.
