Zzoomm 1Gig Full Fibre, SandhurstLast 24h

2026-09-14 13:00:00 → 2026-09-15 13:00:00 · page generated 2026-09-15 13:00:00 (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 29h 55m (no outage or degradation since Mon 07:04) · checked Tue 13:00
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: 1077 lost of 1,077
Last speed test
929↓ 890↑
Mbps at Tue 11:07

Verdict per minute

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

okdegradedDNS failureinternet outagehome networkspeed testmonitor off

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

0255075100 ms13:0017:0021:0001:0005:0009:0013:00

Home routerCloudflareGoogle DNSOpenDNSModem hopISP hop

Packet loss (%, worst minute)

0255075100 %13:0017:0021:0001:0005:0009:0013: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
52 of 85,24514 (8%)52 (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 15:021m 24sInternetdegradedDegraded 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 Mbps13:0017:0021:0001:0005:0009:0013:00advertised 1000

DownloadUpload

TimeDown MbpsUp MbpsPing idle msPing under load ms
Tue 11:079298906446
Tue 07:079298576614
Tue 03:079294136843
Mon 23:077948826356
Mon 19:079308936433
Mon 14:189298916322

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.