For side projects
Free plan
5 more monitors and twice as many status pages. Still $0.
SurePing watches your sites, APIs, ports, certificates and cron jobs around the clock, and tells you first. Fifty-five monitors free, then from $9 a month.
| Monitor | Type | Last 24 hours | Uptime | Response |
|---|---|---|---|---|
API api.acme.io/health | HTTP(S) | 200 OK | 99.98% | 41 ms |
Checkout acme.io/checkout | Keyword | “Pay now” present | 99.99% | 88 ms |
Postgres primary db-primary.acme.io:5432 | Port | TCP open | 100% | 12 ms |
Edge — eu-west 203.0.113.24 | Ping | Request timed out | 98.21% | — |
acme.io certificate acme.io | SSL | Expires in 12 days | 100% | — |
Nightly backup heartbeat / cron | Heartbeat | Pinged 4 min ago | 99.87% | — |
10% more monitors, plan for plan
Start with 55 free. Move to 60-second checks for $10 a month.
Every monitor type is on every plan, including the free one. Nothing here is gated behind an upgrade.
Status codes, response time and redirects on any URL. Custom method and headers.
Alert when a string appears — or stops appearing — in the response body.
ICMP reachability for hosts that do not speak HTTP.
TCP checks on SMTP, POP3, FTP, database and game-server ports.
Expiry warnings ahead of time, on a threshold you set. Default 14 days.
Your job pings a URL when it finishes. Silence raises the alert.
A failed check is retried before anyone gets woken up — twice by default, on a timeout you set per monitor.
203.0.113.24 · Ping
error request timed out after 10s
confirmed after 2 retries · previous check 99.98% over 30d
Down and recovery notices, per monitor.
For the alerts that must wake somebody up. Monthly credits renew every billing cycle. Pro & Business can also use credits for WhatsApp.
Rich Block Kit messages in any Slack channel.
Coloured embed alerts in your Discord server.
Adaptive Card alerts in your Teams channel.
Trigger and auto-resolve incidents via Events API v2.
Alerts straight to WhatsApp, sharing your SMS credit pool. Pro & Business only.
Straight into a personal or group chat.
POST the incident payload to any HTTP endpoint you control.
Publish uptime and incidents on your own domain, so the people asking can check for themselves.
Point a CNAME at us and the page serves on status.yourcompany.com.
Your logo, your description, and your own display name for each monitor.
Password-protect a page for customers, or keep it internal entirely.
Every incident, with its cause and how long it ran, published automatically.
A simple plan-for-plan comparison: 10% more monitors, the same check speed, and a lower displayed monthly price when you upgrade.
For side projects
5 more monitors and twice as many status pages. Still $0.
For faster checks
One extra monitor, with a lower month-to-month price.
UptimeRobot figures checked on 3 August 2026 against its pricing page. Both paid prices are month-to-month: SurePing Starter is $10 and the UK/EU UptimeRobot session showed Solo at €13. UptimeRobot localizes its currency and defaults to annual billing, where this session showed €12 per month billed as €144 per year. No exchange-rate conversion is implied.
Independent buyer's guides and practical monitoring tutorials — from the team that builds SurePing.
Nine alert channels — including Slack, Discord, Teams, PagerDuty and WhatsApp — are available on every plan. Paid plans unlock more SMS credits, alert contacts and premium integrations.
More free monitors than UptimeRobot gives you, permanently.
Free forever, no card required
Minute-by-minute checks for a handful of critical services.
Billed $108 once a year
The tier most teams need, at roughly half what it costs elsewhere.
Billed $228 once a year
Fifteen-second checks for agencies and larger estates.
Billed $468 once a year
SMS and WhatsApp alerts use monthly credits that reset each billing cycle and do not roll over (11 on Starter, 33 on Pro, 55 on Business). Email, Telegram and webhook alerts are unmetered. Premium integrations (Slack, Discord, Teams, PagerDuty, WhatsApp) are limited to 1 on Free and 2 on Starter — unlimited on Pro and Business.
There is nothing to install and nothing to deploy.
Email and a password. No card, no sales call, no trial countdown.
Paste a URL, host or hostname and port. Pick an interval and a timeout, or take the defaults.
Your email is already there. Add SMS, Telegram or a webhook, and choose whether recoveries notify too.
Create a heartbeat monitor and you get a token URL. Have the job call it on success. If the ping does not land inside your window, we open an incident and alert you — the same as any other monitor going down.
Set one up# crontab # nightly backup, pings on success 0 3 * * * /opt/backup.sh && \ curl -fsS https://www.sureping.cc/api/heartbeat/$TOKEN
Six monitor types: HTTP(S) endpoints, keywords in a response body, ICMP ping, TCP ports, SSL certificate expiry, and heartbeat (cron) jobs that ping us when they finish. Every type is available on every plan, including the free one.
The free tier runs efficient 5-minute checks and is sized for personal projects and small sites. Paid plans fund the faster checks, additional capacity, storage, and support that larger estates require. Features stay available on every plan; paying gets you capacity and speed, not an artificially unlocked dashboard.
Every 5 minutes on Free, every 60 seconds on Starter, every 30 seconds on Pro, and every 15 seconds on Business. You can set a slower interval per monitor if a target is rate-limited.
Nine channels: Email, SMS, Slack, Discord, Microsoft Teams, Telegram, WhatsApp, PagerDuty, and generic webhooks. Eight channels are available on every plan; WhatsApp is unlocked on Pro and Business. SMS uses monthly credits that reset each billing cycle (11 on Starter, 33 on Pro, 55 on Business). On Pro and Business, WhatsApp alerts draw from the same credit pool as SMS. Email, Telegram, and webhook alerts are unmetered.
A failed check is retried before it becomes an incident — twice by default, configurable per monitor, alongside a per-monitor timeout. A single dropped packet will not page you.
Not yet — checks currently run from a single region. If you need multi-region confirmation to rule out regional routing faults, we are not the right tool today, and we would rather tell you that than let you find out during an incident.
Yes. Point a CNAME at us and the page serves on your domain with your logo and your own display names for each monitor. Pages can be public, password-protected, or fully private.
Create a heartbeat monitor and you get a unique URL. Have the job curl it on success. If the ping does not arrive inside the window you set, we open an incident and alert you.
Existing monitors keep running. You will not be able to add more until you remove some or move up a plan, and we do not bill you for the overage automatically.
Set up the first one now and find out about the next outage before your customers do.
Start monitoring free