Online Ping Tool
Ping any public IP address or domain from your browser and measure response times in real time.
Ping results
| Seq |
Target |
Time |
TTL |
Status |
Ping limits by plan
|
Without login — Your plan |
Free |
Pro |
Premium |
Enterprise |
| Ping limits by plan |
1 targets per 24 h
6 pings per run
Every 20 s |
2 targets per 24 h
12 pings per run
Every 15 s |
6 targets per 24 h
50 pings per run
Every 10 s |
20 targets per 24 h
50 pings per run
Interval 15–60 s adjustable |
Unlimited targets
1000 pings per run
Interval 5–60 s adjustable |
| Pause & stop |
— |
— |
✓ |
✓ |
✓ |
| Interval slider |
— |
— |
— |
✓ |
✓ |
| Response time chart |
— |
— |
— |
✓ |
✓ |
| Multiple targets at once |
— |
— |
— |
✓ |
✓ |
Upgrade your plan
What is ping? ICMP echo explained
Ping is the internet's oldest and simplest network diagnostic: it sends an
ICMP Echo Request (RFC 792 for IPv4, RFC 4443 for IPv6) to a target
IP address or domain and measures the time until the Echo Reply
comes back — the round-trip time (RTT) in milliseconds. A successful
ping proves three things at once: the target resolves in DNS, packets route to it
across the internet, and the host is up and answering. This free online ping test
runs the probes from our European datacenter, so you can check whether a server is
reachable from a neutral, well-connected vantage point — independent of your own
Wi-Fi, VPN, or ISP.
Typical uses: checking if a server, website, or mail
server (MX host) is online, measuring latency to a datacenter before deploying,
watching a host come back after a reboot, and verifying DNS changes with
a second, independent resolver path.
How to read your ping results
- Time (RTT) — the round trip in milliseconds. Watch the trend, not a single value: rising RTT under load signals congestion.
- TTL — the packet's remaining hop budget on arrival. Reply TTL near 64 usually means a Linux host, near 128 a Windows host; the difference from those start values approximates the number of router hops.
- Loss — the percentage of requests without a reply. 0% is the wired-network norm; sustained loss above 5% breaks interactive traffic and slows every TCP transfer.
- Min / Avg / Max — the spread between them is the jitter. A tight spread means a stable route; a wide spread means queueing or an unstable path even when the average looks fine.
Ping latency reference values
| Round-trip time | Rating | Typical for |
|---|
| < 20 ms | Excellent | Same city / same datacenter |
| 20–50 ms | Very good | National routes, competitive gaming |
| 50–100 ms | Good | Intra-continental routes |
| 100–200 ms | Acceptable | Intercontinental routes (EU↔US ~90 ms) |
| > 300 ms | Poor | Satellite links, congested or detoured paths |
Ping vs. traceroute
Ping tells you whether a host is reachable and how fast
the round trip is; traceroute tells you which route packets take and
where the path slows down or breaks. Traceroute works by sending probes
with deliberately small TTL values so every router on the path reveals itself via an
ICMP Time Exceeded reply. Start with ping for a quick health check and continuous
latency monitoring; reach for the online traceroute
tool when ping shows loss or high latency and you need to locate the failing hop.
Ping for mail servers and email deliverability
Email troubleshooting starts at the network layer. An MX host that does not answer, or
answers with high latency and packet loss, produces SMTP timeouts and delayed mail long
before SPF, DKIM, or DMARC enter the picture. Ping your MX hostnames to verify they
resolve and respond, then continue up the stack with the analyzer's companion tools:
the Domain Security Checker for SPF/DKIM/DMARC DNS
records, the Blacklist Checker for RBL listings of
your sending IPs, the Email Header Analyzer for
per-message authentication results, and the
email-deliverability guide for the complete diagnostic funnel.
Frequently asked questions about ping
Quick answers to the most common questions about ping, latency and packet loss. Click any question to expand its answer.
What is ping?
Ping is a network diagnostic utility that tests whether a host (an IP address or domain) is reachable and measures how long packets take to travel to it and back. It works by sending an ICMP Echo Request (defined in RFC 792 for IPv4 and RFC 4443 for IPv6) and timing the ICMP Echo Reply. The result is the round-trip time (RTT) in milliseconds. Ping is named after sonar terminology and has been the first-line connectivity check for network operators since 1983. A successful ping proves the target is online, routable, and answering ICMP; the measured latency indicates how fast the network path is.
How does an online ping test work compared to ping in my terminal?
A terminal ping (Windows cmd, macOS Terminal, Linux shell) measures latency from YOUR computer to the target, so the result includes your local Wi-Fi, ISP, and last-mile connection. An online ping test like this one runs from our server in a European datacenter, so it measures latency from a well-connected neutral vantage point — useful for checking whether a server is down for everyone or just for you, for testing from a second network path, and for measuring a server's baseline reachability without your local network noise. This browser tool sends one ICMP echo per interval tick from our infrastructure and streams each reply time, TTL, and packet-loss statistics back to your browser in real time.
What is a good ping time?
As a rule of thumb: under 20 ms is excellent (same-city or same-datacenter paths), 20-50 ms is very good (typical national routes and competitive online gaming), 50-100 ms is good and normal for cross-country or intra-continental routes, 100-200 ms is acceptable and expected for intercontinental paths (Europe to US East is ~80-100 ms, Europe to Asia ~150-250 ms because light in fiber travels about 200 km per millisecond), and over 300 ms feels sluggish for interactive use like video calls or SSH. For servers, what matters most is CONSISTENCY: a steady 90 ms is healthier than latency swinging between 20 ms and 200 ms (jitter), which indicates congestion or an unstable route.
What does packet loss in a ping test mean?
Packet loss is the percentage of ping requests that never received a reply. 0% is the healthy norm on wired networks. Occasional single lost packets (under ~2%) can be transient congestion and are usually harmless. Sustained loss above 5% degrades every protocol running over the path: TCP throughput collapses because lost segments force retransmissions, video calls stutter, and SMTP connections time out mid-session. Consistent loss usually points to an overloaded link, failing hardware, or an ISP routing problem; loss that only appears at the far end of a route is the target network's problem, while loss from the first hop onward is local. Note that some hosts deliberately rate-limit or deprioritize ICMP, so low-rate loss to one specific host with otherwise perfect connectivity may just be ICMP policing, not real data-plane loss.
What does TTL mean in a ping reply?
TTL (Time To Live) is a counter in every IP packet that starts at an operating-system-specific value (commonly 64 for Linux, 128 for Windows, 255 for network equipment) and is decremented by one at every router hop. The TTL shown in a ping reply is the remaining count when the packet arrived back, so it hints at both the target's operating system and the hop distance: a reply TTL of 55 most likely means a Linux host (started at 64) about 9 router hops away. If TTL ever reaches zero in transit, the packet is discarded and the router sends back an ICMP Time Exceeded message — that mechanism is exactly what traceroute exploits to map a route hop by hop.
Why does my ping time out even though the website works?
A ping timeout does not always mean the host is down. Many networks and hosts block or rate-limit ICMP Echo Requests at the firewall while still serving HTTP, SMTP, and other application traffic normally — Microsoft Azure, for example, historically dropped inbound ICMP by default. So "request timed out" can mean the host is genuinely offline, or that a firewall silently discards ICMP, or that an intermediate network deprioritizes it under load. To distinguish: if the website or mail server responds but ping does not, ICMP is filtered and the host is fine. If both fail, the host or its network is actually unreachable — then a traceroute shows where on the path packets stop getting through.
What is the difference between ping and traceroute?
Ping answers WHETHER a host is reachable and HOW FAST the round trip is; traceroute answers WHICH ROUTE packets take to get there and where the path breaks or slows down. Ping sends ICMP Echo Requests directly to the destination and reports end-to-end round-trip time and packet loss. Traceroute (tracert on Windows) sends probes with deliberately small, increasing TTL values so each router on the path reveals itself via an ICMP Time Exceeded reply — producing a hop-by-hop list with per-hop latency. Use ping first for a quick health check and continuous latency monitoring; switch to traceroute when ping shows loss or high latency and you need to locate WHERE on the path the problem starts.
Why does ping matter for mail servers and email deliverability?
Before diagnosing SPF, DKIM, or DMARC failures, you need to know the basics are healthy: a mail server (MX host) that is unreachable or on a congested route causes SMTP connection timeouts, retry queues, and delayed or bounced mail long before authentication even enters the picture. Pinging your MX hostnames verifies they resolve and respond, and the latency trend reveals network degradation ahead of user complaints. Combined with this DMARC analyzer's other tools — the Domain Security Checker for SPF/DKIM/DMARC DNS records, the Blacklist Checker for RBL listings of your mail IPs, and DMARC aggregate-report monitoring for authentication results — a simple ping closes the loop on the network layer of email troubleshooting.