Uptime monitoring that tells you what failed, from where, and for how long.
Relvato requests your site from Europe and the US as often as your plan allows — every 5 minutes on Free, every minute on Pro and Business, every 30 seconds on Agency. When both regions agree it's down, you're alerted at once with the status, the regions and the time. When it's back, you hear that too, with how long it was down.
- ✓An answer within your timeout (15 s by default) — not a 5xx, a 404 or silence
- ✓Only the status codes you accept, if you set them
- ✓Text that must appear does, and text that mustn't doesn't
- ✓No error page or raw code, even behind a 200
- ✓Confirmed from two regions before anyone is alerted
- ✓Uptime % from confirmed outage minutes, to two decimals
- ✓API endpoints too: GET, HEAD or POST, with rules on the JSON answer
- ✓Maintenance windows: no alerts inside them, and only the time after them counts as downtime
- ✓A screenshot of what visitors saw when it went down
Most outages are short and happen when nobody is looking: a host restart, a certificate that lapsed, a database that stops answering. A single location also cries wolf when its own network has a blip. Two regions that must agree, and an alert that says exactly what failed, mean you act on real outages — and your uptime % counts only those.
On WordPress, if your site is down behind a stuck maintenance page or a “Coming soon” gate, Relvato suggests deleting the leftover maintenance file or lifting the gate, and you apply it with one click in WordPress → Relvato. Relvato then checks that the site is back.
- Light requests from Europe and the US reach the page you choose — the homepage by default — every 5 minutes on Free, every minute on Pro and Business, every 30 seconds on Agency.
- A site counts as down only when both regions agree, so one network blip never alerts you; a single region needs two failures in a row.
- The alert names what each region saw and when it started; a second alert says it's back up and how long it was down. Both go out at once, even if your other alerts come as a daily digest. The outage's run also shows a screenshot of what the page showed when it went down.
- The Uptime monitor's own run also requests the page on its schedule and after changes, and fails on an error page or raw PHP that still answers 200.
Do I need to install anything?
No. Uptime monitoring works on any site — just verify your domain.
How often does it look?
Every 5 minutes on Free, every minute on Pro and Business, every 30 seconds on Agency, from Europe and the US. These are light requests, not runs, so they don't count against your plan's runs.
Can I choose what counts as down?
Yes: the page to request, text that must or must not appear, the status codes you accept, how long to wait for an answer, and how many minutes down before you're alerted — so a 30-second restart doesn't wake anyone.
Will I hear when it's back up?
Yes. Every outage sends “down”, then “back up after N minutes”. If it was over before the first alert went out, you get one “was down for N minutes” alert instead.
Can I see what visitors saw while it was down?
Yes. Right after an outage is confirmed, Relvato opens the page in a browser and adds a screenshot to the outage's run page: the error page, a host's suspension notice, a blank screen. When nothing answers at all, it shows what the browser got instead: the address doesn't resolve, the connection was refused, or it timed out. API monitors (HEAD, POST or JSON rules) don't get one, because there's no page to show.
Where do I see the history?
On each site's Uptime tab: whether it's up now, the latest answer from each region, uptime % over 24 hours, 7, 30 and 90 days, a 90-day bar, response time per region, and every outage with its cause.
Can I schedule maintenance?
Yes. Add one-off or weekly maintenance windows (e.g. Sundays 02:00–03:00 in your time zone). Inside a window nobody is alerted, and an outage that starts there counts against uptime % only for the time after the window ends. A window on now or within the next week shows on your status pages.
Can it monitor an API or health endpoint?
Yes. Point the Uptime monitor at the endpoint, choose GET, HEAD or POST (a POST can send a JSON body), and add up to 10 rules on the JSON answer — for example status equals ok, checks.db.ok equals true, or latency_ms is less than 500. A 200 with the wrong JSON counts as down, and the alert names the rule. Custom headers and tokens aren't supported yet, so use an endpoint that answers without them.
Can it watch a port, like a mail server or a database?
Yes. Add a TCP port monitor on the site's Uptime tab — a host on your own domain and a port, e.g. mail.example.com:587 or db.example.com:5432. It's connected to from Europe and the US as often as your uptime probes, counts as down only when both agree, and alerts at once, then again when it answers. 1 on Free, 5 on Pro, 20 on Business, 100 on Agency.
Put this monitor on autopilot.
Free forever on one site — 100 runs a month, started by you or weekly, no card. Pro re-runs your monitors by itself after every update.