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 checks, so the page reflects reality without anyone updating it by hand at 03:12. See the example status page of Nordhem, a made-up shop, and read how to create a status page customers trust for structure and wording.
Components from real checks
Pick the monitors visitors should see and give them friendly names; their addresses are never shown. Components with the same group name, such as “Storefront”, fold into one row with the worst status, so visitors see the big picture first. A third-party service such as Klarna can be a component too, so customers see that a payment problem is not yours.
Updates, subscribers and maintenance
- Status updates in your own words: investigating, identified, monitoring, resolved or notice, per component, with a ready-made first draft for each stage. Mark each affected component as Degraded performance, Partial outage or Major outage. The page shows the worse of your impact and what the checks find, so a confirmed outage can’t be hidden behind a milder word.
- Subscribers by email with double opt-in, or by Slack, Microsoft Teams, Discord or webhook, for the whole page or chosen components. Only those who follow the affected components are notified.
- Maintenance shown in advance and emailed to subscribers, with a reminder before each window when it repeats. Change a window or a series later, and subscribers who were already told get the new time.
- Incident reviews: what happened, why and what changes, shown under the incident if you choose.
Everything you can configure
- Address: every page lives at app.uptimecheck.com/s/ followed by its name, plus a short code on Start, such as /s/yourcompany-k3x9. On Professional and Business you choose the exact name, such as app.uptimecheck.com/s/yourcompany.
- Branding: your logo, accent color and a light, dark or automatic theme, with removable Uptimecheck branding on every paid plan.
- Languages: English, Swedish, Danish, Norwegian, Finnish, German, French, Spanish and Dutch, with times in UTC so every visitor reads the same clock.
- Custom CSS: on Professional and Business, match your design system exactly.
- Access: protect a page with a password, or hide it from search engines.
- Embeds: a status widget for your website, an SVG badge, a JSON summary and an Atom feed, plus a QR code for printed material or office screens. The JSON summary uses Atlassian Statuspage’s format, with the same component statuses and incident impact, so tools that read Statuspage can read your page.
- Import: move from Atlassian Statuspage with components, incident history, upcoming maintenance and confirmed email subscribers.
One status page per client
Agencies use status pages to stop the phone from ringing. Give every client their own 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 counts its visits by country, referrer and device, without cookies and without storing IP addresses. During an incident 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 confirms the failure, alerts reach the team, the status page shows customers what is affected, subscribers hear about it, and a recovery follows when it is fixed. Incident management keeps the timeline and the review in one place.
What to put on your status page
- The components customers recognize: 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, or add the status widget, 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 hidden from search engines 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, subscribers and analytics are included on every plan. Plans start at €9 per month billed yearly or €12 billed monthly, excl. VAT; see status page limits on the pricing page, or start a 14-day free trial without a card.