IP Tools
Local test ready · production pending

Ping Test

Create one bounded network job and inspect only validated worker evidence.

Method:
Same-origin API → isolated network worker; explicit create, refresh and cancel only
Status:
idle

Input

Result

Ready

No job has been created. Complete the bounded form to begin.

One target and one bounded operation per job. No URL fetch, port range, custom resolver or browser-side probe is available.

Tool guide

Clear input, result, and evidence boundaries

Measure latency, packet loss, and individual replies to one public target from a clearly identified probe.

01

Input and method

One public hostname or IP, probe region, and a bounded packet count of 4 or 10.

02

Reading the result

Method, probe region, min/average/max RTT, packet loss, and each bounded reply are reported.

03

Boundary and privacy

A browser cannot perform ICMP directly; the page must identify the server-side probe and never label HTTP timing as ICMP.

FAQ

Frequently asked questions

What does Ping Test check?

Measure latency, packet loss, and individual replies to one public target from a clearly identified probe.

What input does Ping Test accept?

One public hostname or IP, probe region, and a bounded packet count of 4 or 10.

How should I interpret Ping Test results?

Method, probe region, min/average/max RTT, packet loss, and each bounded reply are reported.

What can Ping Test not prove?

A browser cannot perform ICMP directly; the page must identify the server-side probe and never label HTTP timing as ICMP.

How does Ping Test handle input and results?

Input is used only for this explicit check. A browser cannot perform ICMP directly; the page must identify the server-side probe and never label HTTP timing as ICMP.

When should I run Ping Test again?

Run it again after the relevant network, address, browser environment, or target changes. Method, probe region, min/average/max RTT, packet loss, and each bounded reply are reported.

Continue checking