Uptime monitoring from 15 cities on 4 continents

Know first.
Tell your customers.

BBoxProbe is an uptime monitoring and status page service. It checks your sites from cities around the world, alerts you when they go down, and gives your customers a status page.

Free for 5 monitors and 1 status page, no card. We email you a link to sign in; there is no password.

YPYour product status bbox.to/your-name

Some cities see errors

API errors from Singapore

Website100%
API99.95%
Dashboard99.99%

Investigating, 14:04 UTC: API requests from Singapore time out. The other cities are normal.

An example status page. Yours lives at bbox.to/your-name.

How alerts work

Uptime alerts only for real outages

One city's network trouble shouldn't wake you up. By default a monitor counts as down when more than half of its cities fail, and at least two when it checks from two or more.

How multi-region alerts work
  1. 1. Checked from your cities

    Each round, every city you picked for the monitor checks it: a page, a port or a domain.

  2. 2. Two rounds in a row

    A city counts only when two rounds in a row fail, so a single blip passes. You can make it one round per monitor.

  3. 3. A majority must agree

    The monitor is down when enough of its cities agree. You can set how many per monitor.

  4. 4. Then the alert

    It names the cities and what they saw, by email, Slack, Discord or webhook. Another one follows when it's back up.

API Round at 14:04 UTC
  • Frankfurt 502, twice
  • Virginia 200
  • Singapore 502, twice

2 of 3 cities failed two rounds in a row; 2 are needed. Down.

Sent by email, Slack, Discord or webhook

API is down

Frankfurt and Singapore get 502 Bad Gateway.

Down since 14:04 UTC.

We'll email again when it's back.

An example alert, in the words BBoxProbe sends.

More than up or down

  • Slow responses

    Set a response time per monitor. You get an alert when more than 20% of checks are slower than that for 30 minutes.

  • Down and up again

    A monitor that keeps going down and up sends one notice, not a stream, and another once it has been stable for 1 hour.

  • Error budget

    Set an objective, like 99.9% over 30 days. You hear when errors use up its budget too fast, even while it isn't down.

  • Certificate expiry

    For HTTPS and TLS ports: an alert 14 days before a certificate expires, and again at 7.

What you can check

Monitor websites, APIs, server ports and DNS

A monitor is one address, checked from the cities you pick. Three kinds cover most of what can go down.

How each check works
HTTP

Websites and APIs

Up when it answers with an expected status code (any 2xx unless you list others) and passes the text checks you set.

https://example.com/health

  • GET, HEAD, POST
  • Expected status codes
  • Text that must appear
  • Text that must not appear
  • Headers and body, stored encrypted
  • Redirects on or off
  • Certificate check
TCP

Server ports

For a database, a mail server or any other port. Up when it accepts a connection, and completes the TLS handshake when TLS is on.

example.com:443

  • Any host and port
  • TLS on or off
  • Certificate check
DNS

Domain names

Up when the domain resolves with at least one record of the type you pick.

example.com

  • A records
  • AAAA records
  • CNAME records
  • MX records
  • TXT records
  • NS records

A new monitor starts with Frankfurt, Virginia, and Singapore, one each in Europe, North America, and Asia, so a regional outage shows as one city down. Pick the cities you want: up to 3 on Free and all 15 on Pro and Max.

YPAPI was down Resolved
  1. Resolved 14:31 UTC

    Requests from every region succeed again. A postmortem follows.

  2. Monitoring 14:22 UTC

    A fix is out. We're watching the error rate.

  3. Identified 14:13 UTC

    A bad deploy on the Singapore edge. Rolling it back.

  4. Detected 14:04 UTC

    API is down.

statusoperational Subscribers hear about it by email
An example incident on a status page.

Status pages

A status page your customers can follow

Every plan comes with one, at bbox.to/your-name, or at your own domain on Max. It shows your monitors as the checks see them, so you don't have to update it by hand while you fix things.

Everything a status page does
  • Incidents open themselves

    A monitor that's down shows as an incident, marked Detected until you post an update.

  • Updates and postmortems

    Post Investigating, Identified, Monitoring and Resolved updates, then a postmortem.

  • Planned maintenance

    It shows as maintenance, not an outage, and alerts for those monitors stay quiet.

  • Email subscribers

    Visitors subscribe and confirm by a link; they hear when an outage starts, ends, or gets an update.

  • Feed, JSON and badge

    An Atom feed for feed readers, JSON for your own tools, and a badge for your README.

  • Four layouts

    Globe stage, Calm, Split view, and Map. No cookies and no tracking for your visitors.

Where the checks come from

15 cities on 4 continents

North America

  • California
  • Chicago
  • San Jose
  • Texas
  • Toronto
  • Virginia

Europe

  • Amsterdam
  • Frankfurt
  • London
  • Paris
  • Stockholm

Asia

  • Mumbai
  • Singapore
  • Tokyo

Oceania

  • Sydney

Start on Free

  • 5 monitors and 1 status page, no card
  • Commercial use is fine on Free too
  • Sign in with a link we email you; there is no password
  • No analytics and no tracking on the public pages
  • Paid plans through Stripe, the merchant of record