Quorum-based uptime monitoring

Down means down

When one probe sees a problem, the whole fleet checks at once. You’re paged only when three continents and three networks agree, or when it’s down where your visitors are, and the alert tells you why. If it isn’t down, you sleep.

Type your address: 20 probes on six continents check it this second. No sign-up. or start free without checking →

650,000 free credits a month for the month you join and the three after it, then 200,000. No card, no password needed, no seats, no subscription unless you want one.

Monitors

Checked from 20 probes on 6 continents.

Overall22 1 1
Uptime · 24 h99.96%
Response · median412 ms
Incidents · 24 h1
20
probes on 6 continents
14 of 20
must agree, from 3 continents and 3 networks
47 s
median from the first failed check to a confirmed outage
10 s
shortest check interval
How it works

One failure is a rumour. Agreement across continents is an outage.

Most monitors alert the moment one location times out. That location may have a routing problem, a full disk or a noisy neighbour. We treat a failure as a question: the whole fleet switches to Alert mode, asks it again from everywhere, and works out where it breaks.

01 · check

Scheduled check

On every interval a third of the fleet, six or seven probes on at least four continents, checks your site at once; under a minute, three probes on three continents. That whole check costs one credit; from 24 November 2026, new accounts pay two every 5 minutes and 0.75 under a minute.

02 · alert mode

The fleet switches to Alert mode

The moment one probe sees a failure, every healthy probe joins in and checks your site every 5 seconds, step by step: DNS, connection, TLS, HTTP. Alert mode is free and never touches your balance.

03 · page

Quorum, then alert

Down means two thirds of healthy probes agree, from at least three continents and three networks, and the failure lasts. Then you’re paged, with what broke: refused connection, expired certificate, wrong DNS answer, or a route problem in one region.

Twenty probes on six continents check the same target. Central declares down only when two thirds agree, across three continents and three networks, in two rounds. Europe · 7 probesFRA LON LHR MAN STO AMS WAW Americas · 6 probesNYC EWR DAL SFO SAO SAO2 Asia · Oceania · Africa · 7SIN TYO BOM FJR SYD SYD2 JNB your siteHTTP · TLS · TCP central · quorum ⅔ agree · 3 continents × 2 rounds → down results

“I really like the idea of a quorum deciding if a site is down. Too many times I am chasing transitory issues.”

Paul Kelsall
WP Pro Host · managed WordPress & WooCommerce hosting, UK
Infrastructure

Built like the thing it watches.

A monitor you can't trust is worse than none. So the probes watch each other, the central watches itself, and nothing about the design depends on one machine.

probe fleet
20 dedicated servers in 17 cities on 6 continents, at 6 different providers. Static IPv4 (IPv6 where the provider offers it), published reverse DNS.
quorum
Two thirds of healthy probes, from at least 3 continents and 3 networks, holding for 20 seconds in Alert mode or for two confirmation rounds in a row. A failure seen from one region only is shown as a partial outage, never as down.
probe self-check
Each probe tests known-good canaries. A probe that can’t reach them is quarantined and its votes don’t count. Below 8 healthy probes we never page; we tell ops instead.
central outage
Probes cache their job list and keep checking. Results are buffered in memory and sent when central returns.
dead-man's switch
Central's scheduler pings an external heartbeat every tick. If it stops, we're paged by someone else's monitor.
retention
14 d raw per-probe results · 1 y hourly rollups (uptime, p50, p95) · incidents forever.
safety
Every target resolved once, refused if any address is private, connected to by IP. Redirects re-validated. Body capped at 256 KB.
abuse gate
Any public host gets HTTP/TLS on 80/443, ping, and TCP, SMTP and DNS on the common ports, every 10 s at the fastest. Verify a domain via DNS TXT or a file to unlock any port and custom requests. Owners can opt out at /probes.
jurisdiction
Your data stays in the EU; only the checks run worldwide. GDPR export and deletion built in.
signed checks
Every request our probes make is cryptographically signed and comes from a published address with reverse DNS, so a firewall can verify it is ours and nobody can pretend to be us.
What you get

The checks that matter, done properly.

Alert mode

One failure puts the whole fleet on alert. Every healthy probe checks and reports where the request broke, so the alert says why your site is down, not only that it is. Nobody is paged for one city’s bad route.

HTTP(S) and keywords

Status codes, keyword present or absent, redirects followed and re-checked. Catches a WordPress database-connection error page served with a 200. For APIs on your verified domains: any method, custom headers, a request body and Basic auth.

TLS and expiry

Certificate days read from the same connection as the check, on 443 or any port, including SMTP STARTTLS.

Ping, TCP, SMTP, DNS, SSH, IMAP, NTP, WebSocket

Ping any public server, IPv4 or IPv6. Ports, mail banners, DNS answers, SSH, IMAP, POP3, FTP and NTP servers, WebSocket endpoints, and JSON assertions on API responses. Blacklist (DNSBL) and SPF, DKIM and DMARC checks for your mail domains, and the status pages of 35 cloud providers you depend on.

Cron jobs and backups

Heartbeat monitors: your job calls its own address when it finishes, or reports a failure with the reason. Silence past the grace period pages you.

Domain expiry and slow responses

Every monitored domain is checked for expiry daily, at no cost. Optional slow-response alerts use the median of all probes, so one slow city can't trigger them.

Blocked, not down cloudflare

A WAF challenge or a Cloudflare block page is reported as “blocked”, never as down. Connect your Cloudflare account and we keep the allow-list rule in place for you, or use our ready-made list. Every check we make is cryptographically signed, so a firewall can verify it is ours.

Partial outages and geo-blocking

Unreachable from Asia but fine everywhere else? You see exactly that, with the region. If your site blocks a continent on purpose, we notice and let you take those probes out of the vote.

Dev / stage mode

Staging sites are watched without paging anyone. You see the history, nobody wakes up.

Import from where you are

Paste a read-only key from UptimeRobot or updown.io, or upload an Uptime Kuma backup file or a CSV. You see every monitor we found and the monthly cost before anything is created. Export the same CSV whenever you like; nothing is locked in. How switching works.

Groups and bulk changes

Put one customer’s monitors in one group: its own section on the dashboard, its own status page, its own alert channel, its own maintenance window. Select every monitor that matches a filter and change the interval, channels or group in one go; the credit cost shows before you confirm.

Maintenance windows

Once, daily, weekly or monthly, for one site, a whole group or everything. Checks keep running; nobody is paged, and it doesn’t count against your uptime.

Evidence in every alert

What each probe saw: resolved IP, status, timing, error. Forward it to your host and skip the argument, or share the incident page itself by a secret read-only link that needs no account.

Acknowledge and escalate

One link in every alert puts the incident on hold and stops the reminders. A channel can be told to fire only if nobody has acknowledged within 5, 10 or 30 minutes: the on-call engineer first, the whole team only if they don’t answer.

Monthly uptime report

Every account gets a monthly report of uptime, incidents and response times per site, printable to PDF; resellers get it under their own brand for each customer.

Speed, not just up

Each site shows how often it was fast enough: the share of checks under your target and the time three in four checks stayed under, per region. Slow alerts use the median of all probes, so one slow city can’t wake you.

Ask your AI assistant mcp

Connect Claude or any MCP client to your account and ask «which sites were down this week?» or «add a monitor for shop.example.com every minute». Read only or read and write, owners only, every change in the activity log.

Public status pages

Pick the monitors or a whole group, name them, publish. Visitors see confirmed facts only: operational, partial outage, outage or maintenance, with 90 days of history. Your logo and colours.

API and signed webhooks

Everything you can click, you can script: monitors, incidents, groups, status pages and customer accounts over a REST API, and a signed webhook for every alert. Keys per person, read only or read and write.

Email, Slack, Teams, Discord, Telegram, SMS and calls

Alerts go where you already look, each on its own terms: Telegram at once, email only after 10 minutes, reminders every 30 while it’s down. Also Google Chat, PagerDuty, phone push through ntfy and Pushover, signed webhooks, and SMS and phone calls to EU and UK numbers.

For hosting providers enhance cpanel/whm plesk

Connect your Enhance panel, cPanel/WHM or Plesk server under Integrations and every website is monitored, paused when suspended, removed when deleted. Each customer can get an account under your brand, with their own status page and alerts, on your credits.

More on each: Uptime monitoring · Website monitoring · Status pages · SSL monitoring · Cron monitoring · Free uptime monitoring

Pricing

Pay for what you monitor.

One credit per check; for accounts opened from 24 November 2026, two every 5 minutes and 0.75 under a minute. Every account gets every alert channel, status pages, integrations, the API and your whole team.

€8.64a month for 100 sites checked every 5 minutes

€21.60a month for 100 sites checked every minute

Before the free credits. That’s €5 per million credits.

Free

11 sites every 5 minutes

or 4 every minute

€5 a month

69 sites every 5 minutes

or 27 every minute

€10 a month

127 sites every 5 minutes

or 50 every minute

€25 a month

300 sites every 5 minutes

or 120 every minute

€50 a month

590 sites every 5 minutes

or 236 every minute

Monthly, change or cancel any time. Prefer to pay as you go? Packs from €5. Unused credits last 24 months. New accounts get 650,000 free credits a month for their first months. For companies: PingWise Business, €249 a month with an SLA.

100 sites, checked every minute, a month · public prices, billed yearly

Each service’s cheapest plan that covers the same monitors, interval, check types and people, as its pricing page shows them, checked . Dollar prices as published, compared at $1 ≈ €0.89. Full comparison.

Work out your exact price
€0/mo
a month, at €5 per million
0
credits per month

    PackPricePer million
    • Example: 20 monitors every 1 min = 864,000 credits a month = €3.32/mo.
    • One credit is one scheduled check every minute or slower. For accounts opened from 24 November 2026, a check every 5 minutes is two credits and one every 30, 15 or 10 seconds is 0.75; a monitor every 5 minutes still uses 40% of the credits of one every minute. Confirmation rounds, Alert mode, blocked-probe retries and recovery checks cost nothing. Heartbeat monitors use one credit per expected check-in.
    • Free credits are used first and reset on the 1st. Bought credits last 24 months. Prices are before VAT.
    • An email when about a week of credits is left; at zero, 7 days’ grace, then monitors pause with a message on every alert channel.
    • Accounts opened before 6 November 2026 keep 650,000 free credits every month. Accounts opened before 24 November 2026 keep the earlier rates: one credit a check every minute or slower, 0.6, 0.45 or 0.4 under a minute.

    SMS and phone-call alerts

    Paid from SMS units, bought separately from credits; credits never pay for a text or a call. Every other alert channel is free.

    PackPrice
    50 SMS units€5
    100 SMS units€10
    250 SMS units€25
    • One unit is €0.10, before VAT. Units last 24 months. Unused units are refunded like credits; used ones are not.
    • A text costs 1, 2 or 3 units, by the number’s country. 1 unit: Czechia, Denmark, Greece, Malta, Poland, Portugal, United Kingdom. 2 units: Austria, Belgium, Cyprus, Estonia, Finland, France, Germany, Hungary, Ireland, Italy, Latvia, Lithuania, Luxembourg, Netherlands, Romania, Slovakia, Spain, Sweden. 3 units: Bulgaria, Croatia.
    • A call costs 3, 6, 9 or 13 units a started minute. 3 units: Cyprus, Czechia, Denmark, France, Hungary, Ireland, Romania, Slovakia, Spain, Sweden. 6 units: Austria, Germany, Italy, Luxembourg, Netherlands, Poland. 9 units: Belgium, Bulgaria, Estonia, Finland, Greece, Latvia, Lithuania, Malta, Portugal, United Kingdom. 13 units: Croatia, Slovenia. Unanswered, busy or failed calls cost nothing. Calls ring for outages only, and you press 1 to acknowledge.
    • The 6-digit code that confirms a number costs 1 unit by text, or the price of a call when you confirm by call. Up to 2 numbers and 50 texts and calls a day per account.
    • Numbers in other countries can’t receive texts or calls from PingWise. Prices follow our provider’s rates, and the price for each country shows when you add the number. See SMS and phone-call alerts.
    Compared

    What 50 monitors at 1 minute cost.

    Public list prices, checked . Monthly cost on each vendor's cheapest plan that covers it.

    Full comparison with features, locations, confirmation policy and every source.

    PingWise Business

    Need a contract and an invoice?

    A yearly plan for businesses, €249 a month before VAT, billed yearly. The same probes and the same quorum, on terms your company can sign.

    25,000,000 credits a month

    About 578 monitors every minute, included each month of the plan.

    Priority support: critical incidents answered within 1 hour

    08:00–22:00 Athens time, every day; everything else by the next business day, ahead of the general queue.

    99.9% monthly availability commitment with service credits

    The panel, the API and alert delivery to your channel's provider, measured on our public status page.

    An invoice your finance team can pay

    Card, or bank transfer against a yearly invoice with your company's VAT ID.

    See PingWise Business More than 25 million checks a month? Write to hello@pingwise.com.
    Questions

    Plain answers.

    Where are the probes?

    Frankfurt, London (two), Manchester, Stockholm, Amsterdam, Warsaw, New York, New Jersey, Dallas, San Francisco, São Paulo (two), Singapore, Tokyo, Mumbai, Fujairah, Sydney (two) and Johannesburg. Names and IPs are on the probe page.

    Will you ever miss a real outage?

    Confirmation adds less than a minute before we page: 47 seconds at the median in our two-week test. In exchange, every page is real. If one region can’t reach you, you see a partial outage with the region, and can choose to be alerted for that too; if it’s the region where your visitors are, we alert you once it has lasted a minute.

    How many minutes after a site goes down do I hear?

    At most the check interval to notice it, plus usually less than a minute to confirm it. Checked every 5 minutes: within about 6 minutes. Every minute: within about 2. Every 15 or 10 seconds: within about a minute. The alert itself leaves within seconds of confirmation.

    My site is behind Cloudflare. Will it work?

    Yes. We publish our probe IPs and show the exact WAF rule that lets them through. Until you add it, challenges show as “blocked”, never as down.

    Is there a free plan?

    Every account gets 650,000 credits a month for the month it joins and the three after it, enough for 15 monitors every minute or 37 every 5 minutes, and 200,000 on the 1st of every month after that: 4 monitors every minute, or 11 every 5 minutes, without paying anything (for accounts opened before 24 November 2026, 75 and 23 every 5 minutes). Accounts opened before 6 November 2026 keep 650,000 every month. Bought credits last 24 months.

    Do you have status pages?

    Yes, included. Each page shows only confirmed outages, partial outages and maintenance, never an unconfirmed blip, and carries your name, logo and colours. Each page can run on your own domain, like status.yourcompany.com, and gives you a status badge to embed on your site or in a README.

    Who runs this?

    Our team works remotely, with members from Greece, Sweden, Serbia and North Macedonia. Five people who have run hosting and their own projects for fifteen years, and built PingWise because our own servers needed a monitor we could trust.

    Is there an API?

    Yes. A REST API with keys you make in Team → API keys, read only or read and write: monitors, incidents, groups, alert channels, status pages and probes, plus customer accounts for resellers. Docs at pingwise.com/docs/api. Signed webhooks for alerts as well.

    Be paged only when it's real.

    650,000 free credits a month for the month you join and the three after it, then 200,000. No card needed.