Ping Tool

Ping any host with TCP handshake or HTTP TTFB measurement from Cloudflare's edge network. View real-time latency chart, average/min/max statistics, and jitter analysis.

Was this tool helpful?

How to Use

Measure network latency to any host using TCP or HTTP ping:

Enter a hostname or IP — Type a domain name (e.g., google.com) or IP address (e.g., 8.8.8.8). Select a port from the dropdown — 443 (HTTPS) is the default. Use the quick-try buttons to test common targets.
Choose ping mode — TCP mode measures the TCP handshake round-trip time using Cloudflare Workers' connect() API. HTTP mode measures Time to First Byte (TTFB) using a HEAD request. TCP is faster and lower-level; HTTP reflects application-layer latency.
View results — Each ping result appears in the terminal output with color-coded latency (green <50ms, yellow 50-100ms, red >100ms). The sparkline chart shows latency trends. Summary statistics include average, min, max, jitter (mean deviation), and packet loss percentage.

About This Tool

TCP Ping vs ICMP Ping

Traditional ping uses ICMP (Internet Control Message Protocol) echo requests, which cannot be sent from a browser or serverless environment. This tool uses TCP handshake timing as a proxy measurement. When you "TCP ping" a host on port 443, the Cloudflare Worker initiates a TCP three-way handshake (SYN → SYN-ACK → ACK) and measures the time until the connection is established. This closely approximates ICMP RTT for most networks.

The key difference: ICMP ping tests if a host is alive at the network layer, while TCP ping tests if a specific port is open and responding. Some hosts block ICMP but accept TCP connections. The results may differ by 1-3ms due to the additional TCP state machine processing on the target host.

HTTP TTFB Measurement

HTTP mode sends a HEAD request and measures Time to First Byte (TTFB) — the total time from sending the request to receiving the first byte of the response. This includes DNS resolution, TCP handshake, TLS handshake, and server processing time. TTFB is a more realistic measure of what users experience when loading a webpage compared to raw TCP latency.

Cloudflare Edge Context

Pings are executed from a Cloudflare Worker at the nearest edge data center. The "Edge" indicator shows the IATA airport code of the data center handling your request (e.g., SFO for San Francisco, LHR for London). This provides context for interpreting results — latency to a host in the same region as your edge server will be lower than to a host across the world. For measuring your connection to the Cloudflare edge itself, see Internet Speed Test.

Jitter and Stability

Jitter is the variation in latency between consecutive measurements, calculated as the mean absolute deviation from the average RTT. Low jitter (under 5ms) indicates a stable, predictable connection ideal for real-time applications. High jitter causes packet reordering, which degrades VoIP call quality, causes video stuttering, and introduces input lag in gaming. Related network tools include DNS Lookup and WHOIS Lookup.

Why Use This Tool

Network Diagnostics

Ping is the most fundamental network diagnostic tool. It answers two questions: "Is this host reachable?" and "How fast is the connection?" The terminal-style output provides a familiar interface for developers and network engineers who use ping from the command line, while the visual chart and statistics make results accessible to all users.

Common Use Cases

Server monitoring: Check if a server is responding on a specific port. TCP ping to port 443 verifies HTTPS, port 22 verifies SSH, port 3306 verifies MySQL.
Latency comparison: Ping multiple DNS resolvers (8.8.8.8 vs 1.1.1.1 vs 9.9.9.9) to find the fastest one for your location.
Connection stability: Run 50 pings to identify intermittent connectivity issues. High jitter or packet loss suggests network problems.
CDN verification: Ping a CDN-hosted domain to verify you're hitting a nearby edge server. High latency to a CDN suggests DNS misconfiguration.

Privacy

The Worker does not log hostnames, IP addresses, or ping results. Each request is processed and discarded. For more network analysis tools, see What Is My IP, Internet Speed Test, Subnet Calculator, and DNS Lookup.

FAQ

How does the TCP ping work?

The tool uses Cloudflare Workers' connect() API to establish a raw TCP connection to the target host and port. The time for the TCP handshake to complete (socket open) is measured as the round-trip time. This is the closest approximation to ICMP ping available in a browser environment.

What is the difference between TCP and HTTP ping?

TCP ping measures the time for a raw TCP handshake (SYN/SYN-ACK/ACK). HTTP ping measures Time to First Byte (TTFB) — the full round-trip including TLS handshake and HTTP response. TCP ping is faster and lower-level; HTTP ping reflects real-world application latency.

Why does the ping come from a Cloudflare data center?

Browsers cannot send ICMP packets or raw TCP connections directly. The ping is executed from a Cloudflare Worker at the nearest edge location. The data center ID (colo) is shown so you can understand the measurement context.

Is my data logged?

No. The Worker does not log hostnames, IP addresses, or ping results. Each request is processed and discarded immediately.