PingWise vs Cronitor
Cronitor is built around cron-job monitoring, with SDKs and per-run metrics. PingWise is built around uptime checks that page you only when 10 of 15 probes agree.
Which one should you pick?
Pick Cronitor if scheduled jobs are your main worry. It tracks each run’s start, finish and duration, has SDKs and integrations for common job runners, alerts on duration and error rates, and adds real-user monitoring. Our heartbeat monitors cover the basic case, a job that didn’t report in or reported a failure, but not that depth.
Pick PingWise if websites and APIs are your main worry. Cronitor documents retrying a failed check from the same location. We check every scheduled round from several cities at once and page you only when 10 of 15 probes, on at least 3 continents and 3 providers, fail two rounds in a row. We also report WAF challenges as “blocked”, and every alert shows what each probe saw.
On price, Cronitor charges per monitor and per user. The table below shows 50 monitors every minute at €7.55 a month here and $105 there, with unlimited team members here.
Start free 650,000 free credits every month.
Price per month
HTTP monitors at the given interval, on each service's cheapest plan that covers it. Annual billing where it's cheaper. Prices in each vendor's own currency, not converted. Checked 26 Oct 2026.
| Service | Cheapest paid | 10 × 1 min | 50 × 1 min | 50 × 5 min | Free tier | Locations | Before alerting |
|---|---|---|---|---|---|---|---|
| PingWise | credits from €5 | free | €7.55 | free | 650,000 credits every month | 15 cities, 6 continents | Two thirds of 15 probes (10), 3 continents, 3 providers, 2 rounds in a row |
| Cronitor | $2/monitor + $5/user | $25 | $105 | $105 | 5 monitors @ 5 min | 11 regions | Consecutive failures; no second location documented |
PingWise prices use the rate of the credit pack a year of that usage would use up.
Features
On each service's cheapest paid plan, as documented by that vendor.
✓ documented by the vendor · – documented as not offered · n/d not found in the vendor's public documentation · text = yes, with that limit
| Feature | PingWise | Cronitor |
|---|---|---|
| Every check from several locations at onceon every scheduled check, not only when confirming | ✓ | n/d |
| Confirmation before pagingwhat the vendor documents happens after a failed check | 2 rounds, all 15 probes | retries, same location |
| Confirmation must span continentsa failure in one region can't page you | ✓ | n/d |
| Confirmation must span providersone provider's network trouble can't page you | ✓ | n/d |
| Broken probes removed automatically | ✓ | n/d |
| WAF challenge shown as “blocked”, not down; Cloudflare allow-list managed for youconnect your Cloudflare account; we keep the skip rule in place | ✓ | n/d |
| What each probe saw, in the alert | ✓ | n/d |
| Prepaid credits, no subscription | ✓ | – |
| Unlimited team memberson the cheapest paid plan | ✓ | $5/user |
| Telegram and webhook alertson the cheapest paid plan | ✓ | ✓ |
| Slack, Teams and Discord alertson the cheapest paid plan | ✓ | ✓ |
| PagerDuty alertson the cheapest paid plan | ✓ | Business plan |
| 15-second checks | verified domains | n/d |
| Ping (ICMP) to any host | ✓ | n/d |
| SMS and phone alerts | soon | SMS |
| Public status pageswith your logo and colours | ✓ | 1 |
| Monitor groups: a status page, an alert channel and a maintenance window per groupone group per monitor; the dashboard shows a section per group | ✓ | n/d |
| Bulk changes across every monitor that matches a filterinterval, channels, group, pause, delete; the monthly credit cost is shown before you confirm | ✓ | n/d |
| Import from other monitoring tools, with a preview firstwhat the vendor documents it can read in | UptimeRobot, updown.io, Uptime Kuma, CSV | n/d |
| Heartbeat / cron monitoring | ✓ | ✓ |
| Domain expiry alertsregistrable domain of every monitor, checked daily | free · date by hand where the registry hides it | n/d |
| Slow-response alerts | median of all probes, not one slow city | ✓ |
| Public APIkeys, monitors, incidents, groups; an OpenAPI document | ✓ | ✓ |
Where Cronitor is the better choice
Being honest about this saves everyone time.
Job monitoring depth
Cronitor records start and finish of each run, durations and counts, with SDKs for common languages and schedulers. Our heartbeats only know whether a job reported in, and whether it reported a failure. If a backup that ran but took four times longer than usual is a problem for you, Cronitor tells you; we don't.
Metrics in heartbeats
Cronitor heartbeats can carry custom metrics with range alerts. Ours carry an optional failure reason. That lets you alert on what a job did, for example how many records it processed, not just whether it ran.
Real-user monitoring
Cronitor sells web analytics and real-user monitoring. We only run external checks. If you want to know how real visitors experience your pages, that is a different product from ours.
Browser checks
Cronitor can check JavaScript-rendered pages with a real browser on paid plans. We don’t run browsers. Pages that render only with JavaScript can look up to us while broken for visitors.
What PingWise does differently
- Every scheduled check runs from several cities at once, not from one place with a retry.
- The moment one probe sees a failure, every healthy probe checks again, free, before anyone is paged.
- Nothing pages you until two thirds of our 15 probes (10) fail, on at least 3 continents and 3 different providers, two rounds in a row.
- A WAF or Cloudflare challenge is reported as “blocked”, never as down.
- Every alert says what each probe saw: resolved IP, status code, timing and error.
- Prepaid credits, no subscription: 650,000 free every month, packs from €5, bought credits last 24 months.
More comparisons
PingWise vs updown.io · PingWise vs Hyperping · PingWise vs Uptime Kuma · All services side by side
Sources
Compiled from each vendor's own pricing and documentation pages on 26 Oct 2026, linked under Sources. Vendors change plans and features; we re-check quarterly. All product names are trade marks of their owners and are used only to identify them. If you work at one of these companies and something here is wrong or out of date, email [email protected] and we will correct it within one working day.