Online Ping Test — Check Latency to Any Host

Measure how fast a server responds: enter a host and get the round-trip latency, jitter and failed attempts over several pings — measured from our server with a TCP ping to the port you choose.

Runs on our server

This tool fetches the public URL you enter from our server. Results are held in temporary memory for a few minutes and never stored in a database.

How to use the Ping Test

  1. Enter a domain (example.com) or a public IP address.
  2. Keep port 443 for websites, or choose another port the server listens on (80 for HTTP, 22 for SSH, 25 for mail).
  3. Click Ping. Each attempt measures how long the server takes to accept a TCP connection.
  4. Read average, minimum and maximum latency, jitter (how much the latency varies) and the share of failed attempts.

TCP ping vs classic ping

The classic ping command sends ICMP echo packets. Cloud servers — like the one running this tool — can’t send raw ICMP, and many hosts block ICMP anyway. This tool uses a TCP ping instead: it measures how long the target takes to complete a TCP handshake on a real service port (443 by default). For web servers that’s often more meaningful, because it tests the path your visitors actually use.

Reading the results

ValueWhat it meansGood
Latency (avg)Round-trip time to open a connection< 50 ms same region, < 150 ms across continents
JitterAverage change between consecutive pings< 10 ms
FailedAttempts that timed out or were refused0%

Latency is measured from our server’s data center, so it reflects the distance between that location and the target, not your own connection. A website on a CDN usually answers from a nearby edge and shows very low latency.

Troubleshooting

  • Refused — the host is reachable but nothing listens on that port. Try 80 or 443.
  • Timeout — a firewall drops the packets, or the host is down. Check with the Port Checker and the Website Down Checker.
  • Doesn’t resolve — check the domain’s records with DNS Lookup.

Tools that pair well with the Ping Test

  • DNS Propagation Checker — Changed DNS or moved a site to Webflow?
  • SSL Checker — Verify an HTTPS certificate in seconds — see when it expires, who issued it, which hostnames it covers and whether the chain is trusted.
  • SPF, DKIM & DMARC Checker — Find out why emails land in spam.
  • WHOIS Lookup — Enter a domain to see its registrar, creation and expiry dates, domain age, status codes, nameservers and DNSSEC — or an IP address to find the network and organisation that owns it.

Frequently asked questions

Why does this ping use TCP instead of ICMP?
Serverless cloud environments can’t send raw ICMP packets, and many networks block ICMP. A TCP ping measures the time to open a real connection on a service port, which closely matches what users experience.
Where is the ping sent from?
From the data center that runs our server (shown in the results). To test latency from your own computer, use the ping command in your terminal.
Can I ping private or local IPs?
No. For security, private, local and reserved addresses (like 192.168.x.x or 10.x.x.x) are blocked.
What is a good ping?
Under 50 ms is excellent within the same region, 50–150 ms is normal across continents, and anything consistently above 200 ms or with high jitter can cause slow pages or laggy calls.

Related tools