← My IP
Reachability
Ping
Five ICMP requests from our server to a host or an IP address: whether it answers, how fast, and whether packets get lost. By default the field holds your own address, so you can see if it responds to ping from the outside.
nothing pinged yet
The requests are sent from our server in Nuremberg, Germany, so the times show the path from there to the host, not from your device. Your own latency is measured on the speed test page.
| # | Time | TTL |
|---|
Raw output
What the numbers mean
- Response time
- Round trip from our server to the host and back, in milliseconds. A few ms means the same data centre, 20–40 ms the same region, 100 ms and more another continent.
- Packet loss
- Requests that got no answer within two seconds. Occasional loss on a long path is normal; steady loss points to an overloaded link or a firewall dropping some ICMP.
- TTL
- Time to live left in the reply: each router on the way subtracts one. Starting values are usually 64, 128 or 255, so 64 − TTL, 128 − TTL or 255 − TTL is roughly the number of hops.
- No reply
- The host may be down, may not exist at that address, or may simply ignore ping — many servers and home routers do. No reply to ping does not mean a site is unavailable.
Ping questions
- Where does the ping come from?
- From our server, not from your device — browsers cannot send ICMP. The result shows the path from our data centre to the host. To measure your own connection use the speed test.
- My IP does not respond to ping — is that bad?
- No. Many routers and providers block incoming ICMP by default, and nothing stops working because of it. Some people even prefer it: a silent address draws less attention from scanners.
- Why is the time so high?
- Distance is the main factor: light in fibre needs about 5 ms per 1000 km one way, plus router hops. Satellite links, mobile networks and VPN detours add tens of milliseconds more.