Zzoomm 1Gig Full Fibre, SandhurstLast 24h

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

No full outages in the last 24h, but the line was degraded
1 spell of packet loss or high latency totalling 1m 0s
Right now: connected, clean for 4h 14m (no outage or degradation since Thu 09:46) · checked Thu 14:00
Uptime
100.00%
external hosts reachable
Full outages
0
none
Degraded spells
1
1m 0s of loss / lag
Avg latency
21090926 ms
to external hosts
Packet loss
0.00%
ISP hop: 1 lost of 84,884
Last speed test
930↓ 799↑
Mbps at Thu 12:07

Verdict per minute

14:0018:0022:0002:0006:0010:0014:00

okdegradedDNS failureinternet outagehome networkspeed testmonitor off

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

012500000000250000000003750000000050000000000 ms14:0018:0022:0002:0006:0010:0014:00

Home routerCloudflareGoogle DNSOpenDNSModem hopISP hop

Packet loss (%, worst minute)

0246810 %14:0018:0022:0002:0006:0010:0014: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
5 of 85,28001 (20%)0 (0%)4 (80%)

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
Thu 09:451m 0sInternetdegradedDegraded connection — high latency (29837325130 ms)

Throughput (Mbps)

037575011251500 Mbps14:0018:0022:0002:0006:0010:0014:00advertised 1000

DownloadUpload

TimeDown MbpsUp MbpsPing idle msPing under load ms
Thu 12:079307995154
Thu 08:079318976944
Thu 04:079328626649
Thu 00:079328086692
Wed 20:079289066330
Wed 16:079283626715

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.