Frankfurt, DE (Auto)
Back to Home

What is Ping?

A complete guide to ping: what it measures, how different tools measure it, what the numbers mean for gaming, streaming, and video calls, and why physical distance sets a hard floor under your latency.

Definition of Ping

Ping is the time it takes for a small piece of data to travel from your device to another machine on the internet and back, expressed in milliseconds (ms). The name comes from sonar: a submarine sends a "ping" and times the echo to judge distance. Networking borrowed the term for the ping command, a diagnostic tool released in 1983 that does exactly the same thing with network packets.

Unlike bandwidth — how much data your connection can move per second — ping measures how quickly a single message gets a reply. A connection can be very fast in megabits yet still feel sluggish in a game if its round trips are slow. That is why gamers and remote workers care about ping at least as much as raw speed.

Ping vs. Latency vs. RTT: Sorting Out the Terms

These three words get used interchangeably, but they have slightly different technical meanings:

  • Latency is the general concept: any delay between a cause and its effect on a network. Strictly speaking, one-way latency is the time for data to travel in a single direction.
  • RTT (round-trip time) is the specific measurement: the time for data to go out and for the reply to come back. This is what nearly every test actually measures, because timing a one-way trip requires perfectly synchronized clocks on both ends.
  • Ping is, technically, the tool or action that produces an RTT measurement — but in everyday use, "my ping" simply means "my round-trip time."

So when a game shows "ping: 42ms," it means a round trip between your machine and the game server took about 42 milliseconds. Your one-way delay is roughly half that.

How Ping Is Measured — and How This Tool Measures It

The classic ping command sends ICMP echo packets: tiny probes that the target machine bounces straight back at a low level of the operating system. It is the purest latency measurement available, but it requires OS-level access — which web pages, by design, do not have.

Browser-based tools like CheckPing therefore measure something slightly different: the round-trip time of small HTTPS requests sent from your browser to nearby cloud region endpoints. This adds a little overhead from TLS and browser processing, so the absolute number typically runs a few milliseconds higher than a raw ICMP ping to the same destination. It is also not the same as your in-game ping, which is measured by the game client against the specific server hosting your match.

What a browser test is good at is showing your real-world latency baseline and its stability: whether your connection is fast or slow, steady or spiky, better on Ethernet than on Wi-Fi, worse at 9pm than at 9am. For comparing your latency to different game server regions, our per-game ping pages measure against the cloud regions closest to each game's server locations.

What Ping Numbers Mean, Activity by Activity

There is no single "good ping" — the threshold where delay becomes noticeable depends entirely on what you are doing. Typical ranges:

Competitive FPS (CS2, Valorant, Overwatch 2)

The most latency-sensitive category. Under ~30ms feels instant; 30-50ms is fine for ranked play; above ~80ms you will start losing duels to peeker's advantage — the attacker's information reaches the server before your reaction does. Consistency matters as much as the average here.

MOBAs and strategy (League of Legends, Dota 2)

More forgiving because actions are point-and-click rather than aim-dependent. Under ~50ms is excellent; up to ~80ms is comfortable; precise skillshot dodging degrades noticeably beyond ~100ms.

Cloud gaming (GeForce Now, Xbox Cloud)

Every input travels to the cloud and every frame travels back, so latency is felt twice. Under ~40ms to the streaming region feels close to native; beyond ~70ms the input lag becomes hard to ignore in action games.

Video calls and remote work

Conversation flows naturally below ~150ms of one-way delay; people start talking over each other beyond that. A ping under ~100ms with low jitter is plenty — call quality problems are more often caused by jitter and packet loss than by raw latency.

Streaming video (Netflix, YouTube, Twitch viewing)

The least sensitive activity. Players buffer several seconds of video ahead, so even a 200ms ping is invisible once playback starts. If streams stutter, the cause is almost always bandwidth or packet loss, not ping.

For game-by-game targets, see what is a good ping for gaming.

The Physics: Why Distance Sets a Floor

Data in fiber-optic cable travels at roughly two-thirds the speed of light — about 200,000 km per second. That sounds instant, but over continental distances it adds up: a rough rule of thumb is about 1ms of round-trip time per 100km of cable distance. A round trip between Europe and the US East Coast crosses roughly 6,000km of ocean each way, so ~60ms of ping is physically unavoidable before a single router adds its share.

Real routes are longer than the straight line on a map: your packets hop through your ISP's network, exchange points, and transit providers, each hop adding queueing and processing time. This is why two players in the same city can see different pings to the same server — their ISPs may route traffic along very different paths. It is also why no software tweak can ever beat moving to a closer server region.

Ping, Jitter, and Packet Loss: The Quality Triangle

Ping is one corner of a triangle. A connection is only as good as its weakest corner:

  • Ping — how long round trips take on average.
  • Jitter — how much that time varies from packet to packet. A steady 50ms often plays better than a 25ms average that spikes to 150ms, because games and calls can compensate for constant delay but not for unpredictable delay. See jitter vs. ping explained.
  • Packet loss — the percentage of packets that never arrive. Lost packets must be resent or interpolated around, causing rubber-banding in games and robotic audio in calls. Even 1-2% is noticeable in real time. See how to fix packet loss.

When diagnosing a bad connection, check all three: a "high ping" complaint often turns out to be a jitter or loss problem in disguise.

Factors Affecting Ping

  • Distance: Physical distance to the server - closer servers = lower ping
  • Network Type: Fiber typically has lower ping than cable or DSL
  • Connection Type: Wired Ethernet has lower ping than Wi-Fi
  • Network Congestion: Peak hours and heavy traffic increase ping
  • ISP Routing: Some ISPs have better routing paths than others
  • Router Quality: Better routers can reduce ping slightly
  • Background Traffic: Downloads and streaming increase ping

Many of these are within your control. Our step-by-step guide covers what actually helps: how to lower your ping.

How to Check Your Ping

The quickest way is a browser test: open CheckPing.io, click Start Test, and within seconds you get your minimum, average, and maximum round-trip times plus jitter — measured over HTTPS to nearby cloud endpoints, with nothing to install. Remember the honest caveat above: this is a real-world latency baseline, not your exact in-game ping.

For more common questions — like why browser results differ from in-game numbers — see our FAQ.

Test Your Ping Now

Ready to check your ping? Use CheckPing.io to test your latency and see how your connection performs.

Check Your Ping Now

Related Reading