Website monitoring with a second-region outage check.

Monitor websites, APIs, SSL certificates, DNS and scheduled jobs. Your checks run from the region you pick, out of ten on six continents. When a website or API check fails, a second region checks it before you are alerted, so a bad route to one probe does not page you. The application and your results are hosted in Germany.

  • 7-day trial of every check type on 5 sites, then free for 3 sites with every check type
  • No card needed
  • €10 a month for five sites, excl. VAT

Fleet figures

across the whole fleet, since June 2026

Incidents opened
476,395
Alerts sent
1,106,235
Probe regions
10
10Regions to choose from
30sFastest check interval
9Check types
10Alert channels
What it monitors

One tool for everything that can quietly stop working.

A valid certificate, a correct DNS record and a cron job that actually ran matter as much as the page being up. Every type below is included in the trial and on every paid plan, at every size.

Uptime and response time

HTTP and ping checks every 60 seconds, or every 30 seconds for up to 10 checks on a paid plan, with status code, response time and body assertions. Results are kept per region, so you can see whether the site is down or only the route from one probe is.

TLS certificates

Expiry warnings well before the renewal fails. The certificate outage you find out about on Monday is the one nobody was watching.

DNS records

Your hostname is resolved from each region. You get told when its CNAME target changes or, for a hostname without a CNAME, when its own addresses change.

TCP ports

Check that a public port accepts connections: a mail server, a database endpoint or a VPN gateway. In the trial and on paid plans.

Cron and job heartbeats

Give a scheduled job a ping URL. If the job stops running, the missing ping raises the alert. Backups and imports that silently stopped are the outages nobody notices.

Broken links and mixed content

Crawl your pages on a schedule for dead links and assets still loading over plain HTTP, and fix them before a customer meets one.

Application health endpoints

Poll your own /health route and alert on the fields it reports: queue depth, database reachability, disk, whatever you already expose.

Public status pages

Up to five hosted status pages, with incident history and email subscribers. Stop answering the same question fifty times during an outage.

Teams, reports and an API

Invite your team with roles, group sites per client or environment, view uptime reports, receive monthly report emails, and manage sites and checks through the REST API.

See every feature in detail

Alerting

Confirmed before anyone is woken up.

A check can fail because your site is down, or because one route to it is. Outbound checks are re-run from a second region — normally the nearest — before the incident opens. A missed heartbeat has no second region: it alerts on the window you set.

  • Email, SMS through your own Vonage, Twilio or CM.com account, Slack, Microsoft Teams, Google Chat, Discord, Telegram, PagerDuty, ntfy and webhooks
  • Rules per site and per check, not one global switch
  • Recovery notices, with how long it was down
  • Maintenance windows and silences, so planned work pages nobody
Incident timeline
09:41:02  eu-west-2  Amsterdam  HTTP 502  api.example.com09:41:13  eu-west-1  London     HTTP 502  second region checks09:41:32  eu-west-2  Amsterdam  HTTP 502  rechecked after 30 s09:41:43  eu-west-1  London     HTTP 502  confirmed09:42:43  incident #4471 opened, still down after 60 s09:42:44  notify     slack #ops, on-call email09:44:21  eu-west-2  Amsterdam  HTTP 200  recovered09:44:22  incident #4471 closed, down 3m 20s

Example incident.

Global coverage

Pick your region. We pick the second one.

Your check runs from the primary region you choose. Any failure is re-run from a second region — normally the nearest one — and only a failure both agree on opens an incident. Ten regions today, and the list only grows.

  • Amsterdam eu-west-2
  • London eu-west-1
  • Falkenstein eu-central-1
  • Newark na-east-2
  • Los Angeles na-west-1
  • Singapore ap-southeast-1
  • Tokyo ap-northeast-1
  • Sydney ap-southeast-2
  • São Paulo sa-east-1
  • Johannesburg af-south-1
Getting started

Monitoring your first site takes about two minutes.

Add a site

Paste a URL. We detect what is worth checking — the page, its certificate and its DNS — and turn those checks on for you.

Say where alerts go

Connect email, SMS, Slack, Microsoft Teams, Google Chat, Discord, Telegram, PagerDuty, ntfy or a webhook. Set the thresholds that matter to you and nothing else.

Go back to work

You hear from us when something is wrong, confirmed from a second region, with the detail you need to start fixing it.

Pricing

One plan. You pick the number of sites.

Every capability on this page is included at every size. No feature tiers and no per-seat charge.

Standard

€10 / month, excl. VAT

One to five sites included

Monthly price by number of sites, excluding VAT
SitesPer month
1–5€10.00
10€17.50
25€40.00
50€70.00
100€130.00
250€272.50
500€447.50
Start free

Any whole number of sites from one to five hundred: seven sites is €13.00 a month. Sites 6–25 add €1.50 each, 26–100 €1.20, 101–250 €0.95, 251–500 €0.70. Pay monthly by card, or prepay 6 or 12 months in one payment by card, iDEAL or bank transfer. Monthly billing renews until you cancel; the trial does not start a paid subscription by itself. Cancel from your billing page with no notice period, and monitoring runs to the end of the period you have paid for.

Included at every size

  • Checks every 60 seconds from the region you pick, and every 30 seconds for up to 10 HTTP or ping checks
  • Website, API, ping and DNS failures confirmed from a second region before you are alerted
  • HTTP, ping, TCP port, DNS, SSL certificate, SSL score, broken-link, application health and heartbeat checks
  • Up to 5 hosted public status pages
  • Unlimited team members and unlimited alert rules
  • Incident timeline, maintenance windows and silences
  • Monthly uptime report emails and REST API access

A site is one hostname. www.example.com and api.example.com are two. One hostname can carry several checks and they count once, including the cron heartbeats you add to it. Need every check run from all ten regions at once, rather than a primary plus a confirming second? That is a premium option, as is going past 500 sites. Talk to us and we will size it with you.

Free plan: 3 sites, checked every 5 minutes from one region, with every check type, every alert channel, 1 status page and 30 days of history. No card, never billed. A trial that ends without a paid plan continues on it.

Pricing details, examples and VAT

Questions

The things people ask before signing up.

Do I need a credit card to try it?

No. The 7-day trial starts as soon as you register and needs no payment details. If you do nothing at the end of it, your team continues on the Free plan: 3 sites with every check type and every alert channel, checked every 5 minutes. Nothing is charged.

How fast will I hear about an outage?

Checks run every 60 seconds from your main region, or every 30 seconds for up to 10 HTTP or ping checks on a paid plan. When a check fails, it is rechecked every 30 seconds, and a second region, normally the nearest, checks it too. The incident opens when both regions have failed twice and the failure has lasted another minute: at a 60-second interval, typically 1.5 to 2 minutes after the first failed check. This filters out failures on a single route. A heartbeat has no second region; it alerts when its window passes.

What counts as a "site"?

One hostname you monitor. A site can carry several checks — the page, its certificate, its DNS records, a broken-link crawl — and those all count as one site. A heartbeat for a cron job belongs to a site and counts with it.

Can I share a public status page?

Yes. Share a hosted status page URL. Visitors can subscribe by email. After they confirm their address, they get an email when a component goes down or recovers, and when you post an update, unless you turn that off for the page or for one update.

Where is my data stored?

The application, its databases and your check results are in Germany. The probes run worldwide and hold no account data; they receive a check definition, run it, and send the result back.

Can I cancel whenever I want?

Yes, from the billing page in your account, with no notice period and no cancellation fee. You keep access until the end of the period you have already paid for.

Is there an API?

Yes — a REST API with personal access tokens covering sites, checks, results, incidents and status pages. Use it to manage monitors and retrieve monitoring data.

Start now

Hear about the next outage from us.

A 7-day trial of every check type on 5 sites, then free for 3 sites. No card, and your first check running in about two minutes.