Make a page
Open Status pages and choose New page. Pick a name for the address: your page will be at https://<name>.aperioflow.co.uk/status. Add components (for example “Website” or “Checkout”) and attach one or more of your monitors to each.
Each component has a public name that you type. The page never shows the address that is monitored or your monitor’s own name. A page stays unpublished, and answers “not found”, until you publish it.
Your plan sets how many pages you can have: 1 on Free, 3 on Solo and 5 on Team.
What visitors see
Each component shows its current status, and uptime bars for up to 90 days, and no more than your plan keeps. The page also shows incident history with updates (Investigating, Identified, Monitoring and Resolved), scheduled maintenance, and a summary in JSON at /status.json.
An incident opens by itself when a monitor fails and is confirmed. You can also write an incident yourself, from a template, and post updates until you resolve it.
Text you type into an incident is your own and is shown publicly, so do not put personal data in it. Every page says it is published by your organisation and hosted by AperioFlow, links to the Privacy Policy, and has a link to report abuse.
Pages load no code, fonts, images, analytics or widgets from anyone else, and our code sets no cookies. (Our network provider may set its own cookie for running the network, as the Cookie Notice says.)
By default a page asks search engines not to list it. You can change that with “Let search engines list this status page”.
The rules for status pages are in the Terms of Service (G8A).