Zzoomm 1Gig Full Fibre, SandhurstLast 24h

2026-09-08 23:00:01 → 2026-09-09 23:00:01 · page generated 2026-09-09 23:00:01 (Europe/London) · updated on the hour

No full outages in the last 24h, but the line was degraded
2 spells of packet loss or high latency totalling 1m 20s
Right now: monitor offline, last sample 9 Sep 21:48:54 · checked Wed 23:00
Uptime
99.99%
external hosts reachable
Full outages
0
none
Degraded spells
2
1m 20s of loss / lag
Avg latency
6 ms
to external hosts
Packet loss
0.01%
ISP hop: 0 lost of 80,417
Last speed test
924↓ 823↑
Mbps at Wed 21:04

Verdict per minute

23:0003:0007:0011:0015:0019:0023:00

okdegradedDNS failureinternet outagehome networkspeed testmonitor off

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

0306090120150 ms23:0003:0007:0011:0015:0019:0023:00

Home routerCloudflareGoogle DNSOpenDNSModem hopISP hop

Packet loss (%, worst minute)

0246810 %23:0003:0007:0011:0015:0019:0023:00

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
14 of 80,79900 (0%)0 (0%)14 (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
Wed 21:4227sInternetdegradedDegraded connection — high latency (154 ms)
Wed 16:3353sInternetdegradedDegraded connection — intermittent loss

Throughput (Mbps)

037575011251500 Mbps23:0003:0007:0011:0015:0019:0023:00advertised 1000

DownloadUpload

TimeDown MbpsUp MbpsPing idle msPing under load ms
Wed 21:049248235151
Wed 17:049218716319
Wed 13:049217416672
Wed 09:049229026959
Wed 05:049278406459
Wed 01:049268826523

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.