Zzoomm line status, Sandhurst

2026-09-26 05:00:00 → 2026-09-27 05:00:00 · page generated 2026-09-27 05:00:00 (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.

1 full internet outage in the last 24h

1s with the provider's network unreachable, plus 4 spells of packet loss or lag (29m 42s)

Right now: connected, clean for 3h 29m (no outage or degradation since Sun 01:31) · checked Sun 05:00

Uptime

99.95%

external hosts reachable

Full outages

1s offline

Degraded spells

29m 42s of loss / lag

Avg latency

14 ms

to external hosts

Packet loss

0.05%

ISP hop: 41 lost of 83,041

Last speed test

932↓ 822↑

Mbps at Sun 04:07

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
53 of 83,142	25	23 (43%)	24 (45%)	6 (11%)

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
Sun 01:30	43s	Internet	degraded	Degraded connection — high latency (160 ms)
Sun 01:15	13m 14s	Internet	degraded	Degraded connection — high latency (162 ms)
Sun 01:01	1s	Internet	outage	ISP outage — router reachable, all external hosts unreachable
Sun 01:00	14m 40s	Internet	degraded	Degraded connection — high latency (150 ms)
Sat 22:44	1m 4s	Internet	degraded	Degraded connection — high latency (153 ms)

Throughput (Mbps)

Time	Down Mbps	Up Mbps	Ping idle ms	Ping under load ms
Sun 04:07	932	822	5	618
Sun 00:07	929	850	5	464
Sat 20:07	failed
Sat 16:07	898	824	6	279
Sat 12:07	930	894	5	371
Sat 08:07	929	523	6	836

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.