Online Tool Store
Network Ping
Run a ping test in your browser to any host. See round-trip latency, jitter, packet loss and min/avg/max on a live chart, then export CSV or JSON.
π This tool runs entirely in your browser. Your files are never uploaded to a server.
Example shown β replace it with your own host or URL.
How the Network Ping works
- Type the host or URL you want to test β a bare name like example.com is enough, and a full https:// address works too.
- Pick how many packets to send (4, 10, 20, 50, 100, or Continuous), how long to wait between them, and the per-packet timeout.
- Press Ping. The tool first sends one discarded warm-up request that pays for DNS, the TCP handshake and the TLS handshake, so those costs are reported separately instead of inflating the first measurement.
- Watch the live chart, the reply list and the min/avg/max/jitter summary update after every packet. In Continuous mode the button turns into Stop, so you can leave it running and end the test whenever you like.
- Copy the full report, or download the per-packet results as CSV or JSON for a ticket, a report or a spreadsheet.
What is actually being measured
A web page cannot send an ICMP echo request β that needs raw-socket access the browser deliberately withholds from JavaScript. So instead of ICMP, this tool times an HTTPS round trip to the host you entered and reports it the same way the ping command reports packets:
round trip = time from issuing the request to the response headers arriving loss = packets with no reply Γ· packets sent jitter = mean of |RTT(n) β RTT(nβ1)| across consecutive replies std dev = β( mean(RTTΒ²) β mean(RTT)Β² )
Because the warm-up request absorbs the one-off setup cost, and because every packet carries a unique cache-busting parameter, the measured packets reflect the network path plus the host's response time rather than a DNS lookup, a TLS negotiation, or a cache answering locally. They will read a little higher than ICMP ping to the same host, since a web server has to process the request as well as receive it.
FAQ
Is it possible to ping a server from the browser?
Not with ICMP. Sending a real ICMP echo request needs raw-socket access, which browsers do not give to JavaScript for security reasons. What a browser can do is time an HTTPS request to the host and report round-trip time, loss and jitter from that β which is what this tool does, from your own device and connection.
How do I ping a website here?
Type the domain into the box β example.com, without any protocol, is fine β and press Ping. The tool sends the packets from your browser to that host and shows round-trip time, packet loss, min/avg/max, jitter and standard deviation as each reply comes back.
How do I ping a URL rather than a bare domain?
Paste the full URL, including the path. The tool pings that exact address, so you can compare a slow page against the site root. It adds a unique query parameter to each packet so a cache cannot answer without a real round trip.
How do I ping a website 100 times?
Set Packets to 100 and press Ping β or choose Continuous, which keeps sending until you press Stop. The summary, the chart and the exports all cover the whole run, so you can leave a continuous test going while you reproduce an intermittent problem.
Can you get a reply from an HTTPS site using the ping command?
The ping command does not speak HTTPS at all β it sends ICMP, which is a separate protocol from the web traffic on port 443. A host can serve HTTPS perfectly while dropping every ICMP packet at the firewall, which is why command-line ping sometimes reports 100% loss for a site that loads fine. This tool measures the HTTPS path itself, so it answers the question command-line ping cannot.
How is jitter calculated?
Jitter here is the mean absolute change between consecutive successful replies β the average of |RTT(n) β RTT(nβ1)|. It needs at least two replies. Standard deviation is shown next to it as the population standard deviation of all successful round trips, so you can see both how much consecutive packets vary and how spread out the whole run was.
What counts as a good ping?
The reference point is ITU-T G.114, which defines three bands of one-way transmission time: 0β150 ms is acceptable for most user applications, 150β400 ms is acceptable provided the impact is understood, and above 400 ms is unacceptable for general network planning. A round trip is roughly twice one-way, so the rating badge treats under 300 ms as good and 800 ms or more as poor. The sub-100 ms Excellent band is a plain rule of thumb, not part of the standard.
Why does every packet show as lost when the site clearly works?
A browser request can be refused for reasons that have nothing to do with the host being down β the name may not resolve, the host may not serve HTTPS, or it may reject the cross-origin request outright. 100% loss here means your browser could not complete a request to that address, not that the site is offline for everyone.
Does this tool send my data anywhere?
No. The test runs entirely in your browser and the requests go straight from your device to the host you typed. Nothing is sent to our servers, no account is needed, and the results only exist on your machine until you copy or download them.
How we compare
| Feature | Online Tool Store | Check-Host.net | DNSChecker.org | Meter.net |
|---|---|---|---|---|
| Measures latency from your own device and connection | β | Their nodes | Their server | β |
| Ping any host or URL you type in | β | β | β | Own server list |
| Runs entirely in the browser β nothing reaches our servers | β | β | β | β |
| Jitter reported alongside min / avg / max | β | β | Std dev only | β |
| Live latency chart while the test runs | β | β | β | β |
| Choose packet count, interval and timeout | β | β | β | β |
| Continuous ping until you press Stop | β | β | β | β |
| Download per-packet results as CSV or JSON | β | Permalink only | β | β |
| Connection setup time (DNS + TCP + TLS) reported separately | β | β | β | β |
Check-Host.net and DNSChecker.org run real ICMP ping, but from their own machines β useful for asking "is this host up from elsewhere in the world?", and no help at all for "is my connection to it slow?". Meter.net measures from your browser like we do, but only against its own servers. Use this tool when the host you care about is one you choose, and the connection you care about is your own.