Guides 5 min read
How to Create a Status Page Customers Trust
A status page tells customers what is broken, what you are doing and when to check back. How to set one up, what to put on it and ready-to-use incident update templates.
ReadGlossary · Incidents and alerting
A status page is a public web page that shows whether a service and its components are working, with current incidents, planned maintenance and recent history, so users can check for themselves instead of asking support.
Status pages answer the first question in any outage, “is it just me?”, and cut support load when it is highest. Components such as website, API, checkout and email let users see what is affected; status updates say in plain words what is known and when the next update comes.
A status page should run on separate infrastructure from the service it reports on, so it stays up during the outage it describes. Status that comes from monitoring keeps it right when nobody has time to update it by hand.
Subscriptions by email, chat or webhook bring updates to people instead of making them reload the page, and announcing a maintenance window there in advance avoids surprises.
Uptimecheck status pages update themselves from your monitors, with 90 days of history per component, status updates in your own words, planned maintenance and incident reviews, in the visitor’s time zone and one of 9 languages. Visitors can subscribe by email, Slack, Microsoft Teams, Discord or webhook. A page can be password protected and carries your logo and colours.
14-day free trial · Then free on 20 monitors · No credit card
Guides 5 min read
A status page tells customers what is broken, what you are doing and when to check back. How to set one up, what to put on it and ready-to-use incident update templates.
ReadGuides 5 min read
How to tell customers about an outage: who speaks, how often, on which channel and in what words. A one-page plan, severity levels, update cadence and ready-to-use templates for status pages, email and social media.
ReadPublic for customer-facing services, so anyone can check. Password protected for internal tools or a page made for a single client.
Component status, yes: from monitoring it is right at 3 a.m. too. Incident text, no: write it yourself, since only people know the impact and what is being done.
What is affected, what users may notice, what you are doing and when the next update will come. Leave out guesses about the cause until you know.
Click around the live demo without an account, or start your trial and add your first monitor.
14-day free trial · Then free on 20 monitors · No credit card
We use Google Analytics and Microsoft Clarity to improve the site. No ads. We measure how the site is used with Google Analytics and Microsoft Clarity, to make it better. They don’t tell us who you are, and we run no ads. You can turn statistics off here, or at any time under Cookie settings at the bottom of every page. Privacy policy