Home Features Pricing Network Map Monitoring
Diag Tools
Sign In Start Free

Ping any host from 24 locations.

Measure round-trip latency and detect packet loss to any server or website. Test ICMP reachability from 24 monitoring nodes across 13 countries — see exactly where a host is fast, slow, or unreachable.

24 Monitoring nodes
13 Countries
$0 No account

Measure round-trip latency and packet loss to any host from 24 global locations. Enter any reachable hostname or IP address — results stream back in seconds.

Try:

Note: All checks are public. Create a free account to keep your checks private and get an email if your site stops responding.

What is a Ping Test?

A ping test uses the Internet Control Message Protocol (ICMP) to verify whether a host is reachable and to measure how long it takes for a packet to travel from a source to a destination and back. This round-trip journey is measured in milliseconds and referred to as Round-Trip Time (RTT).

When you run a ping test, your machine sends an ICMP Echo Request to the target host. If the host is reachable and not blocking ICMP traffic, it replies with an ICMP Echo Reply. The time between sending the request and receiving the reply is the latency you see reported.

Two other key values reported by a ping are Time to Live (TTL) and packet loss. TTL indicates how many network hops a packet can traverse before being discarded — it decreases by one at each router. Packet loss, expressed as a percentage, tells you how many requests went unanswered, which can signal network congestion, hardware issues, or deliberate ICMP filtering.

Ping is the most fundamental network diagnostic tool. When something is wrong with connectivity, ping is almost always the first tool used. Emercom runs pings simultaneously from 24 servers spread across 13 countries, giving you a global view of your host's reachability in a single test run.

A ping operates at Layer 3 — the network layer. It answers one question: "is this host alive, and how long is the round trip?" It does not validate HTTP, TLS, or DNS — those each need their own checks. Ping is the floor, not the ceiling.

Key Ping Metrics

Every ping result is built from a small set of values that together describe both raw speed and consistency. Understanding what each metric represents makes it much easier to diagnose where a problem actually lives.

Metric Name What it means
RTT Round-Trip Time Total travel time of a packet, in milliseconds, from source to target and back.
min Minimum RTT Best (lowest) round-trip time observed across all packets in the run — the network's best-case performance.
avg Average RTT Mean round-trip time across all packets — the typical latency baseline a user would experience.
max Maximum RTT Worst round-trip time observed — indicates how bad latency spikes get during the run.
mdev Jitter Mean deviation across RTT samples — measures how consistent latency is over time. High values mean an unstable connection.
TTL Time to Live Hops remaining on the return packet. Useful for detecting routing loops and inferring path length.
Loss Packet Loss Percentage of requests that received no reply — anything above 0% is worth investigating.

Understanding Ping Results

Not all latency is equal — context matters. A 10ms ping to a server in the same city is excellent; a 10ms ping across the Atlantic would be impossible. The following ranges are general guidelines based on geographic distance and typical internet routing.

Latency Rating Typical Cause Impact
< 50ms Excellent Same region or nearby data center. No perceptible delay for any application.
50–150ms Good Cross-continent (e.g., US to Europe). Fine for web apps and APIs; borderline for real-time.
150–300ms Acceptable Intercontinental (e.g., US to Asia). Noticeable in real-time applications; acceptable for most web services.
> 300ms High — investigate Poor routing, congestion, satellite links. Significant delays; likely to cause user-facing issues.

Packet Loss

Any packet loss above 0% warrants investigation. Small amounts (1–2%) may be caused by ICMP deprioritization on busy routers — the router receives the packet just fine but delays or drops the ICMP reply to conserve resources for actual traffic. However, consistent packet loss or values above 5% typically point to a genuine network problem: congested links, misconfigured firewalls, or failing hardware.

If you see packet loss from many Emercom locations simultaneously, the issue is close to the target host. If only a few specific locations show loss, the problem may be regional routing or ISP peering.

Jitter

Jitter (sometimes shown as mdev in ping output) measures how much your latency varies between packets. Low jitter means a consistent, stable connection. High jitter — even with an acceptable average — can degrade real-time applications like VoIP, video conferencing, and online gaming significantly.

A server with 80ms average RTT and 2ms jitter will feel more reliable than one with 40ms average and 60ms jitter, because the unpredictability forces applications to buffer more data, increasing perceived lag.

Why Ping From Multiple Locations?

Running a ping from your own machine only tells you what the network looks like from your vantage point. A host might respond in 20ms for you but be completely unreachable from Asia, or show 800ms latency from South America due to suboptimal BGP routing. Single-location pings will silently miss these regional failures. Multi-location testing surfaces five distinct things a local ping cannot:

  • Regional outages. Your server may be down in one geography while appearing fine in another — a local ping would never catch it.
  • ISP routing issues. Traffic from specific providers or regions taking inefficient or congested paths shows up as elevated latency from one location and not others.
  • Geographic latency baselines. Understand the physics-imposed minimum RTT for each region before you start debugging anything else.
  • CDN & anycast behavior. Verify that users in different regions actually hit the nearest edge node instead of being routed across continents.
  • Firewall & ACL gaps. ICMP may be blocked from some networks but not others — only visible when you ping from many vantage points at once.

Emercom runs all 24 pings in parallel from nodes spread across 5 continents and 13 countries. You get a complete global picture in seconds rather than having to manually test from multiple tools or VPN endpoints.

Related Tools

More free network diagnostics, all running from the same 24-location footprint.

Website Availability Check

Test HTTP status codes, response times, and redirects globally.

Port Checker

Verify TCP port accessibility and firewall rules globally.

DNS Lookup

Query DNS records and verify propagation across regions.

WHOIS Lookup

Find domain registration details, expiry dates, and nameservers.

Monitor this host continuously

Turn this ping test into an ICMP monitor and get alerts when the host goes unreachable — from 24 global locations, via email, SMS, voice, or Telegram.

Start Monitoring Free See how monitoring works Open Full Tools