ICMP ping checks
Confirm a host is alive and responding to ping, with response-time tracking — the simplest health check for any server.
Beyond websites, PingWise watches your infrastructure. Confirm a host is alive by ICMP ping, or that a specific TCP port is open and accepting connections — SSH, MySQL, RDP, SMTP and anything else — and get alerted the moment it stops responding.
Confirm a host is alive and responding to ping, with response-time tracking — the simplest health check for any server.
Verify a port is open and accepting connections: SSH (22), MySQL (3306), RDP (3389), SMTP (25) — or any port your service uses.
Every check records response time and up/down, with uptime percentages over 24 hours, 7 days and 30 days.
A server only flips to DOWN after a few confirmed failures, so a momentary network blip never triggers a false alarm.
Email, SMS, Slack, Microsoft Teams, Discord, Telegram, webhook and ClickUp — with recovery notices too.
Servers and websites share the same monitor limit — mix and match however you like, on any plan.
Server monitoring checks that your server or host is reachable and its services are responding. PingWise does this from the outside using ICMP ping or a TCP port check, and alerts you when a host goes unreachable or a port stops accepting connections.
A ping (ICMP) check confirms the host itself is alive on the network. A TCP port check goes further and confirms a specific service — such as SSH, MySQL or a web server — is actually listening and accepting connections on its port.
Any TCP port. Common ones include 22 (SSH), 3306 (MySQL), 5432 (PostgreSQL), 3389 (RDP), 25/587 (SMTP) and 443 (HTTPS), but you can enter any port your service uses.
No — websites and servers share one simple monitor limit on every plan, so you can mix and match. Start free with up to 2 monitors, no credit card.