Server Latency Checker

Measure real round-trip latency to any server with repeated TCP connect timing - min/avg/max, jitter and connection loss, plus a best-effort ICMP ping.

Times 8 real TCP connect attempts against the port you choose (default 443). Also attempts one ICMP ping as a bonus signal - many networks block this entirely.

Enter a host and port to measure round-trip latency.

Not checked

Run a check to see latency and connection stability.

Average — mean of successful attempts

Min / Max — fastest and slowest attempt

Jitter — variation between attempts

Connection Loss 0% attempts that failed

📊 Individual Attempts

Each row is one independent TCP connect attempt, in order.

Attempt Result Time

📡 ICMP Ping (Bonus)

Reachable

—

Round-Trip Time

—

Note

—

📋 Query Details

Host

—

Resolved Address

—

Port

—

Checked At

—

📦 Raw API Result

This tool measures TCP connect time rather than ICMP echo by default, because most cloud hosting blocks outbound ICMP entirely - an ICMP-only tool would report "unreachable" for the majority of real servers even when they're working perfectly. TCP connect time is a genuine latency number in its own right: it's the same handshake a browser or API client pays before any data can flow.

HOW IT WORKS

Eight Real Connections, Timed Individually

This tool opens eight independent TCP connections to the host and port you choose, timing each one with a stopwatch from the first SYN to the completed handshake, with a short pause between attempts. From those eight real numbers it reports the minimum, average and maximum round-trip time, plus jitter - the average change in latency between one attempt and the next, the same definition used by the Global Ping Test - and how many attempts failed outright. A single best-effort ICMP echo is attempted afterward purely as a bonus data point; if it's blocked or unavailable in this hosting environment, that's reported honestly rather than treated as a failure, since the TCP-based numbers above are unaffected either way.

What else can you check?

These tools all work on the same connection and address data — pick whichever question you actually have.

Want to see the full path to a site? DNS, redirects, every hop, the CDN, TLS and the origin server. Want to know your public IP? See your IPv4 and IPv6 addresses, location, ISP and ASN. Want to check your tower & route? Live ping, speed, DNS, traceroute and a map of nearby points. Want to ping from around the world? Real latency from real probes across 12 countries, live on a map. Want to locate any IP address? City, region, country and coordinates for any public IP. Want to know if an IP is risky? Proxy, VPN, Tor, hosting and abuse-report indicators. Want to know if you're blacklisted? Check an address against major spam and abuse DNSBLs. Want to know who owns an IP? Network owner, ASN, CIDR range and abuse contact. Want to explore an AS number? Announced prefixes, BGP neighbours and registry details. Want to test your connection speed? Measure real download, upload, ping and jitter. Want to see what changed? Word-level diff between two blocks of text or code. Want to know if a DNS change is live yet? Compare answers from five independent public resolvers. Want to verify a domain's nameservers? Direct authoritative checks, glue records and SOA serials. Want to check a domain's DNSSEC setup? DNSKEY, DS records, signature expiry and real validation. Want to see the hop-by-hop path to a server? A real traceroute from a genuine probe anywhere in the world. Want to know if a server port is open? A real TCP connection attempt - open, closed or filtered. Want a clean URL slug from a title? Real transliteration, stop words and batch mode. Want to find and replace across a document? Regex, capture groups and a live preview before you commit. Want to find the invisible character? Code points, escapes, bytes and hidden-character detection. Want to escape text for HTML? Minimal, named or numeric entities, attribute-safe. Want to strip emoji cleanly? Whole clusters - no half-flags or stray modifiers left. Want to spot repeated words? Frequency, density and accidental doubles like "the the".

COMMON QUESTIONS

Server Latency Checker FAQ

Why TCP connect time instead of a normal ping?

A normal ping uses ICMP, which most cloud providers and many corporate networks block outbound entirely. TCP connect time to an actual open port is measurable almost everywhere and reflects a real cost - the same handshake your browser pays before any data is exchanged.

What does "ICMP not available in this environment" mean?

Either the target/network is blocking ICMP echo requests, or this server's own hosting environment doesn't grant the raw-socket privilege ICMP needs on Linux. Either way, it's reported honestly rather than guessed, and the TCP-based numbers are unaffected.

Why does jitter matter?

Average latency alone can hide an inconsistent connection. High jitter (large swings between attempts) is often more disruptive for real-time uses like calls or gaming than a slightly higher but stable average latency.

What port should I check?

443 (HTTPS) works for most public web servers and is the default. Use 80 for a plain HTTP-only server, or whatever port the specific service you care about actually listens on.