Automatic checks

A check every 5 minutes, around the clock

Each monitored website has its own schedule. When a check is due, our worker pool sends an HTTP GET request to your URL, follows up to 5 redirects and records the result.

  • Response time measured until the first response headers arrive
  • HTTP status code of the final response
  • Only headers and at most 64 KB of the page are read, then the connection is closed
  • A clear User-Agent (UptimeStatsBot) so you can recognise our requests in your logs

What counts as "up"?

2xx responses
Up
3xx after redirects
Up
4xx responses
Down
5xx responses
Down
Timeout, DNS, SSL or connection errors
Down

Custom expected status codes per website are planned for a future version.

Anatomy of one check: DNS lookup, TCP connection, TLS handshake, HTTP request with up to 5 redirects and evaluation of the status code. Each step can fail with a DNS failure, timeout or refused connection, SSL error, redirect error or a 4xx/5xx error; a 2xx or 3xx response means the website is up. Anatomy of one check: DNS lookup, TCP connection, TLS handshake, HTTP request with up to 5 redirects and evaluation of the status code. Each step can fail with a DNS failure, timeout or refused connection, SSL error, redirect error or a 4xx/5xx error; a 2xx or 3xx response means the website is up.
Every step of a check must succeed for the website to count as up.
Outage confirmation

Real outages, not network noise

The internet is not perfect. A single packet loss or a slow DNS answer shouldn't wake you up. When a check fails, we schedule a confirmation check about a minute later. Only if it fails again do we open an incident and send an alert.

The incident start time is the time of the first failed check, so your downtime numbers stay accurate.

  1. Check fails

    Status stays unchanged while we verify.

  2. Confirmation check

    Runs about 60 seconds later.

  3. Second failure: incident opened

    One downtime email is sent.

  4. First successful check: incident closed

    One recovery email with the total duration.

Example outage timeline: a failed check at 10:05, a confirmation check at 10:06 that opens an incident and sends one downtime email, continued checks without repeat emails, and recovery at 10:21 with one recovery email. Example outage timeline: a failed check at 10:05, a confirmation check at 10:06 that opens an incident and sends one downtime email, continued checks without repeat emails, and recovery at 10:21 with one recovery email.
Example timeline with 5-minute checks and a 1-minute confirmation check.
Example downtime alert email: My Online Store is down, reason Connection timed out, started Oct 18 at 10:05 UTC, with a View incident details button.
Example of a downtime alert email.
Email alerts

Alerts that tell you what to do next

Each downtime alert names the website, the reason for the failure and the time the outage started, with a direct link to the incident. When the website responds again you receive a recovery email with the total downtime.

  • Sent only after a confirmation check
  • One email per incident, never every 5 minutes
  • Turn downtime or recovery alerts on or off
  • Send alerts to a different address if you prefer
Everything included in the Free plan

Built for clarity

Email alerts

Downtime and recovery emails with the reason for the failure. Turn each type on or off, or send alerts to a different address.

Incident timeline

Every confirmed outage with start time, end time, duration and failure reason.

Response time charts

24-hour and 7-day charts of how quickly your server responds.

Daily uptime

Uptime percentages for 24 hours, 7 days and 30 days, plus a day-by-day availability strip.

SSL expiry tracking

For HTTPS websites we record the certificate's expiry date and issuer on every check and show the days remaining.

Error classification

DNS failures, timeouts, SSL problems, refused connections and HTTP errors are labelled so you know where to look.

On the roadmap

Planned features

These are not available yet. We list them so you know what we're working towards.

Coming soon

Public status pages

Share your uptime with customers on a page you control.

Coming soon

Monthly reports

A monthly email summary of uptime and incidents.

Coming soon

1-minute checks

Faster detection on the planned Pro plan.

Coming soon

Webhooks & API

Send alerts to your own tools on the planned Business plan.

Getting started

From sign-up to first check in under a minute

Sign-up flow: homepage form with website and email, confirmation email, choose a password, then the dashboard with the website added and the first check within a minute. Sign-up flow: homepage form with website and email, confirmation email, choose a password, then the dashboard with the website added and the first check within a minute.
Monitoring starts as soon as you confirm your email address.

Try it on your own website

Free for up to 5 websites. Set up in under a minute.