Status pages
A status pagethat keeps itself up to date.
Every account gets a public status page at its own address. It reads from the same checks that alert you, so it is right without anybody remembering to change it.
What customers see
Working or not, at a glance
Each node you choose shows as working or down, with 60 days of history as a row of bars. Customers can read it without signing in.
You pick which nodes appear, so the public page shows your services and not your internals.
- An address of its own
- 60 days of history for each node
- You choose which nodes appear
- No sign-in needed to read it
- Fits a phone screen
- Your own messages
- Updates with a time on each
- Four clear stages to resolved
- Resolved messages stay for a week
- Recent outages listed for you
When something is wrong
Say what is happening, in your own words
Publish a message and post updates as you go: investigating, cause found, watching the fix, resolved. Each update carries its time.
It saves the support inbox from the same question two hundred times.
Fed by real checks
The page and the pager agree
The status page is driven by the nodes that watch your websites, APIs, servers and scheduled jobs. When a check fails twice, the page shows it.
It comes with every plan, at no extra cost.
- Driven by your live checks
- Website, API, port, DNS and heartbeat nodes
- Browser flows on Standard and Plus
- Included in every plan
- Nothing else to host
Questions
Is the status page included?
Yes. Every plan has one, at no extra cost.
Does it update by itself?
Yes. It reads from your checks. When a node goes down or comes back, the page changes with it.
Can I write my own incident updates?
Yes. Publish a message and add updates as you go: investigating, cause found, watching the fix, resolved.
Can I choose what is shown?
Yes. Each node has a switch for whether it appears on the public page.
Also in every account