Ping is the round-trip time it takes for a small packet of data to travel from your device to a server and back, measured in milliseconds. Dozens of factors influence that number, from the physical distance between you and the server to the quality of your Wi-Fi signal to software running quietly in the background. Understanding each one helps you figure out why your ping is high and what you can actually fix.
Physical Distance to the Server
The single biggest factor in your ping is how far your data has to travel. Light moves through fiber optic cable at roughly two-thirds the speed of light in a vacuum, and even at that speed, distance adds up. A packet traveling from New York to London crosses roughly 5,500 kilometers of undersea cable, and the physics alone guarantee a meaningful delay before any network equipment even touches it.
This is why game servers are spread across regions. Connecting to a server 200 kilometers away will always produce lower ping than one 3,000 kilometers away, no matter how fast your internet plan is. If you consistently see high ping in a specific game or app, check which server region you’re connected to first.
Your Connection Type
The technology carrying your internet signal sets a baseline for how low your ping can go. Fiber optic connections produce the lowest latency, typically in single-digit to low-double-digit milliseconds. Standard cable (coaxial) connections sit a step behind. DSL, which runs over old phone lines, tends to be higher still. Satellite internet is in a different category entirely, with latency that can reach 600 milliseconds or more on traditional geostationary satellites because the signal has to travel tens of thousands of kilometers into orbit and back.
Newer low-earth-orbit satellite services like Starlink have cut that down significantly, but they still can’t match a wired fiber connection. If you’re on DSL or satellite and frustrated by ping, the connection type itself is likely your ceiling.
Network Congestion and Bufferbloat
When too many devices or users compete for the same bandwidth, packets start lining up in queues inside your router, your modem, and equipment along the route. The longer the queue, the higher the latency. This is why your ping can spike during peak evening hours or when someone else in your house starts a large download.
A particularly common version of this problem is called bufferbloat. Modern networking equipment contains large memory buffers designed to prevent packet loss by holding onto data rather than dropping it. The intention is good, but the side effect is terrible for latency. Once those buffers fill up, every packet sits in line waiting its turn, and your ping balloons. Services that need low latency, like online gaming, voice calls, and video chat, can slow to the point of being unusable. You can test for bufferbloat at sites like dslreports.com or waveform.com. If the problem exists on your home router, enabling a feature called SQM (smart queue management) in your router’s settings, if available, can help by intelligently managing those queues.
Number of Network Hops
Your data doesn’t travel in a straight line from your device to the server. It passes through a chain of routers, switches, and exchange points, each one called a “hop.” Every hop introduces a small delay as the equipment reads the packet’s destination and forwards it along. While modern high-performance routers process packets in microseconds (around 0.1 milliseconds each), the delays add up across 10, 15, or 20 hops.
The route your data takes depends largely on your ISP’s peering agreements with other networks. ISPs don’t optimize routes for the lowest ping. They route traffic based on cost, business relationships, and available capacity. Your ISP might send your data through a hub hundreds of kilometers out of the way because that’s where their peering agreement with the destination network exists. Two people in the same city using different ISPs can have noticeably different ping to the same server for exactly this reason. Some ISPs maintain local peering hubs close to major content providers like Google or gaming platforms, while others route through more distant exchange points.
Wi-Fi Interference and Signal Quality
Switching from a wired Ethernet connection to Wi-Fi almost always increases your ping, and the difference can be dramatic depending on your environment. Wi-Fi signals are vulnerable to interference from other devices broadcasting on the same frequency. On the common 2.4 GHz band, cordless phones, baby monitors, Bluetooth devices, microwave ovens, and your neighbors’ routers all compete for the same airspace. When interference hits, your device has to retransmit packets, and each retransmission adds milliseconds to your ping.
The 5 GHz band is less crowded and less susceptible to interference from household electronics, which generally makes it better for latency-sensitive tasks. The tradeoff is shorter range: 5 GHz signals don’t pass through walls and floors as well. If you’re gaming or video calling, the best move is a wired Ethernet connection. If that’s not possible, getting closer to your router and using the 5 GHz band will typically give you the lowest and most stable wireless ping.
Background Software and Bandwidth Usage
Programs running on your own device can quietly eat into your ping. Cloud backup services like Google Drive, Dropbox, or iCloud sync files in the background and consume bandwidth without any visible sign. Operating system updates, antivirus scans that phone home to cloud databases, and real-time notification services all generate network traffic. Each one adds a small amount of congestion on your local connection, and together they can meaningfully raise your ping.
This is especially noticeable on slower connections where background processes take up a larger share of available bandwidth. Before blaming your ISP for high ping, check what’s running in the background. On Windows, Task Manager’s “Network” column shows which processes are using bandwidth. On Mac, Activity Monitor has a “Network” tab that does the same. Pausing cloud syncs and delaying updates during gaming sessions or video calls can make a real difference.
Packet Loss and Hardware Problems
Packet loss and latency are different problems, but they feed into each other. When packets get lost in transit, your device has to request and wait for replacements, which inflates your effective ping. Common causes of packet loss include faulty or degraded cabling, failing network hardware, and wireless interference. A damaged Ethernet cable, a corroded coaxial connector, or an aging modem can all introduce intermittent packet loss that shows up as ping spikes.
You can distinguish between the two problems by watching patterns. If your ping is consistently high, that points to a latency issue like distance, congestion, or connection type. If your ping is normally stable but you see occasional “Request timed out” messages, that’s packet loss, and it often points to a hardware or signal quality problem. Running a continuous ping test (typing “ping -t” followed by an address in your command prompt) for a few minutes can reveal which pattern you’re dealing with.
When Ping Actually Matters
Not every online activity is equally sensitive to ping. For web browsing and streaming video, latency barely matters because data loads in large chunks and buffers ahead. For real-time activities, the thresholds are much tighter. In competitive online gaming, players can perceive latency differences as small as 5 to 10 milliseconds, and anything above 50 to 80 milliseconds starts to feel sluggish in fast-paced games. Voice and video calls become choppy around 150 milliseconds. Generally, under 20 milliseconds is excellent, 20 to 50 is good for most uses, 50 to 100 is playable but not ideal for competitive gaming, and above 150 creates noticeable problems for any real-time application.