Network Latency (Ping) & Stability
Monitor Ping, Jitter, and Packet Loss in real-time.
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.
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.