Uptime monitoring that only says «down» when it’s down
PingWise checks your sites, servers and ports from 20 probes in 17 cities on 6 continents. One failed request from one place never wakes you up. Every probe checks again, and a monitor goes down only when most of them agree.
How a check becomes an alert.
A round
Every scheduled check runs from six or seven probes on at least four continents. At 10, 15 and 30 seconds a round uses three probes on three continents.
Confirmation
If any probe sees a failure, every healthy probe checks again about eight seconds later. Confirmation rounds are free.
Down, then back up
Two thirds of the healthy probes fail, on at least three continents and three different providers, in two confirmation rounds in a row. That usually takes about a minute. The recovery alert goes out about 15–25 seconds after the site answers again.
The full rule, with the numbers: How a check works.
Not every red light is an outage.
Blocked
A firewall or a Cloudflare challenge answered the probe. That’s reported as blocked, not as down, because your visitors may be fine. Check a site in advance with the Cloudflare check.
Partial
Unreachable from some continents only. It alerts only if you turn that on.
Slow
The median response is over your threshold for 5 minutes. Slow never counts against uptime.
Unconfirmed failure
A short stumble that never reached a quorum. It’s marked on the timeline, but doesn’t alert and doesn’t count as downtime.
What you can monitor, and where you hear about it.
What you can monitor
Websites and APIs (HTTP/HTTPS, keywords, JSON fields), TLS certificates, TCP ports, ping, DNS, SMTP, SSH, IMAP, POP3, FTP, NTP, WebSocket, cron jobs (heartbeats), spam blocklists, SPF/DKIM/DMARC, and cloud providers’ own status pages. Domain expiry is tracked for every monitor at no cost. Every monitor type.
Alerts where you work
Email, Slack, Microsoft Teams, Discord, Telegram, Google Chat, PagerDuty, Pushover, ntfy and webhooks, plus SMS and phone calls to EU and UK numbers. Every alert shows what each probe saw: the address it resolved, the status code, the timings and the error. Alert channels.
Checks every 10 seconds, on every account
Any interval from 10 seconds to 1 hour, on free accounts too. A faster interval only uses more credits. Intervals and credits.
Pricing in one line
Free: 650,000 checks a month for your sign-up month and the three after it, then 200,000 a month. After that: €5 per million, prepaid. Bought credits last two years. No subscription and no per-seat price. Pricing · What’s free.
Questions
How fast will I know?
A confirmed outage usually takes about a minute: one round sees it, then two confirmation rounds agree. If you need an alert within seconds of the first failed request, this isn’t built for that.
Where are the probes?
In Amsterdam, Dallas, Frankfurt, Fujairah, Johannesburg, London, Manchester, Mumbai, New Jersey, New York, San Francisco, Singapore, Stockholm, Sydney, São Paulo, Tokyo and Warsaw. Every IP is listed at pingwise.com/probes for your firewall allowlist.
My site is only for one region. Will Asia’s probes mark it down?
You can exclude continents from voting on a monitor, as long as at least three probes on two providers remain.
Can I connect my hosting panel?
Yes: Enhance, cPanel/WHM and Plesk create a monitor for every site automatically.