Skip to content
StatusCheck

Find out your site is down before your customers tell you.

We check your sites, APIs and cron jobs from 18 regions on four continents. Before anyone gets woken up, a second region has to agree it is really down.

Early access opens in batches. No spam, one email when it's your turn.

  • Free plan, no card needed
  • Every limit written down
  • Cancel any time
Up

API Gateway

https://api.acme.com/health

Uptime, 30 days
99.98%
p95, 24 hours
142 ms
Checks run
25,920
Times we paged you
0
Live 07:57:39 UTC
  • SFO

    138 ms

  • SJC

    141 ms

  • IAD

    104 ms

  • NYC

    112 ms

  • YYZ

    119 ms

  • GRU

    186 ms

  • LON

    96 ms

  • PAR

    92 ms

  • AMS

    90 ms

  • FRA

    88 ms

  • BAH

    162 ms

  • CPT

    221 ms

  • BOM

    178 ms

  • BLR

    184 ms

  • SIN

    214 ms

  • ICN

    198 ms

  • TYO

    205 ms

  • SYD

    241 ms

Three jobs, and you need all three.

Knowing something broke is not much use on its own. You need the right person told, and your customers told, without you writing anything at 3 a.m.

Notice it, wherever it broke.

Pages, APIs, ports, DNS records, certificates and the cron jobs nobody watches until the backup silently stops. One check every 30 seconds, from up to 18 places at once.

Network monitors

4 up · 1 degraded
  • TCP db-primary.acme.internal:5432 12 ms Up
  • DNS acme.com · A 31 ms Up
  • ICMP edge-01.acme.com 148 ms Degraded
  • TCP smtp.acme.com:587 44 ms Up
  • DNS acme.com · MX 28 ms Up

Wake exactly one person, once.

The alert goes to whoever is actually on call, with what failed and where already in it. No answer in ten minutes and it moves to the next person. Nobody else gets touched, and a flapping monitor does not become forty messages.

Escalation policy · Core platform

3 steps
  1. On-call engineer

    SMS + push

    delivered

    Wait 5 min, then

  2. On-call engineer

    Phone call

    delivered

    Wait 5 min, then

  3. 3

    Engineering lead

    Phone call

    queued

Acknowledged by Mira from the phone call · escalation stopped

Tell your customers before they ask.

A status page on your own domain, with your logo and not ours, that updates itself from the same confirmed failure that raised the alert. Subscribers hear about it without anyone writing a post.

status.acme.com
A Acme
Subscribe

Partial degradation

Checkout is slower than usual. Investigating · updated 4 min ago

  • API
    99.98% Up
  • Web app
    100% Up
  • Checkout
    99.71% Degraded
  • Email delivery
    99.95% Up
90 days ago Today

Single sign-on, an audit log, scoped API keys and encrypted secrets are on the plans that need them, so the security review does not become a separate negotiation.

See all eight products

The same team, the same monitors, three very different bills.

Take 3 people on call, 40 monitors, and one status page on your own domain without somebody else's logo on it. Here is what that costs, at each vendor's own list prices.

Better Stack

3 responder licenses, 50 extra monitors, and white-label on 1 page

$316 /mo

Statuspage and Pingdom

Hobby for the page and 50 checks for the monitoring. Two tools, connected by you

$101 /mo

StatusCheck Team

3 people, 40 monitors and the white-labeled page all fit inside the Team plan, with on-call escalation and incident timelines in the same subscription. Extra teammates are $8 rather than $29.

$16 /mo

Both columns include seats. List prices billed yearly, taken from Better Stack, Statuspage and Pingdom, checked on September 4, 2026. Prices change. If one of these is out of date, tell us and we will correct it the same day.

Price it for your team

What happens when a check fails.

Four steps, and nothing in between that can raise a false alarm.

  1. 01

    Check

    from up to 18 places

    Every monitor runs on its own schedule, from the places you pick. Each check times every stage separately, so a slow page tells you whether it was the DNS lookup, the connection, the certificate or your own server.

  2. 02

    Confirm

    a second region agrees

    One region failing is a data point. A second region failing is an incident. Nothing is sent until two independent paths agree, which is the whole difference between an alert and a false alarm.

  3. 03

    Page

    and only that person

    The incident opens with the facts already filled in. The on-call is paged, and if they do not acknowledge it, the next person is. No storms, no duplicates.

  4. 04

    Tell

    without writing a post

    Your status page updates itself and your subscribers get an email, both from the same confirmed failure. You do not retype anything. When it recovers, that goes out too.

Your site can be fast in London and slow in Sydney.

Choose the places your customers actually are, and check from all of them. Every result says which region it came from, so when something is slow you know whether it is your server or the distance.

San Francisco N. California N. Virginia New York City Toronto São Paulo London Paris Amsterdam Frankfurt Bahrain Cape Town Mumbai Bangalore Singapore Seoul Tokyo Sydney San Francisco New York N. Virginia Toronto São Paulo London Frankfurt Bahrain Cape Town Mumbai Singapore Seoul Tokyo Sydney

Americas 6

  • San Francisco US
  • N. California US
  • N. Virginia US
  • New York City US
  • Toronto CA
  • São Paulo BR

Europe 4

  • London GB
  • Paris FR
  • Amsterdam NL
  • Frankfurt DE

Asia-Pacific 6

  • Mumbai IN
  • Bangalore IN
  • Singapore SG
  • Seoul KR
  • Tokyo JP
  • Sydney AU

Middle East & Africa 2

  • Bahrain BH
  • Cape Town ZA

Why we built it this way.

We built this for the version of you that is awake at 3 a.m., holding a phone, trying to figure out in one look whether this is real and what to do about it. Everything else follows from that.

  • It stays quiet

    Nothing flashes, buzzes or turns red for effect. If your phone goes off, something is genuinely wrong, which is the only way an alert keeps working on the fiftieth week.

  • It shows its work

    Every check keeps what it saw and where it saw it from, so you can go back and ask why it decided your site was down, and get an answer.

  • The bill has no surprises

    Every limit is written on the pricing page rather than discovered when you hit it, and going slightly over one costs a few dollars instead of a forced upgrade.

Four plans, and no surprises in any of them.

Pick one by how much you monitor and how many of you there are. Every limit is written on the pricing page, and if you go slightly over one you can buy a little more instead of jumping a plan.

Free

For side projects and trying things out.

$0/mo

Free forever

  • 10 monitors at 5-minute checks
  • 3 regions per monitor
  • 1 person
  • 1 status page on statuscheck.io
See full pricing

Solo

For one person running one product.

$7.50/mo

$90 a year, two months free

  • 20 monitors at 60-second checks
  • 5 regions per monitor
  • 1 person, extra teammates $8 each
  • 3 status pages with custom domains
See full pricing

Team

Most popular

For teams with an on-call rotation.

$15.83/mo

$190 a year, two months free

  • 50 monitors at 30-second checks
  • All 18 regions per monitor
  • 3 people included, then $8 each
  • On-call schedules and escalation
See full pricing

Business

For companies with SLAs to keep.

$40.83/mo

$490 a year, two months free

  • 300 monitors at 30-second checks
  • 10 people included, then $8 each
  • Unlimited status pages, including private ones
  • SAML single sign-on and an audit log
See full pricing

Questions people ask.

Anything else? Email us and a person replies.

support@statuscheck.io
What does StatusCheck monitor?
Websites and APIs over HTTP with status, content, and header assertions; open ports over TCP; DNS records against the resolver you choose; hosts over ICMP; TLS certificates for validity, chain, and expiry; and cron jobs or background workers through heartbeat monitors that alert when a job fails to check in.
How does StatusCheck avoid false alarms?
Every monitor runs from the regions you choose, and a failure has to be confirmed from a second region before the monitor is marked down and anyone is paged. One region’s network blip stays a data point, not a 3 a.m. phone call.
Where are the probe regions?
Eighteen regions across the Americas, Europe, Asia-Pacific, and the Middle East and Africa. San Francisco to São Paulo, London to Cape Town, Mumbai to Sydney. Every result is stamped with the region it actually ran from.
How many people can I add?
One on Free and Solo, three on Team, ten on Business. After that a teammate is $8 a month, and an alert-only seat, for somebody who needs to be paged but never opens the dashboard, is $2. We keep them cheap so nobody gets left off the on-call schedule to save money.
Is white-label an extra?
No, but it starts on the Team plan at $19 a month rather than the cheapest one. That covers removing “Powered by StatusCheck”, your own logo, and subscriber email from your own domain. A custom domain with automatic TLS starts a plan lower, on Solo at $9.
When can I use it?
StatusCheck is in early access. Join the waitlist and we’ll invite teams in small batches so we can onboard each one properly. Early-access teams keep launch pricing for at least a year after general availability.

Get on the list.

We are inviting teams in small batches. Join the waitlist and keep launch pricing for a year after general availability.

Early access opens in batches. No spam, one email when it's your turn.