Key takeaways
- In the FCC's thirteenth Measuring Broadband America report, fiber providers posted median idle latency of 7 to 14 ms, cable 12 to 24 ms and DSL 23 to 34 ms.
- Distance is a fixed cost: Cloudflare's examples put a 100 mile trip at 5 to 10 ms and a New York to London round trip at 145 ms, so choosing a nearby game server matters.
- Latency rises when your connection is busy, so wiring your console or PC and pausing big uploads often lowers ping more than a faster plan would.
In this story 8 sections
- Ping, latency and round trip time are nearly the same number
- Why fiber lands at 7 to 14 ms while DSL sits in the 20s and 30s
- Distance adds milliseconds no plan can remove
- The 100 ms line the federal government draws
- Idle latency and latency under load are different numbers
- Reading the four replies from a Windows ping test
- A worked example with real arithmetic
- How to lower ping for gaming
Your game shows a little number in the corner, maybe 18, maybe 140, and when it climbs, shots stop landing. That number is latency. So what is latency, exactly? It is the time data takes to travel from one point on a network to another, measured in milliseconds (ms). Speed tests call it ping, games call it lag, and network engineers call it round trip time. The figures below give you a sense of what normal looks like and how to bring yours down.
- 1 ms is one thousandth of a second, the unit every ping test reports.
- 7 to 14 ms is the range of typical idle latency the FCC measured for fiber providers.
- 12 to 24 ms is the FCC's range for cable internet.
- 23 to 34 ms is the FCC's range for DSL.
- 2x: round trip time is about double the one way latency, according to Cloudflare.
- 145 ms is Cloudflare's example of a round trip between New York and London.
- 100 ms is the round trip ceiling the federal BEAD broadband program sets for 95% of tests.
- 4 is the number of echo requests the Windows ping command sends by default.
Ping, latency and round trip time are nearly the same number
Strictly speaking, latency is the one way trip. Cloudflare's explainer on latency points out that round trip time, the time for your request to reach a server and the reply to come back, works out to roughly double that. A ping test measures the round trip, because your computer can only time the moment it sent a packet and the moment the answer arrived.
In daily use, nobody separates them. When a game, a speed test or your provider says your ping is 20 ms, it means a round trip of 20 ms. Lower is better, every time.
Why fiber lands at 7 to 14 ms while DSL sits in the 20s and 30s
The FCC's thirteenth Measuring Broadband America report, based on tests run in September and October 2022, compared idle latency across major US providers. Median results per provider ranged from 7 to 34 ms overall. Fiber providers clustered at the low end (7 to 14 ms), cable came next (12 to 24 ms), and DSL trailed (23 to 34 ms).
The connection type shapes the first stretch of every trip. Fiber carries light over glass all the way to your home, while cable and DSL rely on older copper for the last leg. The report did not publish comparable figures for satellite or fixed wireless, so if that is your service, our guide to how satellite internet works is a better place to start.
Distance adds milliseconds no plan can remove
Cloudflare calls distance one of the main causes of latency. Data does travel at close to the speed of light, but a trip across a continent or an ocean still takes time, and every network hand off along the route adds a few milliseconds.
Its examples make the point. A host in Columbus, Ohio, would likely reach users in Cincinnati, about 100 miles away, in 5 to 10 ms. Users in Los Angeles, about 2,200 miles away, would see something closer to 40 to 50 ms. Across the Atlantic, a New York to London round trip in Cloudflare's example took 145 ms.
That is why picking a game server in your own region often does more for your ping than upgrading to a faster plan. A gigabit plan cannot shorten the distance to a server in another country.
The 100 ms line the federal government draws
For networks built with money from the federal BEAD program, the NTIA's performance measures notice requires that 95% or more of round trip latency tests come in at or below 100 ms. Providers must run at least one test per minute during each testing hour, and lost packets count as failed tests.
Treat 100 ms as a floor for acceptable service, not a target for gaming. A connection that just meets it would still sit well above the fiber and cable medians the FCC measured.
Idle latency and latency under load are different numbers
Most speed tests report ping on a quiet line. The FCC report added a second measurement, latency under load (also called working latency), which checks ping while the connection is busy. It found working latency is higher than idle latency.
This explains a common complaint: ping looks great in a test, then spikes the moment someone in the house starts a large upload, a cloud backup or a 4K stream. If your lag comes and goes with household activity, the problem is congestion on your own connection, not the game. Our guide on why your internet is so slow walks through those fixes, and how to check internet speed explains where each result number comes from.
The same report put packet loss in context too. It said loss of a few tenths of a percent is common and unlikely to noticeably hurt most applications. Steady loss above that is worth chasing.
Reading the four replies from a Windows ping test
You can measure latency without any app. Microsoft's documentation for the ping command explains that it sends ICMP echo requests and shows the round trip time for each reply. Open Command Prompt and type ping followed by an address. By default it sends 4 requests. Add /n with a number to send more, or /t to keep pinging until you stop it with Ctrl+C.
The single number matters less than the spread. If the four replies are close together, your connection is steady. If they swing widely, you have jitter, the variation between pings, and that is what makes characters rubber band in online games even when the average looks fine.
A worked example with real arithmetic
Say you run ping with /n 10 to a game server and get these round trip times in ms: 18, 19, 21, 18, 20, 19, 64, 22, 18, 21.
- Add them up: 18 + 19 + 21 + 18 + 20 + 19 + 64 + 22 + 18 + 21 = 240 ms.
- Divide by the number of replies: 240 ÷ 10 = 24 ms average.
- Take out the one spike: 240 minus 64 = 176, and 176 ÷ 9 ≈ 19.6 ms.
- Measure the spread: the highest reply (64) minus the lowest (18) is 46 ms.
The average of 24 ms looks healthy and sits right in cable territory. The 64 ms outlier is the moment you would feel lag. One spike in ten is often a busy moment at home, so run the test again while nothing else is using the connection. If the spikes vanish, congestion was the cause.
Now apply the BEAD rule to a full hour of testing. At one test per minute, that is 60 tests. To pass, 95% must be at or below 100 ms: 60 × 0.95 = 57. So no more than 3 tests in that hour could exceed 100 ms or be lost.
How to lower ping for gaming
These steps attack the causes the numbers above point to, starting with the easiest.
- Plug in with an Ethernet cable. WiFi adds its own delay and interference. A cable removes both.
- Pick the closest server region in the game's settings. Distance is a fixed cost, so cut it where you can.
- Pause heavy uploads and downloads while you play. Cloud backups, game updates and video uploads push working latency up.
- Restart your modem and router if ping is high on every server. Our guide on modem vs router explains which box does what.
- Compare your results to the FCC medians. If you are on fiber and see 60 ms to a nearby server on a wired connection, call your provider with your ping results ready.
For a final check, run the same ping test at a quiet hour and again at peak evening time. If the numbers barely move, your setup is fine. If evenings run far higher, you have found where your lag comes from. You can find more guides like this in our tech section.
Sources
Share this story
Spotted an error? Tell us

