Uptime monitoring + status pages

Know before your customers do.

Status Bee checks your sites, APIs and certificates, opens the incident when something fails, and keeps a status page your customers can trust.

Free for one monitor, for as long as you like. No card needed.

All systems operational99.98%
api.tidepool.io60 days
  • Web app182 ms
  • Checkout API240 ms
  • Webhook deliveryDegraded
Checking every 30s6 regions
6
Monitor types
30s
Fastest check
7
Alert channels
13
Webhook events
What you get

Everything a small team needs to look like a big one.

The checks, the alerts, the incidents and the page your customers read, in one tool.

01

Add a monitor

Paste a URL. Pick an interval and what counts as healthy: status code, response time, or text in the body.

02

Build the page

Group monitors into components your customers recognise, write the headline, set the domain and decide who can see it.

03

Let it run

When a check fails, Status Bee raises the incident, updates the page, and tells everyone who subscribed.

Status page

The page your customers refresh

Up to a year of history, component by component. Subscribers choose how they hear from you. You write the update once.

  • Custom domain over HTTPS, your logo and colors
  • Audience-specific pages, so each customer sees their own services
  • Scheduled maintenance announced before it starts
Tidepool statusUpdated 12s ago
All systems operational
Web app99.99%
Checkout API99.94%
Webhook delivery99.71%
45 days agoToday
Get told when something changes
Monitors

The console you check at 2am

Every check and every response time in one list. Pause a monitor, change its interval, or open an incident without leaving the screen.

  • Assertions on status code, response time and body text
  • Intervals from 30 seconds to 24 hours
  • Roles from owner down to viewer, so the new hire can look but not publish
Monitors4 up · 1 degraded
  • tidepool.io
    HTTPS · every 30s
    182 ms
  • hooks.tidepool.io
    HTTPS · every 30s
    2 410 ms
  • db.tidepool.io:5432
    TCP · every 1 min
    41 ms
  • Nightly export
    Heartbeat · every 24 h
    3 h ago
Incidents

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.

  • Saved templates for the incidents you have written before
  • Impact levels from minor to critical, shown on the page
  • A full history your customers can read back through
Elevated webhook latencyResolved
  1. Resolved · 14:52

    Delivery is back to normal. The backlog has drained and every queued webhook has been sent.

  2. Monitoring · 14:21

    We have added delivery workers and are watching the queue.

  3. Identified · 13:58

    A slow database migration is holding up the webhook queue.

  4. Investigating · 13:44

    Webhook delivery is slower than usual. We are looking into it.

Notifications

Tell people where they already are

Seven channels for subscribers, and outbound webhooks on thirteen event types, from monitor.down to page.published.

Email
SMS
Slack
Discord
Telegram
Teams
Webhook
REST API

Questions people ask first

Your site is up. Prove it.

One monitor and a status page, free. No card needed.

Create your status page