Ping (connection monitor)

Probes a host on a fixed interval and records every drop. bfunc.cc

Idle
Press start to begin
—
latency
Uptime
—
Checks
0
Drops
0
Avg
—
Elapsed
0:00

Timeline

fastslow (>400ms)unreachablebar height = latency · last 100 checks

Events

No connection drops recorded.

How this works. Browsers cannot send ICMP pings, and they cannot read a cross-origin response from google.com. So this issues a no-cors request to a tiny endpoint and times it: if the request completes, the network is up; if it fails or times out after 4s, it is down. The response body is opaque, which is fine — reachability and round-trip time are all we need.

Latency includes DNS, TCP and TLS on the first request, so the first reading usually runs high. Keep this tab visible: browsers clamp timers in background tabs to roughly one wake-up per second, so anything faster than that only holds while the tab is in front — hidden, the timeline stretches and a short outage can slip between checks. A captive portal that intercepts traffic can look like a working connection here.