Network Monitor

Idle

Latency

– ms

Jitter

– ms

Failed probes

– %

Uptime (session)

– %

Dropouts today

Round-trip time

Targets

Host	Last	Avg	Jitter	Fail

Slow on every host points at your own link. Slow on one points at that host.

Connection breakdown

Speed test

Download Upload

Download

– Mbps

Upload

– Mbps

Transferred

– MB

Uses Cloudflare's public speed endpoints and consumes real data. On metered connections, run it sparingly.

Event log

Time	Event	Host	Detail	Duration

Settings & targets

Sampling

Interval s Timeout ms Latency alert above ms

Alerts Desktop notification on dropout, recovery, and sustained high latency

Targets

What this measures — and what it can't

Not ICMP ping. A browser has no raw sockets, so every number here is an HTTPS round trip. It tracks the same shape as ping but reads higher, because it includes TLS and server response time.

Failed probes are not packet loss. A probe counts as failed when it errors or exceeds the timeout. That is a useful stand-in, not a measurement of dropped packets.

The breakdown needs permission from the host. DNS, TCP, and TLS timings are only exposed for hosts that send a Timing-Allow-Origin header. Others show round-trip only. After the first probe the connection is reused, so handshake times read zero — the panel shows the last cold connect instead.

Keep this tab visible. Chrome throttles timers in background tabs to roughly once a minute, so a hidden tab samples far more coarsely. Samples taken while hidden are flagged in the export.

Cross-origin probes can't see HTTP status. For hosts without CORS, a 404 or 500 still counts as a reachable response, since the browser only reveals that something came back.