Help / Ping
Ping
Measures how long packets take to reach a host and come back, and how many get lost, from real probes around the world, from our server, or from your own browser.
How to use it
- Type a hostname or public IP address.
- Pick where to ping from: near you, a region, worldwide, or our server. You can also type any location, like a city, a US state (US-NY), a network (AS13335) or a cloud (AWS).
- Press Ping. Probe results fill in live over a few seconds; the page link then points at the saved result, so you can share it.
- Under “From your computer”, test from your own browser, or copy the ping command for your system.
Reading the results
- Round-trip time (ms)
- How long one packet takes to get to the host and back. Under 30 ms is nearby; 100+ ms usually means another continent.
- Min / Avg / Max
- The fastest, average and slowest of the packets sent. A big gap between min and max means jitter.
- Loss
- Packets that never came back. Any steady loss to the destination itself is worth looking into.
- ICMP
- Classic ping. Some hosts and firewalls ignore it, which shows as 100% loss even when the host is up.
- TCP
- Times opening a connection to a port (443 for websites). Works where ICMP is blocked.
- Our server
- A TCP connect test from the Cloudflare data center handling your request, usually the one closest to you.
- Probe
- A computer in the Globalping network that runs the test. Each row is one probe.
Examples
- cloudflare.com Ping from probes near you
- 8.8.8.8 Google’s DNS, usually very close to everyone
From the command line
curl "https://tools.nexayori.com/ping?q=cloudflare.com" curl "https://tools.nexayori.com/ping?q=cloudflare.com&format=json"
| q | Host or public IP to ping |
| from | near (default), world, server, a region (Europe), country, city, US-NY, AS13335, AWS… |
| proto | icmp (default) or tcp |
| port | TCP port (default 443); also used with from=server |
| id | A saved result ID |
| format | text (default for curl), json, or html |
Questions
Why 100% loss when the site loads fine?
The host ignores ICMP ping. Switch Protocol to TCP (port 443), which is what a browser uses.
Why is the browser test slower than ping?
It times full HTTPS requests, so each sample includes the server handling the request. The first one also includes DNS, connection and TLS setup.
Why can’t our server ping some hosts?
Cloudflare doesn’t let code on its servers open raw connections to its own network, so sites on Cloudflare can’t be tested “from our server”. Use a probe location.
Can I ping my router or a 192.168.x.x address?
Not from here: those addresses only exist inside your network. Use the command for your computer instead.
Limitations
- Web pages can’t send real pings; the browser test times HTTPS requests instead.
- Probe results are public to anyone with the result link, for about six months.
- Shared hourly limits apply; heavy use may be asked to wait.