When something breaks, customers have one question: is it just me? Without a status page they answer it by emailing support, calling the account manager or posting on social media. A status page answers it for them, and it shows that you know about the problem before they had to tell you.
Uptimecheck status pages are connected to your monitors, so the page reflects reality without anyone updating it by hand at 03:12. Read how to create a status page customers trust for structure and wording.
Everything you can configure
- Short link: share the page at app.uptimecheck.com, with your own URL alias on Professional and Business.
- Branding: your logo, colors and social links, with removable Uptimecheck branding.
- Public or private: protect a page with a password, for internal teams or a single client.
- Search engines: block indexing when the page is not meant to be found.
- Custom CSS and JS: on Professional and Business, match your design system exactly.
- QR code: generate one for printed material or office screens.
One status page per client
Agencies use status pages to stop the phone from ringing. Give every client their own branded page, connected to the monitors for their site. When the client’s shop is slow, they check the page first. Start includes 10 status pages, Professional 25 and Business 250.
See who is watching
Every status page includes analytics. During an incident you can see how many people checked the page, from which countries and cities, through which referrers and UTM campaigns, and on which devices. That tells you how big the impact really is. See status page analytics.
Part of the incident flow
A status page works best next to fast alerts. The monitor detects the failure, alerts reach the team, the status page shows customers what is affected, and a recovery notice follows when it is fixed. Weekly and monthly reports give you the uptime record to share afterwards.
What to put on your status page
- The components customers recognise: website, checkout, API, login, email delivery.
- A short, plain-language note during incidents: what is affected, what you are doing, when you will update next.
- Uptime history, so customers can see that today is the exception.
- A link back to your support channel for anything the page does not answer.
Keep component names in your customers’ language, not your infrastructure’s. “Payments” means more to a shopper than “api-gateway-eu”. Link to the page from your app footer, your help center and your incident emails so people find it when they need it.
Private pages for internal teams
Not every status page has to be public. A password-protected page with search engines blocked works well for internal tools, a single enterprise customer or a client who wants a view of their own services. Each page has its own components, branding and access settings.
Status pages with analytics are included on every plan. See status page limits on the pricing page.