Online Ping Test Ping a Website or Server From Multiple Locations
Ping any website, server or IP address from locations around the world. This free online ping test sends real ICMP echo requests from each location and shows the average latency, packet loss and the IP address that answered.
At a glance
- Real ICMP ping: 5 echo requests of 32 bytes from each location, with a 2-second timeout.
- Results per location: average latency, packet loss and the resolved IPv4 address.
- Multiple locations at once: compare up to 3 locations side by side without an account.
- Host names or IPs: enter
example.comor an IPv4 address; the name is resolved at each location. - DNS errors reported: if a location can't resolve the name, you see that instead of a timeout.
- Free: no sign-up; export results as PDF, CSV or JSON.
How to ping a website online
- Enter a host name, such as
www.example.com, or an IPv4 address. Enter the host only, not a full URL. - Select up to three locations.
- Click Run Test. Results appear within seconds.
How the ping test works
Ping uses ICMP (Internet Control Message Protocol) echo requests. The host replies to each request, and the time between sending and receiving is the round-trip time (latency). From each location, Dotcom-Tools sends five packets at once and waits up to two seconds for each reply. Packets that time out count as 2,000 ms in the average, so partial packet loss is clearly visible; if no packet comes back, the average is shown as N/A with 100% loss.
What is a good ping?
| Round-trip time | Rating | Typical situation |
|---|---|---|
| Under 30 ms | Excellent | Server in the same city or region |
| 30–100 ms | Good | Same continent |
| 100–200 ms | Acceptable | Across an ocean |
| Over 200 ms | Slow | Long or congested route, or satellite links |
Any packet loss above 0% on a stable connection is worth investigating.
Why ping from multiple locations?
Pinging from your own computer only tests one path. A global ping test from several locations shows whether a host is down everywhere or only unreachable from one region, and how latency grows with distance. That helps you separate a server problem from a network or routing problem, and choose where to host or which CDN regions to use.
Ping fails but the website works?
Many servers, firewalls and cloud load balancers block ICMP on purpose. If the ping test shows 100% loss but the site loads in a browser, the host simply doesn't answer ping. Use the Web Server Test to check the website over HTTP instead, or the Traceroute Test to see how far packets get.
Related free tools
- Traceroute Test: see each hop on the way to the host and where latency or loss starts.
- Web Server Test: check HTTP availability and server response time.
- Website Speed Test: measure the full page load in a real browser.
To ping your servers continuously with alerts on downtime and latency, see Dotcom-Monitor.
Frequently asked questions
What is a ping test?
A ping test sends small ICMP echo packets to a host and measures how long the replies take (latency) and how many are lost (packet loss). It is the quickest way to check whether a server is reachable and how far away it is in network terms.
Does this test my own internet connection?
No. This ping test runs from Dotcom-Tools' test locations to the host you enter, so it measures the latency between those locations and your server. To test your own connection, use an internet speed test.
Why does ping show 100% packet loss?
Either the host is down or unreachable, or it blocks ICMP. Many servers and firewalls drop ping on purpose. If the website loads in a browser, run the Web Server Test to check it over HTTP.
What is a good ping time?
Under 30 ms is excellent and typical within a region, 30–100 ms is good within a continent, and 100–200 ms is normal across oceans. Above 200 ms, interactive applications start to feel slow.
Can I ping an IPv6 address?
Not yet. The ping test supports host names and IPv4 addresses.
How many packets does the ping test send?
Five 32-byte ICMP echo requests from each location, sent at the same time, each with a two-second timeout.
Last updated: