Professional online network diagnostics. Test via ICMP Ping (remote proxy) or HTTPS GET (direct from browser) to measure latency and stability.
Average Latency
0 ms
Packet Loss / Failure
0%
Jitter
0 ms
Requests Sent
0
📖 Introduction:
ICMP Ping (remote proxy) and HTTPS GET (browser direct) side by side, meeting various diagnostic needs.
Dynamic line chart of latency changes, colour‑coded success/failure requests.
Automatically saves recently tested targets; click the input field to pick one, one‑click clear.
Each request’s sequence, response time, status (HTTPS), or loss indication clearly printed.
Automatically computes average absolute difference between consecutive delays – a precise stability metric.
Select “Continuous” to send requests until manually stopped – ideal for long‑term stability monitoring.
Enter your domain or IP (e.g., example.com or 93.184.216.34) in the target field, select the test mode (Ping or HTTPS), and click Start. For HTTPS tests, ensure your server listens on port 443.
ICMP Ping measures network‑layer round‑trip time, while HTTPS GET involves TCP handshake, TLS negotiation, and HTTP request/response – it normally takes tens of milliseconds longer, which is expected.
For wired networks, loss should be 0% most of the time; for Wi‑Fi, up to 0.1% is acceptable. Consistent loss above 0.5% or frequent timeouts indicate a significant problem – check your local network or contact your ISP.
Browsers cannot send raw ICMP packets due to security restrictions. This tool uses a backend proxy (or public API) to perform the Ping and returns the results, enabling ICMP tests to any target.
Yes – ICMP Ping latency includes the time from the proxy to the target, not from your location. However, loss and jitter still reflect the target's network stability. HTTPS GET is not affected because it runs directly from your browser.
If a request fails within 5 ms, it's usually blocked by a browser extension (e.g., ad blocker). The tool marks it as “Local Block” rather than a network failure. Try disabling extensions and retest.
Each Ping request is just tens of bytes; HTTPS requests are lightweight (HEAD/no‑cors). Even after an hour, total traffic is usually below 10 MB – safe to use.