Selected Test Server
Ready to Check Latency
Measures round-trip time (RTT), latency spikes, packet loss, and jitter consistency.
Live Metrics
Network Quality & Stability Score
NOT TESTEDStart an interactive test to generate your connection quality score.
- Run a full 100-packet probe to generate diagnostic recommendations.
What Is a Ping Test?
Understanding Ping and Round-Trip Time (RTT)
A ping test is a fundamental network diagnostic procedure that measures the total round-trip time (RTT) required for a packet of data to travel from your local device, through your local network and internet service provider (ISP), to a remote test server, and back again.
Round-trip time is recorded in milliseconds (ms). Because one millisecond represents one-thousandth of a second, even minor fluctuations can impact interactive online experiences. A lower ping generally indicates a more immediate, responsive connection, while a higher ping introduces a noticeable delay between your actions and the server's acknowledgment.
Why Ping Varies Across Different Servers
You will rarely observe the exact same ping when testing against different online destinations. Server response times depend on multiple physical and logical factors:
- Geographic Distance: Physical distance to the datacenter creates a natural baseline delay, as signals can only travel as fast as fiber-optic transmission allows.
- Routing Paths & Intermediary Networks: The specific network exchange points and intermediary routes your ISP uses to direct data to the target server.
- Server Node Processing: Server load, operating system queue times, and application layer response processing at the destination edge.
Ping vs. Download Speed vs. Upload Speed vs. Stability
Understanding how different network metrics define connection performance:
| Network Metric | What It Measures | Primary Unit | Impact on Real-Time Use | Practical Reference |
|---|---|---|---|---|
| Ping / RTT | Round-trip signal transit delay | Milliseconds (ms) | Immediate responsiveness, reaction speed, input lag | Lower is generally better (< 30 ms is a common low-latency reference) |
| Jitter | Statistical variance in latency over time | Milliseconds (ms) | Audio stutter in calls, glitchy gaming movement | Low variance (< 3 ms is a common stability reference) |
| Packet Loss | Percentage of sent packets that failed to arrive | Percentage (%) | Rubber-banding, dropped audio words, frame freezes | Typically 0% in brief test probes; impact depends on application |
| Download Speed | Volume of data transferred to your device per second | Mbps / Gbps | File download duration, 4K/8K video streaming buffer | Higher capacity based on service plan needs |
| Upload Speed | Volume of data sent from your device per second | Mbps / Gbps | Live video broadcasting, cloud file backups | Higher capacity based on service plan needs |
How to Test Ping Online
Follow this structured procedure to perform a precision multi-probe network diagnostic using the interactive tools above:
Select Test Node
Keep the default Auto Select to benchmark the nearest edge server, or pick a specific datacenter route from the dropdown.
Start 100-Packet Probe
Click Start Ping Test. The lab dispatches 100 sequential micro-probes while graphing round-trip times and jitter in real time.
Review Stability Score
Inspect your Median Ping, Jitter, Packet Loss percentage, and check the custom application readiness scores for Gaming, Calls, and Streaming.
What Is a Good Ping?
There is no universal, rigid standard for what constitutes an acceptable ping because performance expectations vary significantly depending on the application. A 120 ms ping is entirely imperceptible when streaming a 4K movie or reading web articles, yet it can feel delayed in a fast-paced multiplayer first-person shooter.
The following categories represent an approximate practical reference. Actual real-world performance depends heavily on the specific application, physical distance to the server, regional routing, and local network consistency:
| Approx. Ping (ms) | Reference Category | Online Gaming Experience | VoIP & Video Calling | Web Browsing & Media |
|---|---|---|---|---|
| < 20 ms | Very Low | Highly responsive feel; common in competitive esports with close servers. | Clear voice flow without noticeable conversational delay. | Near-instantaneous initial connection response. |
| 20 – 50 ms | Low | Smooth gameplay; generally responsive for most online games. | Natural conversation flow without noticeable overlap. | Fast loading times with seamless navigation. |
| 50 – 100 ms | Moderate | Playable in casual games; minor delay may be noticed in twitch FPS. | Occasional minor speaking collision; generally solid. | Standard browsing experience; media buffering is unaffected. |
| 100 – 180 ms | High | Noticeable delay, input lag, delayed hit registration, rubber-banding. | Noticeable speech delay, frequent conversational interruptions. | Slightly sluggish webpage initial loading; streaming remains fine. |
| > 180 ms | Very High | Delay is clearly noticeable; can be problematic for real-time matches. | Noticeable lag, audio clipping, talk-over confusion. | Slow initial response times; media buffering remains largely functional. |
Jitter & Packet Loss Diagnostics
What Is Network Jitter?
Jitter represents the statistical variance or fluctuation in packet arrival times over a continuous connection. For instance, if one packet takes 25 ms to arrive, the next takes 65 ms, and the third takes 30 ms, your network is experiencing jitter.
Real-time applications like voice calls (Discord, Zoom, Teams) and multiplayer gaming rely on steady, predictable packet delivery. When jitter is high, packets arrive out of order or in erratic bursts, forcing the receiving software to buffer or drop delayed packets.
What Is Packet Loss & Why Does It Cause Lag?
Packet loss occurs when one or more data packets travelling across a network fail to reach their intended destination. This can happen due to router queue drops during heavy congestion, wireless radio frequency interference, or intermediary routing problems.
In real-time UDP streams (used in online games and voice communication), lost packets cannot always be retransmitted in time without introducing delay. This can lead to dropped syllables, character warping (rubber-banding), or brief input desynchronization.
Practical Protocol to Troubleshoot Packet Loss & Spikes
Switch to another server in the Multi-Server Mesh tab to confirm if packet loss is isolated to a single route or present across all endpoints.
Connect via a physical Ethernet cable to help rule out local Wi-Fi channel congestion, physical wall blockage, or wireless radio interference.
Ensure background cloud backups (OneDrive, Google Drive, iCloud) or game updates (Steam, Epic) are not saturating your upstream link.
Restart modem and router to clear memory buffer leaks, refresh DHCP leases, and re-establish clean downstream line synchronization with your ISP.
Loaded Latency & Bufferbloat
Idle Latency vs. Loaded Latency
Most traditional speed tests only measure Idle (Unloaded) Latency—the time it takes for a packet to travel when no other traffic is actively utilizing your internet connection.
In reality, home networks are rarely completely idle. Other household members may be streaming video, downloading updates, or uploading files. Loaded Latency measures round-trip time while your link is under simulated bandwidth strain, revealing whether your latency remains stable or surges under load.
What Is Bufferbloat?
Bufferbloat is high latency and jitter caused by excessively large buffers built into routers, modems, and network switches. When heavy download or upload traffic occurs, routers hold packets in long memory queues rather than dropping or pacing them intelligently.
Because real-time gaming or voice packets can get stuck behind large file transfers in the queue, ping can spike noticeably. Enabling Smart Queue Management (SQM) algorithms such as CAKE or FQ_CoDel on compatible routers is an effective way to mitigate bufferbloat.
Gaming Ping & Lag Optimization
Why Low Ping Alone Does Not Guarantee Smooth Gaming
While a low average ping is helpful for fast-paced multiplayer and competitive games, connection consistency is equally important. A steady connection with low jitter often provides a smoother, more predictable experience than an erratic connection that intermittently spikes or drops packets.
In competitive gaming, latency spikes and jitter can disrupt client-side prediction and server reconciliation, causing delayed hit registration or movement stutter. To ensure your display and input hardware are performing smoothly alongside your network, calibrate your setup with our FPS Checker and Refresh Rate Checker.
Top Gaming Network Optimizations
- • Connect via wired Ethernet when practical instead of Wi-Fi.
- • Select game matchmaking servers within your immediate geographic region.
- • Configure router QoS / SQM to prioritize real-time interactive traffic.
- • Close high-bandwidth cloud synchronization apps during competitive matches.
Peripheral & Hardware Diagnostics
Network lag is only one part of total system latency. Make sure your input peripherals and communication hardware are responsive using our:
Ethernet vs. Wi-Fi & VPN Latency
Ethernet vs. Wi-Fi Latency Comparison
Ethernet often provides more predictable local latency, while Wi-Fi can be more variable depending on signal conditions, channel contention, interference, and distance.
| Factor | Wired Ethernet | Wireless Wi-Fi |
|---|---|---|
| Physical Interference | Generally lower | Can vary with walls & RF |
| Local Stability | Often more consistent | Depends on environment & distance |
| Jitter Variance | Typically low | Can fluctuate with airtime load |
| Convenience & Mobility | Fixed cable | High Mobility |
Does a VPN Increase Network Ping?
A VPN often adds latency because it introduces an additional routing path, encryption processing, and intermediary server hops, but the amount varies widely depending on provider infrastructure, server distance, and routing quality.
In rare cases where an ISP uses an inefficient route to a specific destination, a well-routed VPN server with direct peering can occasionally offer an improved path.
DNS Latency & DNS-over-HTTPS
What Is DNS Latency?
The Domain Name System (DNS) translates human-readable hostnames into machine-routable IP addresses.
DNS latency is the time required for a DNS resolver to return this resolution. Responsive DNS resolvers ensure that new website lookups start promptly, although DNS lookup occurs during initial connection setup rather than on every subsequent packet.
What Is DNS-over-HTTPS (DoH)?
Traditional DNS queries are transmitted in plaintext over port 53, leaving them visible to local networks and ISPs.
DNS-over-HTTPS (DoH) encrypts lookup requests inside standard HTTPS sessions over port 443. Use the DNS-over-HTTPS (DoH) tab above to benchmark response latency across verified public resolvers like Cloudflare and Google.
Browser Ping vs. Traditional ICMP Ping
A critical technical consideration in network diagnostics is understanding the difference between operating system command-line ping tests and browser-based latency diagnostics:
| Technical Dimension | Browser-Based Diagnostic (This Tool) | Command-Line ICMP Ping (OS Terminal) |
|---|---|---|
| Underlying Protocol | HTTPS / HTTP Fetch API / TLS over TCP | Internet Control Message Protocol (ICMP Echo) |
| Execution Layer | Application Layer (Web Browser Sandbox) | Network Layer (Operating System Kernel) |
| Measurement Scope | Provides latency measurements for the specific browser-accessible endpoints used by this tool | Measures low-level network layer ICMP echo response to the target IP address |
| Firewall Compatibility | Passes standard port 443; rarely restricted by firewalls | Frequently deprioritized or blocked by some ISP routers and firewalls |
| Timing Overhead | Includes browser runtime event loop and TLS record processing | Pure kernel network stack timing |
Why results may differ: If a command-line ping shows a slightly lower number than a browser-based test, this delta represents normal TLS transport handshaking, HTTP protocol handling, and browser thread scheduling.
Network Latency Troubleshooting Guide
When diagnosing persistent connection lag, packet loss, or erratic ping spikes, follow this systematic 10-step diagnostic workflow:
Run a 100-packet probe on the nearest edge node when no heavy downloads or streaming tasks are active.
Check that jitter and loss remain within steady practical ranges for your connection. Repeat the test across different times to confirm whether irregularities are temporary or persistent.
Run the Multi-Server test to see if latency issues are route-specific or affect every destination universally.
Run the Bufferbloat tab to check if your router buffers inflate ping under simultaneous data strain.
Plug in an Ethernet cable directly to the router to isolate wireless radio channel interference.
Disable third-party VPN clients and browser proxy extensions to evaluate direct ISP routing performance.
Perform the test on a smartphone or second laptop to ensure a background OS task isn't saturating the link.
Power cycle both your modem and standalone wireless router, waiting 60 seconds before powering on.
Compare morning and peak evening (8:00 PM – 11:00 PM) results to identify neighborhood ISP node congestion.
If latency instability or packet loss persists across wired devices with zero local load, contact your provider to check for regional outages, routing maintenance, or line signal issues.
Frequently Asked Questions
What is a ping test and what does it measure?
A ping test measures the round-trip time (RTT) required for a data packet to travel from your device to a remote test node and return. In addition to average delay in milliseconds (ms), a comprehensive ping diagnostic evaluates network jitter (latency variance), packet loss percentage, latency spikes, and loaded latency under background traffic strain.
What is the difference between ping and latency (RTT)?
Latency is the general networking term for any time delay experienced in data transmission, including one-way delay or processing delays. Ping is both the diagnostic probing action and the specific numerical measurement of round-trip time (RTT)—the complete elapsed time for a request to reach a server and receive a response.
What is considered a good ping for everyday internet use?
As an approximate practical reference, ping under 30 ms is generally considered very responsive for interactive tasks and gaming; 30 ms to 60 ms is typically smooth for general browsing, streaming, and calls; 60 ms to 100 ms is acceptable for everyday use though slight delay may be noticed in fast-paced scenarios; and ping exceeding 150 ms often introduces noticeable lag. Actual experience always varies depending on the specific application, physical distance, server location, and routing path.
What is a good ping for online gaming?
For fast-paced multiplayer and competitive FPS games, a consistent ping below 40 ms with low jitter is often desirable. However, practical thresholds depend heavily on the game genre, server region, and netcode implementation. A steady 50 ms ping with near-zero jitter often provides a smoother gaming experience than an unstable 20 ms ping suffering from frequent spikes or packet loss.
What is network jitter and how does it affect real-time apps?
Network jitter is the statistical variation in latency across successive packet transmissions. While steady latency allows applications to predict data flow, high jitter causes packets to arrive out of order or in bursts. This can disrupt real-time applications like voice calls (Discord, Zoom), video conferencing, and competitive gaming, potentially leading to voice distortion or movement stutter.
What is packet loss and why does it cause sudden lag?
Packet loss occurs when transmitted data packets fail to reach their destination due to network congestion, hardware buffer overflow, or wireless interference. In real-time UDP streams (games, calls), lost packets cannot be retransmitted in time, which can result in audio dropouts, brief video pauses, or unresponsive in-game actions.
What causes ping spikes during online gaming and calls?
Ping spikes are abrupt, temporary surges in latency. Common causes include wireless RF interference on Wi-Fi, background cloud backups or game updates starting on local devices, bufferbloat in the local router when bandwidth is heavily utilized, dynamic routing changes, and server-side traffic surges.
How does bufferbloat cause lag on fast internet connections?
Bufferbloat occurs when routers and modems buffer excessive amounts of data during heavy downloads or uploads instead of dropping or pacing packets efficiently. This causes high queue delay, making latency surge from an idle state to several times higher, even on high-speed connections.
What is loaded latency and how is it tested?
Loaded latency measures your connection round-trip response time while simultaneous network throughput traffic is applied. By comparing idle ping to loaded ping, our diagnostic calculates the latency delta and assigns a load resilience grade indicating how well your router maintains real-time responsiveness under load.
Why is browser-based ping different from command-line ICMP ping?
Command-line ping sends low-level ICMP Echo Request packets directly handled by operating system networking kernels. Web browsers operate in an application sandbox and cannot send raw ICMP packets; instead, browser ping tests measure real HTTP/HTTPS fetch round-trip times to specific edge server endpoints. This reflects browser-accessible endpoint response timing, including TLS negotiation and protocol overhead.
Why do different test servers report different ping values?
Latency is fundamentally dictated by physical distance, fiber optic routing paths, internet exchange points (IXPs), ISP peering arrangements, and server processing load. Testing against an edge node in your regional area will naturally yield a lower ping than routing across intercontinental transit links.
Does using a VPN increase or decrease my ping?
A VPN often adds latency because it introduces an additional routing path, cryptographic overhead, and intermediary server hops, though the exact impact varies widely based on server distance, network load, and routing quality. In rare cases where an ISP has sub-optimal routing to a specific destination, a direct VPN tunnel may occasionally improve the path.
How does Wi-Fi latency compare to a wired Ethernet connection?
A wired Ethernet connection often provides more predictable local network latency with minimal physical interference. Wi-Fi latency can be more variable depending on signal conditions, wall attenuation, radio frequency interference, channel contention from neighboring networks, and distance from the access point.
What is DNS latency and how does DNS-over-HTTPS (DoH) work?
DNS latency is the time required for a recursive resolver to translate a human-readable domain name (like example.com) into a machine-routable IP address. DNS-over-HTTPS (DoH) encrypts these DNS queries inside standard HTTPS traffic on port 443, preventing local snooping and tampering while adding minimal cryptographic negotiation overhead.
How can I reduce my ping and fix high network latency?
To reduce ping: switch from Wi-Fi to a direct wired Ethernet cable, pause heavy background downloads and cloud syncing, disconnect idle devices from your local network, choose the closest game server region, enable Smart Queue Management (SQM/FQ_CoDel) on your router to mitigate bufferbloat, disable unneeded VPN tunnels, and restart your router and modem.
How can I tell if network lag is caused by my router or my ISP?
Test multiple devices across both wired Ethernet and Wi-Fi. If high ping, packet loss, or jitter occurs across all devices—even when connected via Ethernet with no other local network activity—this makes a local device issue less likely and suggests investigating the modem, ISP path, or regional routing. If only wireless devices or specific computers experience lag, the cause is more likely local Wi-Fi interference or background software.
What does the Network Stability Score mean on this tool?
The Network Stability Score is an algorithmic heuristic generated by this diagnostic lab. It synthesizes measured median latency, jitter coefficient, packet delivery ratio, and spike frequency into an intuitive 0–100 index to help you understand overall connection reliability. It is a practical observational assessment rather than an official industry standard.
Why should I test my ping at different times of the day?
Residential internet connections share neighborhood network infrastructure and local distribution nodes. During peak evening hours (7:00 PM to 11:00 PM), increased neighborhood traffic and broader internet transit links experience heavier utilization, which can introduce temporary latency spikes, higher jitter, and bufferbloat not present during quiet morning hours.
Region & Language
Select your preferred language for the interface.