Everything UptimeVanguard checks, how it confirms an outage, and where your alerts go. Every feature on this page is in the paid plan at every size, from €10 a month for five sites, excl. VAT. The Free plan covers 3 sites with every check type and every alert channel, checked every 5 minutes.
One site can carry all of these checks, and they count once.
HTTP checks with any method, headers, a request body, basic or bearer authentication and redirect control. Assert the status codes you expect, text the response must contain or must not contain. Expect down turns the check around: we alert when a private address becomes reachable.
Expiry date, certificate chain and host name, checked every 1, 6, 12 or 24 hours. You get a warning well before the certificate expires, and a notice when it is renewed.
Reachability of a host with ICMP echo requests, every 1, 5, 10, 15 or 30 minutes.
Checks that a public port accepts a connection and measures the connect time: mail servers, database endpoints, VPN gateways. Any port from 1 to 65535, on public addresses only.
We read the A, AAAA, CNAME, MX, NS and TXT records from each region, and alert when the CNAME target or, without a CNAME, the host's own addresses change.
A testssl.sh grade of your TLS setup per domain. Scans run weekly, monthly or quarterly, or daily on a paid plan.
A daily scan of your page for dead links and resources that still load over plain http://.
Reads the health report of your application: queues, database, disk, scheduler. It uses the JSON format of spatie/laravel-health, and runs every five minutes.
Your job calls a ping URL each time it runs. When the call does not arrive within the interval plus a grace period, an incident opens. Snippets for shell, crontab, Laravel, Python, GitHub Actions and PowerShell.
A bad route to one probe should not wake anyone up.
Amsterdam, London, Falkenstein, Newark, Los Angeles, Singapore, Tokyo, Sydney, São Paulo and Johannesburg. Keep Automatic, or choose the primary region per monitor.
When a website, API, ping or DNS check fails, we recheck it 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: typically 1.5 to 2 minutes after the first failure at a 60-second interval.
On the paid plan, up to 10 HTTP or ping checks per team run every 30 seconds, at no extra charge. Other checks run every minute or slower. The trial checks every minute, the Free plan every 5 minutes.
Choose whether we alert after 1, 2, 3 or 5 failed checks in a row. The default is 2.
A heartbeat has no second region, because your job reports in itself. It alerts when its interval and grace period pass.
Route each event to the channel that should get it, and silence planned work.
Email, SMS, Slack, Microsoft Teams, Google Chat, Discord, Telegram, PagerDuty, ntfy and webhooks. SMS goes through your own Vonage, Twilio or CM.com account, so there are no SMS credits to run out.
Send one monitor to its own Slack channel and certificate warnings to email only. Rules match on monitor, check type and event, with a severity of Critical, Warning or Info.
Goes down, recovers, TLS certificate expires soon or is renewed, DNS records change or are restored, new scan issue or issue resolved. Gets slow and is fast again go to email and Telegram.
During a maintenance window failures open no incident and send no alert, and the time does not count in reports. Snooze a monitor for 30 minutes up to 24 hours.
Every alert and every attempt, with its status: delivered, failed, retrying, queued or muted. Kept for 90 days.
One place for the outage, the response and the update to your customers.
Every confirmed outage gets a timeline with the failed checks per region, who acknowledged it, notes and updates. It closes by itself when the monitor recovers.
Acknowledge an incident so your team knows someone is on it. Add internal notes, or post a public status page update from a template, now or at a set time.
Open incidents, average time to acknowledge, average time to resolve and total downtime, per period.
Download the incidents of one monitor for a period as CSV.
Tell customers what works before they ask.
Up to five public status pages per team, with the monitors you choose, active and planned maintenance, and the updates you post.
Visitors subscribe by email and confirm by link. 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.
Your logo, an accent color and auto, light or dark appearance. The page shows “Powered by UptimeVanguard”.
A public status badge for each monitor on a public status page, to show in a README or on your own site.
No custom domain and no password-protected pages yet. Pages run on our address: /status/your-page.
See which monitors met their target, and how much downtime you had.
Availability per monitor against a target of 99% up to 99.99%, with the error budget used, downtime, incidents and coverage. Maintenance windows do not count as downtime.
Export a period as CSV, or print the report and save it as a PDF from your browser. The owner can get a monthly report by email on the first day of each month.
Bring everyone in, and automate the rest.
Invite your whole team at every size. There is no per-seat charge.
Owner, Admin, Member and Viewer. A viewer sees everything and changes nothing, which suits a manager or a client who only needs to look.
Group monitors per client or environment, and filter reports by group. One person can own up to 10 teams, each with its own monitors and billing.
Manage sites, checks, incidents and status page updates, and read uptime, performance and report data. Personal access tokens with read or write abilities, an OpenAPI document, and 60 requests a minute.
Every request names us in its user agent, and the probe IP addresses are public, so you can allow-list them.
Where your data is, who processes it, and how long we keep it.
The application, its databases and your check results run at Hetzner in Falkenstein, Germany. The probes outside Germany hold no account data.
The data processing agreement is part of the terms. Every provider is named with its location and safeguard, including the US ones: Cloudflare in front of the site and Vultr for probes outside Germany.
Time-based one-time codes from an authenticator app, with eight single-use recovery codes.
The privacy statement lists how long each kind of data is kept. Data of an ended trial or subscription is deleted 30 days after the end.
UptimeVanguard is registered in the Netherlands, KvK 42017143. Invoices are in euro, with the EU VAT reverse charge checked against VIES.
So you can decide quickly whether this is the right tool:
See how this compares with Hyperping, UptimeRobot, Pingdom and Better Stack, and what it costs on the pricing page. The documentation covers every feature step by step.
Monitor every client site for one price per site, with groups per client and unlimited seats.
Know when the shop, its checkout page or its certificate fails, before customers tell you.
Watch customer websites, portals, mail hosts and backup jobs from one place.
Start free: seven days with every check type, then the Free plan for 3 sites. No card, and your first check runs in about two minutes.
