Zzoomm 1Gig Full Fibre, SandhurstLast 24h

2026-09-13 11:00:01 → 2026-09-14 11:00:01 · page generated 2026-09-14 11:00:01 (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 52s
Right now: connected, clean for 3h 55m (no outage or degradation since Mon 07:04) · checked Mon 11:00
Uptime
100.00%
external hosts reachable
Full outages
0
none
Degraded spells
1
52s of loss / lag
Avg latency
6 ms
to external hosts
Packet loss
0.00%
ISP hop: 300 lost of 301
Last speed test
922↓ 893↑
Mbps at Mon 10:18

Verdict per minute

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

okdegradedDNS failureinternet outagehome networkspeed testmonitor off

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

050100150200 ms11:0015:0019:0023:0003:0007:0011:00

Home routerCloudflareGoogle DNSOpenDNSModem hopISP hop

Packet loss (%, worst minute)

0255075100 %11:0015:0019:0023:0003:0007:0011: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
4 of 85,25201 (25%)4 (100%)0 (0%)

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
Mon 07:0352sInternetdegradedDegraded connection — high latency (158 ms)

Throughput (Mbps)

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

DownloadUpload

TimeDown MbpsUp MbpsPing idle msPing under load ms
Mon 10:189228936567
Mon 06:189148696609
Mon 02:189297176342
Sun 22:189258686203
Sun 18:189128146395
Sun 14:189217996971

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.