Monitor websites, APIs, and servers with 23 protocols. Get alerts via Telegram in under 2 seconds. Free forever.
HTTP, TCP, DNS, gRPC, WebSocket, TLS/SSL, WHOIS, SMTP — if it speaks a protocol, we monitor it.
Downtime detected → alert sent. Telegram, Discord, Slack, MS Teams, Mattermost, Email, Webhook, Web Push.
Give your users a live view of service health. Custom domain, your branding, public-facing incident timeline.
Programmatic control over every monitor, alert, and incident. Outgoing webhooks for any state change.
Your job pings PingZen on each successful run. Miss the window — get alerted within seconds.
One monitor, one protocol. Here is what each check really detects, and where its documentation lives.
| Protocol | What it catches |
|---|---|
| HTTP / HTTPS | Response code, response time and a keyword in the body — to tell a live page from a hosting placeholder. |
| TCP / UDP | Whether the port is open. Databases, game servers, VoIP — anything that does not speak HTTP. |
| ICMP Ping | Packet loss and latency to the host. Useful for servers and network gear, useless for a site behind a CDN. |
| DNS | Whether the domain resolves and returns the records you expect. A swapped A record looks like «the site works» — just not yours. |
| TLS / SSL | Days left before expiry, chain completeness, domain match. Thresholds shrink for short-lived certificates. |
| WHOIS | Domain registration expiry. The most embarrassing outage: nobody renewed the domain. |
| WebSocket (WS/WSS) | Whether the connection opens and the server answers a ping frame, not just the handshake. |
| gRPC | gRPC health check, with or without TLS, against a named service. |
| SMTP / IMAP / POP3 | Whether the mail server accepts the connection and greets you over the protocol, STARTTLS included. |
| FTP / FTPS | File server availability, including explicit TLS (AUTH TLS) and self-signed certificates. |
| DNSBL | Whether your mail server's IP or domain landed on a spam blacklist — otherwise mail silently goes to junk. |
| PageSpeed | Core Web Vitals and a page performance score on a schedule, not once by hand. |
| SOCKS5 | Proxy liveness: the handshake plus real traffic passing through, not just an open port. |
| MTProxy | Telegram MTProto proxy availability, secret included. |
| API Check | Status code, shape and field values of the JSON response — not merely «it returned 200». |
| Transactions | A scenario in a real browser: sign in, add to cart, check out. Fails if any step breaks. |
| Heartbeat | Reverse check: your cron job pings PingZen. For backups and servers behind NAT. |
| Timings | Separate DNS, TCP, TLS and TTFB timings on every check — so you can see which hop is slow. |
| Feature | PingZen | UptimeRobot | Pingdom |
|---|---|---|---|
| Free Plan | ✅ Up to 55 monitors | ✅ 50 monitors | ❌ No free plan |
| Fastest Check Interval | 1 minute | 5 minutes | 1 minute |
| Telegram Alerts | ✅ Yes | ❌ No | ❌ No |
| Multi-Location Checks | ✅ Moscow, Novosibirsk, Minsk | ✅ Limited | ✅ Yes |
| Public Status Pages | ✅ Up to 5 | ✅ Paid add-on | ✅ Included |
| API Access | ✅ Yes | ❌ Paid only | ✅ All plans |
| Custom Webhooks | ✅ Yes | ✅ Pro+ | ✅ Yes |
| TLS/SSL Certificate Monitoring | ✅ Yes | ✅ Yes | ✅ Yes |
Detailed comparisons of PingZen with Pingdom, UptimeRobot, Better Stack, Datadog, Zabbix and other monitoring services.
View All Alternatives