A status page your customers check before they email you
Put it on your own domain in a few minutes. Incidents, maintenance windows and subscriber notifications are built in, and monitors keep the page honest while you sleep.
Free for one monitor. No card needed.
What a status page does for you
When something breaks, the first thing customers do is look for a page that says you know. If there is one, they wait. If there is not, they open a ticket, then another, then they tweet. A status page turns a hundred conversations into one you write once.
Status Bee hosts that page for you. Components show what is up and what is not, an uptime strip shows the last year at a glance, and subscribers get every update on the channel they picked. Monitors can update components and open incidents on their own, so the page is right even when nobody is at a keyboard.
Incidents in four words your customers understand
Investigating, identified, monitoring, resolved. Post an update once and it lands on the page, in inboxes and on every channel you have connected. Impact levels tell people how worried to be.
- Templates for the incidents you have written before, so the 2 am one takes a minute
- Drafts you can review before anything goes public
- A history customers can read back through, incident by incident
Tell people before you turn things off
Schedule a maintenance window with a start, an end and the components it touches. Subscribers get a reminder 24 hours and 1 hour before, and the page shows it as maintenance rather than an outage.
- Reminders you can change per window, in hours or minutes
- Start, complete or cancel from the dashboard, and the page follows
- Affected components show Maintenance, not Outage, for the duration
Subscribers pick the channel. You write it once.
Email, SMS, Slack, Discord, Telegram, Teams or a webhook. Each subscriber chooses, and each one can follow only the components they care about. You never pay more because more people signed up.
- Import an existing list, with you vouching for consent
- Destinations are masked in the dashboard, and anyone can delete themselves
- Per-channel counts so you know who hears you where
Monitors keep the page honest
Link a monitor to a component and the page updates itself. A rule can flip the component to Degraded or Outage, draft an incident for you to review, or publish one straight away and notify everyone.
- HTTPS, TCP, ping, DNS, SSL and heartbeat checks, from 30 seconds apart
- A check has to fail as many times in a row as you decide before anything happens
- When checks pass again, the incident moves to Monitoring on its own
From sign-up to a published page
Pick a template
SaaS, API, agency or blank. Rename the components to the words your customers use.
Point your domain
Add one CNAME. We issue the certificate and serve the page over HTTPS.
Connect a monitor
Link a check to each component and decide what a failure should do: change status, draft an incident, or publish one.
The checks that feed the page
Every monitor type can drive a component. These are the ones people ask about most.
Status page questions
Your first page takes about four minutes.
One monitor and a public page are free. No card needed.