Zzoomm 1Gig Full Fibre, SandhurstLast 24h

2026-10-06 23:00:01 → 2026-10-07 23:00:01 · page generated 2026-10-07 23:00:01 (Europe/London) · updated on the hour

8 full internet outages in the last 24h
8m 13s with the provider's network unreachable, plus 8 spells of packet loss or lag (15m 7s)
Right now: connected, clean for 45m 41s (no outage or degradation since Wed 22:14) · checked Wed 23:00
Uptime
99.58%
external hosts reachable
Full outages
8
8m 13s offline
Degraded spells
8
15m 7s of loss / lag
Avg latency
6 ms
to external hosts
Packet loss
0.42%
ISP hop: 360 lost of 84,561
Last speed test
925↓ 858↑
Mbps at Wed 21:06

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)

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

Home routerCloudflareGoogle DNSOpenDNSModem hopISP hop

Packet loss (%, worst minute)

01530456075 %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
355 of 85,2413330 (0%)331 (93%)24 (7%)

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 22:121m 45sInternetdegradedDegraded connection — 67% packet loss
Wed 22:121m 3sInternetoutageISP outage — router reachable, all external hosts unreachable
Wed 20:001m 5sInternetoutageISP outage — router reachable, all external hosts unreachable
Wed 20:002m 0sInternetdegradedDegraded connection — 62% packet loss
Wed 18:0658sInternetoutageISP outage — router reachable, all external hosts unreachable
Wed 18:061m 54sInternetdegradedDegraded connection — 68% packet loss, Cloudflare, OpenDNS unreachable
Wed 16:221m 3sInternetoutageISP outage — router reachable, all external hosts unreachable
Wed 16:221m 58sInternetdegradedDegraded connection — 60% packet loss
Wed 14:441m 5sInternetoutageISP outage — router reachable, all external hosts unreachable
Wed 14:442m 0sInternetdegradedDegraded connection — 60% packet loss
Wed 14:2059sInternetoutageISP outage — router reachable, all external hosts unreachable
Wed 14:201m 54sInternetdegradedDegraded connection — 65% packet loss
Wed 11:421m 2sInternetoutageISP outage — router reachable, all external hosts unreachable
Wed 11:421m 57sInternetdegradedDegraded connection — 62% packet loss
Wed 09:281m 38sInternetdegradedDegraded connection — 67% packet loss
Wed 09:2757sInternetoutageISP outage — router reachable, all external hosts unreachable

Throughput (Mbps)

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

DownloadUpload

TimeDown MbpsUp MbpsPing idle msPing under load ms
Wed 21:069258585497
Wed 17:069258555439
Wed 13:069288865453
Wed 09:069276356529
Wed 05:069328625687
Wed 01:069278895404

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.