Checked as often as every 30 seconds on Team. Confirmed twice.
An HTTP check against your address from up to 2 locations, chosen by you. Down means a second location agrees, so a bad route never wakes you.
Three steps, no setup to learn.
Defaults cover most sites. Change what you need, when you need it.
Add the address
Paste a URL. A test check runs from the page before you save, so you see it work.
Every location checks it
On your interval, from up to 2 locations, chosen by you. Every result keeps its status and timing.
Two agree, then the alert
One failing location is a warning. When a second confirms it, the incident opens and your channels hear.
Evidence, not just a red dot.
Every check records enough to answer why, and a failure keeps more.
- Status expected 200 by default, any code you choose
- Keyword optional, must appear in the body
- Timing DNS, TCP, TLS and first byte inside the total
- Certificate expiry tracked, warnings at 14 and 7 days
- Domain warnings at 30 and 7 days before the registration ends
- On failure headers, 2 kB of body, the DNS answer, kept 30 days
- Slowness two slow checks in a row from one location read degraded, 15 confirmed slow minutes turn the day amber, never an alert
Cookies and authorization headers are never kept. Mark a monitor as carrying secrets and no body or headers are stored at all.
On every plan, faster on paid ones.
Every plan checks the same way. Paid plans check more often and from up to 2 locations, chosen by you.
Free0 EUR
- 20 monitors
- every 5 minutes
- 1 location, chosen by you, down after two failures in a row
Solo15 EUR a month
- 50 monitors
- every minute
- up to 2 locations, chosen by you
Team49 EUR a month
- 150 monitors
- every 30 seconds
- up to 2 locations, chosen by you, a longer wait before the first alert
Solo and Team wait for a second location; a free workspace alerts from its one location.
Before you add one.
What if only one location fails?
The monitor reads degraded and nobody is woken. It is down only when a second location agrees.
What if it is only slow?
A check that passes but takes longer than the time you set is slow. Two slow checks in a row from one location make the monitor read degraded, and 15 confirmed slow minutes turn that day amber in the history. Slowness never sends an alert.
Can I bring my monitors from another service?
Paste a list of addresses or upload a CSV. The preview shows what your plan allows before anything is created.
Can alerts go to a webhook?
Yes. A webhook channel posts a signed JSON event to your https address when an incident opens, repeats, is acknowledged and recovers. Alerts reach you by email, Slack, Telegram, webhooks, Discord and Microsoft Teams today.
What if my response contains secrets?
Mark the monitor as carrying secrets. Its checks then store no body and no headers, and what was kept before is removed.