Status pages
Publish a public page so customers always know the current state.
A status page is the customer-facing side of your monitoring — a single place that answers "is it just me, or is the service down?" without anyone having to open a ticket.
Create a status page
Start a page
Give it a name and description. You can run multiple pages — for different products, regions or audiences.
Add components
Build the page out of components — the services your customers recognize, each backed by one or more monitors.
Publish
Each page gets its own web address — yourname.watchfor.io — from the name
you choose. Share that link; the page updates itself as incidents open and
resolve.
What's on a page
- An overall status banner ("All systems operational", or the current problem).
- Each component's current state.
- A live uptime heatmap so visitors can see recent history at a glance.
- Ongoing incidents and scheduled maintenance, with updates.
- An RSS feed so people can subscribe to changes.
Auto-updating, with manual control
Components reflect their monitors automatically, but you stay in control: you can post incident updates in your own words and set a component's state manually when you need to. See Incident updates.
The public page is cached for speed and refreshes when things change — so it stays fast even under a traffic spike during an outage.