What a page shows
Some cities see errors
API errors from Singapore
- Frankfurt84 ms
- Virginia61 ms
- Singaporedown
Investigating, 14:04 UTC: API requests from Singapore time out. The other cities are normal.
- The overall state, in plain words: all systems operational, some cities see errors, a partial or major outage, maintenance in progress.
- Each monitor you put on the page, in the order you choose, with a bar for each of the last 90 days and its uptime over 30 and 90 days.
- Each city's latest check, with its answer time, or that it fails.
- Open incidents and maintenance at the top, and the incidents of the last 90 days below, each with a page of its own.
The live part comes straight from the checks, so a page shows an outage as soon as the monitor is down, whether or not anyone has written about it yet.
Its address
You choose the address when you create the page: bbox.to/your-name, with 3 to 63
letters, digits and dashes. Untick Public to keep a page to yourself while you set it
up; anyone with the address can see a public one.
On the Max plan a page can also have your own domain, such as status.example.com:
add the domain in the page's settings, then the two DNS records shown there: a CNAME that points the domain at
us, and a TXT record that shows the domain is yours. The certificate is issued automatically once they are in place.
Four layouts
Globe stage
The globe leads, with each city's latency beside it; details below.
Calm
One readable column: a status banner with a small globe, then the details.
Split view
Details on the left; the globe and each city's latency pinned on the right.
Map
The world map leads, each city lit in its state, a card per city; details below.
Every layout is dark by default, and visitors can switch it to light. You can change the layout at any time; the address stays.
Incidents, updates and postmortems
When a monitor on the page goes down or becomes unstable, an incident opens on its own and shows as Detected until you post an update. It closes when the monitor is back. You can also open an incident by hand, for something the checks can't see.
Each update has a status, Investigating, Identified, Monitoring or Resolved, and a few lines for your customers. Once it is over, add a postmortem: what happened, why, and what changes. It stays on the incident's page.
Planned maintenance
Schedule a maintenance window for some monitors and the pages that show them list it a week ahead, then say "maintenance" instead of an outage while it runs. Alerts for those monitors stay quiet meanwhile. A window can start up to 90 days ahead and last up to 30 days.
Email updates for subscribers
Visitors can subscribe with their email address. They get a link to confirm first, which works for 2 days, so nobody is signed up by someone else. Once confirmed, they get an email when an incident starts, when you post an update, and when it ends. Every email has a link to unsubscribe.
Feed, JSON and badge
Every page has three more addresses, linked at its foot, for tools and other pages:
/feed.atom: an Atom feed with an entry for each incident of the last 90 days and its updates, for feed readers./summary.json: the overall state, each monitor's status and 30-day uptime, and the open incidents with their updates. The field names follow the summary.json layout many status tools read (page,status.indicator,components,incidents); a monitor with no recent checks isunknownrather than operational./badge.svg: a small "status | operational" badge for a README or a footer, in the page's current state.
Pages per plan
| Plan | Status pages | Your own domain |
|---|---|---|
| Free | 1 | No |
| Pro | 5 | No |
| Max | 20 | Yes |
Incidents, maintenance, subscribers, the feed, the JSON and the badge come with every page on every plan.
Private for your visitors
Status pages set no cookies and carry no analytics or tracking. A visitor's light or dark choice stays in their own browser. At the foot of each page is a small "Monitored by BBoxProbe" link, which you can hide on the Max plan.