Zzoomm 1Gig Full Fibre, SandhurstLast 24h

2026-09-06 17:00:01 → 2026-09-07 17:00:01 · page generated 2026-09-07 17:00:01 (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 60h 47m (no outage or degradation since Sat 04:13) · checked Mon 17:00
Uptime
99.99%
external hosts reachable
Full outages
0
none
Degraded spells
0
none
Avg latency
6 ms
to external hosts
Packet loss
0.01%
ISP hop: 2 lost of 84,488
Last speed test
920↓ 743↑
Mbps at Mon 15:23

Verdict per minute

17:0021:0001:0005:0009:0013:0017:00

okdegradedDNS failureinternet outagehome networkspeed testmonitor off

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

0125250375500 ms17:0021:0001:0005:0009:0013:0017:00

Home routerCloudflareGoogle DNSOpenDNSModem hopISP hop

Packet loss (%, worst minute)

0246810 %17:0021:0001:0005:0009:0013:0017: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
21 of 85,19721 (5%)1 (5%)19 (90%)

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 15:3857sInternetdegradedDegraded 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 Mbps17:0021:0001:0005:0009:0013:0017:00advertised 1000

DownloadUpload

TimeDown MbpsUp MbpsPing idle msPing under load ms
Mon 15:239207436300
Mon 11:239268426340
Mon 07:239298646682
Mon 03:239278556455
Sun 23:239308646239
Sun 19:239278536548

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.