Uptime and response time
HTTP and ping checks as often as every 60 seconds, 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.
Your customers should never be the ones who tell you it is down.
Pick the region your checks run from. When one fails, a second region re-runs it before you are told, so a bad route to one probe does not page you at 3am. Eleven regions to choose from, on six continents.
- 7-day trial
- No card required
- €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
- 11
11Regions to choose from
60sFastest check interval
8Check types
5Alert 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 at every price.
TLS certificates
Expiry warnings well before the renewal fails, plus a full scan of protocols, ciphers and chain problems. The certificate outage you find out about on Monday is the one nobody was watching.
DNS records
Watch A, AAAA, MX, NS, TXT and CNAME records, resolved from each region, and get told when one changes value or disappears.
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, on your own domain, 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, schedule PDF and CSV reports, and script all of it from the REST API.
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, Slack, Telegram, Discord and generic 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
09:41:02 eu-west-2 Amsterdam HTTP 502 api.example.com
09:41:09 na-east-2 Newark HTTP 502 confirmed
09:41:09 incident #4471 opened
09:41:10 notify slack #ops, on-call email
09:44:21 eu-west-2 Amsterdam HTTP 200 recovered
09:44:22 incident #4471 closed, down 3m 20sExample 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. Eleven 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 - Mumbai
as-south-1 - 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 Slack, Telegram, Discord, a webhook, or just use email. 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
| Sites | Per month |
|---|---|
| 1–5 | €10.00 |
| 10 | €17.50 |
| 25 | €40.00 |
| 50 | €70.00 |
| 100 | €130.00 |
| 250 | €272.50 |
| 500 | €447.50 |
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 as often as every 60 seconds, from the region you pick
- Every failure confirmed from a second region before you are alerted
- Uptime, HTTP, ping, DNS, TLS, broken-link, health and heartbeat checks
- Up to 5 public status pages, on your own domain
- Unlimited team members and unlimited alert rules
- Incident timeline, maintenance windows and silences
- Scheduled reports and the full REST API
A site is one hostname. www.example.com and api.example.com are two. One hostname can carry several checks and they count once; a cron heartbeat counts as a site. Need every check run from all eleven regions at once, rather than a primary plus a confirming second? That is a premium option, as is going past 25 sites. Talk to us and we will size it with you.
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, the account stops monitoring.
How fast will I hear about an outage?
Checks run as often as every 60 seconds from your primary region. A failure is then re-run from a second region, normally the nearest, before the alert goes out. That costs one further check interval and filters out failures on a single route.
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. Heartbeats for cron jobs are counted as sites too.
Can I put a status page on my own domain?
Yes. Point a CNAME at us and the status page is served on your domain with a certificate we manage. Visitors can subscribe by email and are notified when you post an incident 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. Everything the interface does, you can script.
Start now
Hear about the next outage from us.
Seven days free, no card, and your first check running in about two minutes.