Network Stability & Latency (Ping) Test
Test your internet connection stability in real-time. Monitor Ping latency, Jitter, and Packet Loss. Quickly diagnose lag in gaming or buffering in videos.
Avoids unrelated permissions and runs in your browser with the device APIs available on this device.
Works best in current Chrome, Edge, Safari, and Firefox. Support depends on Navigator and Network Information APIs, secure HTTPS, hardware availability, and browser policy.
Diagnosis
- Prioritize using network cables or 5GHz Wi‑Fi, stay close to the router, and avoid interference sources such as microwave ovens/Bluetooth.
- Turn off/switch VPN, proxy, accelerator; check whether company network policy (DPI/firewall) causes reset or packet loss.
- Pause bandwidth-consuming tasks (cloud disk synchronization, downloads, system updates), and observe whether p95/packet loss is significantly improved.
- If only one site is "stuck", it is more likely to be the other party's server/cross-border link/DNS; you can copy the report and send it to the other party for troubleshooting.
Network information and events
How to use this page to quickly locate problems
Network Guide
Run continuous pings to detect intermittent lag spikes.
Start testing (same domain ping)
Keep the default /api/ping and click "Start Test".
Read the results (stuck vs broken)
Focus on packet loss rate, p95, jitter and offline events.
Copy the report for troubleshooting
Copy text reports containing key statistics and events with one click.
What this tool checks
This network page checks browser-visible connection signals and timing stability so you can spot obvious quality issues quickly.
online status
Shows whether the browser currently considers the device online or offline.
latency trend
Uses repeated timing checks to reveal whether round-trip delay is staying low or drifting upward.
jitter pattern
Helps expose whether latency is stable or jumping around from moment to moment.
packet loss clues
Makes failed timing attempts and unstable request patterns easier to notice.
browser network hints
Can surface connection type or estimate fields when the browser exposes them.
user-side troubleshooting signals
Gives a quick first-pass view before deeper ISP or router diagnostics.
What this tool cannot confirm
This is a browser diagnostics view, not a full replacement for ISP-grade throughput testing or enterprise monitoring.
not a full speed test
It does not measure full download and upload throughput with the same rigor as dedicated bandwidth test services.
browser APIs are limited
Many browsers expose only partial network information, and in-app browsers may hide most of it.
results vary by route and time
Latency and loss can change based on Wi-Fi quality, VPN use, congestion, and the endpoint being timed.
cannot inspect your whole network path
The page cannot see router logs, ISP routing decisions, or every transport-layer detail.
How the result is generated
The result is generated from client-side browser timing, request success patterns, and any network hints the browser exposes locally.
browser status read
The page reads online state and any supported Network Information API values.
timing loop
Repeated network requests or pings are used to estimate latency behavior over time.
stability observation
The tool compares responses to detect variation, spikes, and failed attempts.
client aggregation
Observed timings are summarized into simple trends such as latency or jitter.
local result display
The page shows the pattern seen during the current session on this browser and network.
Interpret your results
The result helps you decide whether the problem is likely general network quality, not just a single page loading slowly.
| Observed pattern | Likely meaning |
|---|---|
| Offline or no data | The browser sees no active connection, the test endpoint failed, or the required API is unavailable. |
| High latency | Long network path, congestion, VPN overhead, weak Wi-Fi, or mobile network delay. |
| High jitter | The connection is unstable and delay is changing sharply from request to request. |
| Packet loss signs | Requests are being dropped or timing out, often due to unstable wireless or upstream issues. |
| Stable low latency | The network path looks healthy enough for most real-time browser tasks. |
Supported browsers and known limitations
Network visibility differs a lot by browser because not every platform exposes the same connection APIs.
| browser | network info exposure | latency test support | stability visibility | known limitations |
|---|---|---|---|---|
| Chrome | Partial on supported platforms | Good | Good | Some connection type fields may be missing or approximate. |
| Edge | Similar to Chrome | Good | Good | Policy controls can restrict or alter enterprise environments. |
| Firefox | More limited API exposure | Good | Good | Network Information API support is more restricted. |
| Safari | Limited network info exposure | Good | Basic | Connection type and bandwidth hints are often unavailable. |
| iOS Safari | Very limited browser network hints | Basic | Basic | Backgrounding and mobile power management can affect results. |
| Android Chrome | Some hints on supported devices | Good | Good | Carrier routing and device power modes can shift readings quickly. |
Use cases
Use this as a first browser-level sanity check when lag or instability might interrupt a real-time task.
before online gaming
Check whether latency and jitter already look unstable before you join a match.
before a video call
Catch weak Wi-Fi or erratic delay before a meeting starts buffering or freezing.
after a router restart
Confirm whether the connection looks healthier after local network changes.
when streaming buffers
Use the test to see whether the browser is observing unstable network behavior overall.
when comparing Wi-Fi and hotspot
Quickly compare whether one connection path appears more stable than another.
FAQ
A summary of frequently asked questions about network diagnosis and "stuck/outage" troubleshooting.
What exactly is the "network" tested on this page?
It estimates RTT (round trip delay), jitter, and failure rate by making multiple requests to the specified endpoint (similar to ping sampling), and combines browser online/offline and Network Information API events to help you quickly determine whether it is "stuck" or "disconnected."
Why is the default endpoint /api/ping?
By default, using the same domain /api/ping can reduce the differences between cross-domain and third-party servers, and is closer to the real link quality of "you to this site", and is more stable and reproducible. To diagnose a certain business/site, change the endpoint to its health check or static resource direct link for comparison.
Where does the "stability score" come from? Is it reliable?
The scoring is heuristic on a 0–100 scale: combined packet loss/failure rate, p95 latency, jitter (adjacent RTT variation), and offline events give an intuitive result. It is suitable for quick comparison (change network/change VPN/before and after approaching the router) and is not equivalent to a strict network measurement instrument.
avg is low but p95 is high, what does it mean?
Usually represents "sporadic spikes": fast most of the time, but a few very slow requests often occur. From a somatosensory perspective, it is easy to experience occasional lags in conference voice, occasional circling of web pages, and momentary frame drops in games, etc.
Does an increase in packet loss/failure rate necessarily indicate a network problem?
uncertain. The failure may come from the network (Wi‑Fi interference, router reconnection, VPN instability), it may come from the endpoint server (overload/throttle/failure) or the browser timeout setting is too small. Suggestion: Test the endpoint in the same domain and the target endpoint once each, and increase the timeout appropriately for comparison.
Will the test upload my private data?
Won't. It will only initiate a request to the endpoint you fill in and record the time-consuming/successful failure and other indicators; "Copy Report" just writes the statistical text to the clipboard.
Why does it sometimes show "Network Information API is not supported"?
Some browsers/environments do not expose information such as navigator.connection due to privacy or implementation restrictions. This does not affect ping sampling and result judgment, but only lacks auxiliary information such as network type/estimated RTT.
What are the most common troubleshooting suggestions?
Prioritize three steps of comparison: 1) Turn off/change VPN; 2) Get close to the router and switch to 5GHz or switch to a network cable; 3) Pause bandwidth-consuming tasks such as downloading/synchronization. Running a test every step of the way is the easiest way to identify the main bottlenecks.
Related guides
Read a few practical guides for setup, browser compatibility, and troubleshooting around this test.
Stop the Lag: A Practical Guide to Diagnosing Network Instability for Gamers and Remote Workers
Is your video conference freezing or your game character teleporting? Network instability, characterized by high latency, jitter, and packet loss, is often the invisible culprit. This guide moves beyond simple speed tests to explain how to use real-time stability tools to diagnose connection issues. We break down what Ping, Jitter, and Packet Loss actually mean for your daily workflow and entertainment. Follow our step-by-step walkthrough to run a comprehensive network diagnostic, interpret live metrics, and validate your connection quality before critical meetings or ranked matches. Whether you are a remote employee ensuring readiness or a streamer preventing buffering, learn how to pinpoint the root cause of lag and take actionable steps to stabilize your digital life.
Stop the Lag: A Practical Guide to Diagnosing Network Instability for Gamers and Remote Workers
Is your video call freezing or your character lagging in a crucial match? The culprit is often hidden network instability rather than raw speed. This guide explores how to use real-time Network Stability & Latency tests to diagnose common connectivity issues like high Ping, Jitter, and Packet Loss. We break down what these metrics mean for your specific scenario, whether you are preparing for a high-stakes online meeting or validating your setup before a live stream. Follow our step-by-step workflow to run accurate diagnostics, interpret the data, and take actionable steps to stabilize your connection. Stop guessing and start solving your internet woes with precision.
Feedback / report a bug
Tell us your browser, device, and what happened.
Did this result look wrong?
Comments(0)