Zzoomm line status, Sandhurst

2026-09-07 09:00:01 → 2026-09-08 09:00:01 · page generated 2026-09-08 09: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 full outages in the last 24h, but the line was degraded

4 spells of packet loss or high latency totalling 2m 47s

Right now: degraded, packet loss or high latency · checked Tue 09:00

Uptime

99.98%

external hosts reachable

Full outages

none

Degraded spells

2m 47s of loss / lag

Avg latency

6 ms

to external hosts

Packet loss

0.02%

ISP hop: 11 lost of 84,518

Last speed test

924↓ 654↑

Mbps at Tue 07:23

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
33 of 85,199	2	3 (9%)	2 (6%)	28 (85%)

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
Tue 08:58	1m 0s	Internet	degraded	Degraded connection — high latency (182 ms)
Tue 08:57	10s	Internet	degraded	Degraded connection — high latency (208 ms)
Tue 08:49	52s	Internet	degraded	Degraded connection — high latency (150 ms)
Tue 02:26	45s	Internet	degraded	Degraded connection — intermittent loss
Mon 15:38	57s	Internet	degraded	Degraded connection — OpenDNS unreachable

1 of the degraded rows above are single-resolver blips (one DNS host unreachable while the others answered) rather than line faults.

Throughput (Mbps)

Time	Down Mbps	Up Mbps	Ping idle ms	Ping under load ms
Tue 07:23	924	654	6	633
Tue 03:23	932	872	6	303
Mon 23:23	924	910	5	99
Mon 19:23	921	900	6	346
Mon 15:23	920	743	6	300
Mon 11:23	926	842	6	340

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.