Online ping test
Measures latency and packet loss to a domain or IP address. The measurement is taken from the IPVIEW origin nearest you — inside Iran for visitors there, in Germany for everyone else — and the vantage point is written under every result, so the number means what it says.
Need another tool?
Pick one of the 25 belowOutput
What the online ping test measures
This online ping test sends four ICMP echo requests to a domain or IP address, 0.4 seconds apart, waiting up to two seconds for each reply, and reports packet loss and the minimum, average and maximum round-trip time. The packets leave from the IPVIEW origin nearest you, the server inside Iran for visitors there and the server in Germany otherwise, and the vantage point is written under every result, because a latency without the end it was measured from is not a number anyone can act on.
A name is resolved to its IPv4 address first and the address pinged is on the page; to test IPv6, enter the IPv6 address itself, which answers only when the IPVIEW origin has an IPv6 route; otherwise the result says there is no route. Reserved addresses are refused. Four packets is a sample, not a study: it says whether the host answers and roughly how far away it is, not how the path behaves over a minute, which is what MTR is for.
How to read the result
Packet loss matters more than the average. The average is computed over the replies that arrived, so a host that answered one packet of four at 92 ms shows a flattering 92 ms beside 75% loss, and the loss is the finding. With four packets the smallest loss this test can report is 25%, so any loss at all goes in the headline. The spread between minimum and maximum is jitter, which matters for calls more than for pages.
No reply at all is not the same as down. Many hosts and most cloud firewalls drop ICMP on purpose while serving perfectly well on their ports, and the banner says so. The round trip is bounded by distance: from Iran to Europe, 60 to 120 ms is physics, not a fault; from Iran to a server in Iran, under 30 ms is ordinary. The raw output of the ping command sits under the table.
When it is useful
A site is slow for users in Iran and fine from abroad. Visitors in Iran see the latency from inside Iran here; a large difference from the Germany view points at the path, not the server. If the host answers from one side and not the other, the Reachability check on the domain says whether the name is filtered.
Before blaming a server, to see whether it answers at all and how far it is. When loss appears, Traceroute finds the hop where the path breaks and MTR measures each hop many times to tell a lossy link from a router that merely rate-limits its replies. For a host that drops ICMP, Check one port on 443 or 22 still works.
Common questions
What is a good ping?
It depends on distance: inside one country under 30 ms, across a continent 60 to 120 ms, across an ocean 150 ms and more. The round trip cannot beat light in fibre, so judge the number against where the server is, and judge loss before average.
Why does ping get no reply when the site works?
The host or a firewall in front of it drops ICMP echo requests on purpose, which is common and says nothing about its ports. Use Check one port on the port the service uses, or the Reachability check for a website.
Ping or MTR?
Ping for a quick yes-or-no and a rough latency from four packets. MTR when there is loss or jitter to explain, because it measures every hop five times and shows where the loss begins.
Is the ping test run from inside Iran?
For visitors inside Iran, yes: the packets leave from the IPVIEW server in Iran. For visitors elsewhere they leave from Germany. The result says which, and a saved result carries the vantage point with it.
Limits. The DNS, WHOIS and SSL tools allow up to 20 requests a minute per IP address. Ping, traceroute and MTR send real packets to their target, so they allow 6 a minute.
The port check runs only against your own IP address. That is deliberate: the question people actually have, "is this port reachable from outside?", is answered by it, while this server cannot be used to scan anyone else's network.
Private and reserved addresses. These are refused by the tools that really connect to their target: the SSL check, ping, traceroute, MTR and the port check. The DNS tools have no such limit, because they only ask a nameserver a question and never connect to the address itself.