Zzoomm line status, Sandhurst

2026-09-08 15:00:01 → 2026-09-09 15:00:01 · page generated 2026-09-09 15:00:01 (Europe/London) · updated on the hour

This page is old. It is republished every hour; when an update is missing, the monitor usually could not reach the internet to publish, which itself points to a line fault. The next successful update will include that period.

No outages or degradation in the last 24h

the line met every check for the whole window

Right now: connected, clean for 36h 33m (no outage or degradation since Tue 02:27) · checked Wed 15:00

Uptime

100.00%

external hosts reachable

Full outages

none

Degraded spells

none

Avg latency

6 ms

to external hosts

Packet loss

0.00%

ISP hop: 0 lost of 84,533

Last speed test

921↓ 741↑

Mbps at Wed 13:04

Verdict per minute

Latency (ms, per-minute average; shaded spans are logged events)

Packet loss (%, worst minute)

Where the loss sits

For every second in the window where at least one external host dropped a ping, was the home router or the provider's first hop also silent at that same instant? Seconds during the monitor's own throughput tests are excluded.

Seconds with any external loss	All external hosts lost	Home router also lost	ISP hop also lost	Lost beyond the first hop
10 of 85,042	0	0 (0%)	0 (0%)	10 (100%)

Reading it: a high "home router" share means the problem is inside the property. A high "first hop" share means the provider's gateway itself is dropping traffic. A high "beyond" share means packets get past the first hop and are lost deeper in the provider's network or upstream.

Events (provider-attributable, newest first)

Start	Duration	Layer	Severity	What happened
No provider-side events in this window.

Throughput (Mbps)

Time	Down Mbps	Up Mbps	Ping idle ms	Ping under load ms
Wed 13:04	921	741	6	672
Wed 09:04	922	902	6	959
Wed 05:04	927	840	6	459
Wed 01:04	926	882	6	523
Tue 19:23	927	844	6	273
Tue 15:23	929	826	6	524

How this is measured

A monitor on a wired machine behind the home router in Sandhurst pings the router, the provider's path hops and three independent external hosts (Cloudflare, Google DNS, OpenDNS) once a second, checks DNS every 15 s and HTTPS every 30 s, and runs a throughput test every 240 minutes. A one-second state machine classifies each moment: router unreachable = home problem; router fine but every external host unreachable = provider outage; sustained loss ≥ 10% or latency ≥ 150 ms = degraded. The minutes in which the monitor runs its own throughput test are left out of every figure and chart.