Fusion Proxy
LoginGet Started

Free Network Tool

Ping a host online

Measure round-trip latency from our infrastructure to any public IP or hostname. Useful for sanity-checking a server before pointing traffic at it, or comparing how a host responds from outside your own network.

1–10 probesTCP-based — works behind firewallsLive results, min & avg & maxPer-IP rate limited

Hosts that resolve to private, loopback, or link-local addresses are not allowed.

When ping is the right tool

Ping answers a simple question: how fast can a small probe travel from us to a host and back? That makes it a fast, low-fidelity health check — great for catching obvious routing or uptime issues before reaching for tcpdump or traceroute.

Verify a host is reachable

If every probe times out, the host is either down, firewalled, or unreachable from our network.

Spot routing changes

A sudden jump in average latency often means traffic has been re-routed through a slower path.

Compare against your own network

Run the same check from your own machine to see whether a delay is local or upstream.

Set a baseline before deploying

Knowing the typical RTT to a server lets you alert on regressions later.

How this ping is performed

  1. You submit a hostname or IP. The form runs basic syntax checks before posting to our edge.
  2. We resolve and validate the target. A public DNS resolver looks the host up and the result is checked against a block-list of private and reserved ranges.
  3. We send a small number of probes. Each probe opens a brief connection to the host and times the handshake, which avoids the firewall issues that plain ICMP ping suffers from.
  4. You see the results live. We stream each probe back as soon as it completes, then show a final min/avg/max summary.

Frequently asked questions

Why does this use TCP probes instead of ICMP?
ICMP is filtered or rate-limited by many networks, which would make this tool unreliable. A TCP handshake to a common port reaches a similar answer with fewer false negatives.
What does “100% loss” mean?
Every probe timed out before the host responded. The host is likely offline, firewalled to drop our traffic, or unreachable from our network at the moment.
Can I ping internal hosts on my network?
No. Targets that resolve to private (RFC1918), loopback, link-local, or reserved addresses are refused. Internal pings should be done from inside your own network.
Why is my ping different from the result on this page?
Latency depends on the path between sender and target. Your local network sees a different path than ours, so values will differ.
How many probes can I send?
One to ten per request. The tool is rate-limited to keep it fair to share publicly.
Do you store the host I tested?
Only counters required for rate limiting. The submitted hostname is not associated with your account or kept beyond the request.

Need stable, low-latency proxies?

Our datacenter and ISP plans give you tight RTT alongside clean reputations.

See plans