Zzoomm line status, Sandhurst

2026-09-17 23:00:00 → 2026-09-18 23:00:00 · page generated 2026-09-18 23: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.

No outages or degradation in the last 24h

the line met every check for the whole window

Right now: connected, clean for 43h 34m (no outage or degradation since Thu 03:26) · checked Fri 23: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: 96 lost of 81,128

Last speed test

918↓ 719↑

Mbps at Fri 20: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
9 of 85,134	0	1 (11%)	2 (22%)	6 (67%)

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
Fri 20:07	918	719	5	694
Fri 16:07	930	858	6	615
Fri 12:07	916	835	6	559
Fri 08:07	905	778	6	525
Fri 04:07	929	886	5	1193
Fri 00:07	855	902	6	122

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.