Steps
- Choose New status page. Give it a title and an address (leave the address empty for one that cannot be guessed), and choose who it is for: the whole organisation or one client. A client’s page shows only that client’s sites.
- Under Sites on this page, tick the sites and give each the name it should have on the page. Host names stay hidden unless you choose to show them.
- Switch on Published under the address, then share the address with your client. Changes show within a minute. Preview shows the page before it is public.
- Optionally write a plain-text public summary for an incident. Without one, the page says only that monitoring confirmed it from more than one region.
What visitors see
- Only confirmed incidents: two regions for page, API, port and blocklist checks, and the ping receiver for scheduled tasks. A failure that one region alone saw never appears.
- A day without data is never shown as green.
- Planned maintenance that you schedule as public is announced above the sites, and a site under maintenance says so instead of showing an outage (how).
- On plans that include it, visitors can ask for e-mail when an incident starts, is updated or ends (how).
- Regions, addresses and evidence are never shown.
- By default the page asks search engines not to index it. Search engines may still ignore that, and anyone with the address can open a published page.
Reports about a page
Every public page ends with Report this page. Anyone can use it to tell us about content they believe is illegal; a person reads every report. If we restrict a page, it goes offline at once and the page in the app shows the reason, because it cannot be published again until we lift the restriction. You can ask for a review in Help and support; your monitoring and your other pages are not affected.
Limits
Your plan sets how many status pages you can have. A page on your own domain is a separate step (can a status page use my own domain), and your own name and logo come from branding.