Online Ping — Check ICMP Replies and Latency
Enter a public hostname or IP address. The server sends exactly four ICMP requests and presents the replies as authentic terminal output.
Enter a public hostname or IP address. The server sends exactly four ICMP requests and presents the replies as authentic terminal output.
Measured from the onlinetoolkit.ch server
ICMP may be filtered by firewalls or the destination. This result shows one route from our server to the target — it does not measure your device’s connection.
Ping sends ICMP echo requests to an IP address. From the replies, this tool calculates round-trip time in milliseconds and counts how many of the four packets received no answer.
A short round trip can be healthy on this server route, but it says nothing about page load time, DNS, TLS, or application load. A working web server may also block every ICMP request.
No. Ping measures ICMP round-trip time to the selected IP address. Download throughput, server processing, DNS resolution, and establishing an HTTPS connection are separate measurements.
No. Zero replies are inconclusive. A firewall may block ICMP, a router may limit responses, the route may be impaired, or the target may really be unreachable. Check the service itself separately.
This measurement starts at the onlinetoolkit.ch server in Switzerland. Your device uses a different provider, location, and often a different route, so latency and loss can differ.
Not necessarily. Some systems give ICMP low priority or rate-limit it. Repeated loss can be a useful clue, but four packets provide only a brief snapshot.
Web browsers cannot send raw ICMP packets. The onlinetoolkit.ch server therefore runs the bounded check and returns normalized numbers only.