ICMP ping monitoring from 10+ global locations. Track latency, packet loss, and reachability for every server, router, and network device in your infrastructure. Works alongside HTTP monitoring for full-stack coverage.
30s
Check interval
10+
Locations
99.9%
Uptime SLA
Global visibility
Each monitor is pinged simultaneously from 10+ locations. Hover a location to see how it connects to your infrastructure.
100
Sent
95
Received
5
Lost
5.0%
Loss %
Beyond up or down
A server can respond to 95 out of 100 pings and still technically be "up." But that 5% packet loss degrades VoIP quality, causes timeouts in API calls, and creates a miserable experience for your users. Most monitoring tools report this as "online."
Pulse Stack™ tracks packet loss per check cycle and alerts you when loss exceeds your threshold. Combined with response time tracking, you get a complete picture of connection quality, not just binary availability.
Set separate thresholds for different device types. A 1% loss threshold for your API servers. A 5% threshold for less critical internal devices. Each monitor gets its own rules.
Different layers of your infrastructure need different types of monitoring. Here is when to use each.
Network layer (Layer 3)
Best for infrastructure devices that don't serve web traffic.
Application layer (Layer 7)
Best for anything serving web traffic or API responses.
Use both for complete coverage. A web server can respond to ping while Apache is crashed. Conversely, a firewall rule can block ICMP while HTTP traffic flows normally. Running both catches what either would miss alone.
Network health
Group servers by environment, region, or function. See latency trends, packet loss rates, and uptime percentages at a glance. Drill into any device for full check history.
Combine ping monitors with port checks to verify that specific services (MySQL on 3306, SSH on 22, Redis on 6379) are responding on each server. The device is reachable, and the service is running.
All monitor types share the same incident management system and status pages, so ping failures trigger the same escalation workflows as your HTTP monitors.
Binary up/down monitoring is just the starting point. These three measurements tell you the full story of your connection quality.
Alert at 2x your baseline
The time it takes for a packet to travel to a destination and back. High latency causes sluggish page loads, slow database queries, and laggy real-time applications. Pulse Stack™ tracks latency per location and alerts on sustained increases that indicate network degradation.
Alert above 20ms variance
The variation in latency between consecutive packets. Low, consistent latency is better than fast latency that fluctuates wildly. High jitter destroys VoIP call quality, interrupts video conferencing, and makes real-time collaboration tools unreliable.
Alert above 1% loss
The percentage of packets that never arrive at their destination. Even 1% loss causes TCP retransmissions that multiply latency, degrade throughput, and can trigger cascading timeouts across distributed systems that depend on each other.
Enter an IP or hostname. We start pinging from 10+ locations immediately.
Every web request, API call, database query, and email delivery depends on network connectivity. When a router drops packets or a switch fails, the cascading effects touch every application on that network segment.
Ping monitoring catches these infrastructure-level failures that application monitoring cannot. A web server might appear healthy on localhost while being completely unreachable from the outside due to a network issue.
Network failures rarely happen instantly. Latency creeps up. Packet loss starts at 0.1% and grows. Jitter increases as a switch struggles. These early warning signs are visible in ping data long before a complete outage occurs.
By tracking latency trends over time and alerting on gradual increases, you can replace failing hardware or address routing issues during business hours instead of scrambling at 3 AM during a full outage. Pair this with DNS monitoring for complete visibility.
Your hosting provider promises 99.99% network uptime. But how do you verify that? Ping monitoring from external locations gives you independent proof of actual availability and latency performance against your SLA agreements.
Use our SLA calculator to convert uptime percentages into real downtime minutes, then let Pulse Stack™ track whether your infrastructure actually meets those targets. Historical data exports make SLA reviews straightforward.
50 monitors free forever. Upgrade when you need faster checks or more capacity.
Most popular
£29/month
All plans include multi-location checks, incident management, and public status pages. Full plan comparison →
Ping monitoring is the network layer. Add these for full infrastructure visibility.
Everything you need to know about ICMP ping monitoring.
Ping every server, router, and device from 10+ locations. Free for 50 monitors, no credit card required.
Start ping monitoring free