Network

Online Ping Test

ICMP ping to any host from our server — round-trip latency and packet loss.

About Ping

Sends ICMP echo requests from our server to any host and reports round-trip latency and packet loss. Because the ping originates from a different network than your own connection, it isolates whether a reachability problem is specific to your local network path or a genuine issue with the target host.

Packet loss over multiple pings is often a more useful signal than a single latency number, since intermittent loss is what actually causes application-level timeouts and stalls. Standard first step for any "is the server even up" question, and a quick way to rule out basic network reachability before digging into application-layer debugging.

📖 Read more in our Knowledge Base →

Packet loss over multiple pings is often a more useful signal than a single latency number, since intermittent loss is what actually causes application-level timeouts and stalls. Standard first step for any "is the server even up" question, and a quick way to rule out basic network reachability before digging into application-layer debugging.

Note

Ping runs from our server in Germany. Latency reflects server-to-target, not your browser-to-target.

Related Tools

How to read the result

  • Round-trip time (RTT): time for one echo request to reach the host and come back. Within a continent, 1–40 ms is normal; across an ocean, 70–200 ms; satellite links add 500 ms or more.
  • Packet loss: 0% is the expectation. Occasional single losses happen; steady loss of a few percent is enough to make calls and video stutter and TCP slow down.
  • Jitter: the spread between the lowest and highest RTT. A wide spread points to congestion somewhere on the path.

The tool sends 1 to 10 echo requests (4 by default) from our server. Enter a hostname or an IPv4 address.

"100% loss" does not always mean down

Many hosts and firewalls drop ICMP on purpose. Cloud security groups, Windows Firewall and many corporate edges block echo requests by default while the web server keeps working. If ping fails, test the service itself: an HTTP status check for a website or a port check for anything else.

Next step when ping looks bad

Ping tells you that something is wrong, not where. Run a traceroute or an MTR to the same host to see which hop the latency or loss starts at. If loss appears at one middle hop but not at the hops after it, that router is only rate-limiting ICMP replies to itself; it is not losing your traffic.

Testing from your own machine

  • Windows: ping -n 20 example.com
  • macOS / Linux: ping -c 20 example.com

Compare both results. Good from our server but bad from yours means the problem is on your side of the path: Wi-Fi, home router or your provider.