Status pages

1Create the page

Status pages, create: give it a name and a slug (a-z, 0-9 and dashes, 3 to 48 characters; www, app, api, admin, status and blipit are reserved). Pages per plan: Free 1, Solo 1, Team 3, Scale 10. Only owners and admins can change this; members can see it.

2Add components

Each component is one monitor from the Uptime page. The public page shows its current state and a 90-day uptime bar built from hourly roll-ups. Heartbeat monitors have no roll-ups, so their bars show no data.

3Open an incident

Open incident and email subscribers: give it a title and a first update. Post further updates as you learn more and resolve it when done. Active incidents show a timeline at the top of the page; resolved ones stay listed for 30 days.

4Subscribers

Visitors enter an email under Subscribe to updates. They get a confirmation link that works once and expires in 48 hours; nothing is sent until they click it. Every email carries an unsubscribe link. Subscribing is rate limited per address and per IP.

Good to know

• When a monitor on a public page goes down or recovers, confirmed subscribers are emailed once per state change.
• The public page is cached and refreshed at most every 30 seconds and on every change you make in the dashboard.
• A custom domain can be saved and the editor shows the CNAME to add (to app.blipit.io), but serving the page on that domain is not switched on yet.
• Deleting a page removes its incidents and subscribers.