ICMP reachability
Send echo requests to the target and check whether it answers. The result is a useful signal for servers, routers and other public devices that permit ping.
Is it reachable?
Get a clearer answer.
Watch network reachability with ICMP checks from your selected regions. Follow latency, packet loss and regional differences for the machines and devices you depend on.
Part of your Upty workspace · One workspace. Every signal.
RESPONSE TIME24 ms
- Target
- edge.example.com
- Reachability
- Responding
- Average latency
- 24 ms
- Packet loss
- 0%
When a host stops answering, you need to know whether the problem is the application or the path to the machine. Ping monitoring provides a focused network-level signal that sits alongside your HTTP and port checks.
Use a hostname or IP address, choose your probe regions and inspect the latest packet statistics. Regional results help you see when one route behaves differently from the others.
Keep this signal alongside the rest of your stack: organize related services, choose who receives alerts and follow recovery in the same workspace. The goal is a check that explains what changed and gives the right person a useful place to start.
SMALL DETAILS. USEFUL CONTEXT.More than
More than
an up or down.
Purpose-built checks.
Information you can act on.
Latency over time
Follow response-time history to see how network responsiveness changes. Compare patterns instead of relying on a single ping from your own laptop.
Packet statistics
Inspect sent and received packets, packet loss, minimum and maximum latency, average latency and jitter in the latest check details.
Regional differences
Compare the latest result from each chosen region. A reachable machine can still have an issue along one route, which is useful context when reports seem inconsistent.
Failure details
When available after a failure, network-path details give additional context about the route and whether the destination was reached. Use that context to guide further diagnosis.
Consecutive failure control
Choose how many failed checks in a row should trigger an alert. This helps your alert policy reflect how you want to treat brief network loss.
WHERE IT FITSMade for the work
Made for the work
you already do.
One reliable signal.
Plenty of practical uses.
Public infrastructure
Monitor machines and devices that are expected to answer ICMP. Keep the check separate from application monitoring so the two signals are easy to compare.
Regional reachability
See how a target responds from the locations you selected. Compare probe results before assuming that a problem seen from one network is universal.
Network investigations
Use packet loss and latency details as a starting point. Pair them with port or HTTP checks to determine whether the reachable machine is also serving traffic.
FROM SETUP TO A USEFUL SIGNALStart with what
Start with what
matters most.
Use a meaningful name, choose the behavior you expect and make sure the alert reaches someone who can act. Start with one service, then add the related checks as your monitoring grows.
Open the setup guide- 01
Choose your starting point.
Create a Ping monitor with a friendly name and the public hostname or IP address you want to check.
- 02
Configure the check.
Choose the interval, probe regions and consecutive failure setting. Confirm that the target allows ICMP traffic.
- 03
Follow the signal.
Choose alert channels and review the packet and response-time details as checks arrive. Add a service-level monitor for the application itself.
A LITTLE MORE CONTEXTGood questions.
Good questions.
Clear answers.
The details that help you choose the right check and get a useful result.
Read the full documentationDoes a successful ping mean the website works?+
No. Ping confirms network-level reachability. Use website or API monitoring to validate an HTTP response, or port monitoring to check a TCP listener.
Why is a working server always down?+
The target or a firewall may block ICMP. If blocking ping is intentional, use a suitable port or HTTP monitor rather than changing the firewall only to satisfy the check.
Can I use a hostname?+
Yes. Ping accepts a hostname or an IP address. Use the IP monitor if you want an address-only check without hostname resolution.
What if just one region fails?+
Inspect the latest details from that region and compare the others. Routes differ, so one failed probe can reflect a path-specific problem.
How do I reduce alerts for brief packet loss?+
Review the consecutive failure setting and choose a suitable interval. Requiring more than one failed check can filter isolated failures, with a corresponding delay before an alert.
LESS CHECKING. MORE KNOWING.One more thing
Get started One more thing
off your mind.
Bring ping monitoring into your workspace.