Zzoomm line status, Sandhurst

2026-10-07 23:00:01 → 2026-10-08 23:00:01 · page generated 2026-10-08 23: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.

6 full internet outages in the last 24h

6m 12s with the provider's network unreachable, plus 6 spells of packet loss or lag (11m 31s)

Right now: connected, clean for 4h 42m (no outage or degradation since Thu 18:18) · checked Thu 23:00

Uptime

99.68%

external hosts reachable

Full outages

6m 12s offline

Degraded spells

11m 31s of loss / lag

Avg latency

6 ms

to external hosts

Packet loss

0.32%

ISP hop: 267 lost of 84,542

Last speed test

928↓ 917↑

Mbps at Thu 21:06

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
275 of 85,260	254	0 (0%)	248 (90%)	27 (10%)

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
Thu 18:16	1m 4s	Internet	outage	ISP outage — router reachable, all external hosts unreachable
Thu 18:16	1m 59s	Internet	degraded	Degraded connection — 58% packet loss
Thu 06:42	1m 2s	Internet	outage	ISP outage — router reachable, all external hosts unreachable
Thu 06:42	1m 58s	Internet	degraded	Degraded connection — 62% packet loss
Thu 05:19	1m 41s	Internet	degraded	Degraded connection — 67% packet loss
Thu 05:19	1m 0s	Internet	outage	ISP outage — router reachable, all external hosts unreachable
Thu 03:21	1m 2s	Internet	outage	ISP outage — router reachable, all external hosts unreachable
Thu 03:21	1m 57s	Internet	degraded	Degraded connection — 65% packet loss
Thu 01:46	1m 3s	Internet	outage	ISP outage — router reachable, all external hosts unreachable
Thu 01:46	1m 58s	Internet	degraded	Degraded connection — 62% packet loss
Wed 23:51	1m 0s	Internet	outage	ISP outage — router reachable, all external hosts unreachable
Wed 23:51	1m 57s	Internet	degraded	Degraded connection — 67% packet loss, OpenDNS unreachable

Throughput (Mbps)

Time	Down Mbps	Up Mbps	Ping idle ms	Ping under load ms
Thu 21:06	928	917	5	352
Thu 17:06	909	904	5	113
Thu 13:06	929	829	6	551
Thu 09:06	932	811	6	822
Thu 05:06	932	792	6	650
Thu 01:06	913	914	6	486

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.