Zzoomm 1Gig Full Fibre, SandhurstLast 24h

2026-09-19 03:02:23 → 2026-09-20 03:02:23 · page generated 2026-09-20 03:02:23 (Europe/London) · updated on the hour

No outages or degradation in the last 24h
the line met every check for the whole window
Right now: connected, clean for 71h 36m (no outage or degradation since Thu 03:26) · checked Sun 03:02
Uptime
99.97%
external hosts reachable
Full outages
0
none
Degraded spells
0
none
Avg latency
6 ms
to external hosts
Packet loss
0.03%
ISP hop: 4 lost of 84,971
Last speed test
903↓ 813↑
Mbps at Sun 00:07

Verdict per minute

03:0207:0211:0215:0219:0223:0203:02

okdegradedDNS failureinternet outagehome networkspeed testmonitor off

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

015304560 ms03:0207:0211:0215:0219:0223:0203:02

Home routerCloudflareGoogle DNSOpenDNSModem hopISP hop

Packet loss (%, worst minute)

03691215 %03:0207:0211:0215:0219:0223:0203:02

Home routerISP hopExternal hosts (worst per 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 lossAll external hosts lostHome router also lostISP hop also lostLost beyond the first hop
65 of 85,28400 (0%)0 (0%)65 (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)

StartDurationLayerSeverityWhat happened
Sun 02:021m 33sInternetdegradedDegraded 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)

037575011251500 Mbps03:0207:0211:0215:0219:0223:0203:02advertised 1000

DownloadUpload

TimeDown MbpsUp MbpsPing idle msPing under load ms
Sun 00:079038135192
Sat 20:079249208614
Sat 16:079308545283
Sat 12:079298886488
Sat 08:079318966684
Sat 04:079319106953

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.