Zzoomm 1Gig Full Fibre, SandhurstLast 24h

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

4 full internet outages in the last 24h
3m 12s with the provider's network unreachable, plus 4 spells of packet loss or lag (6m 35s)
Right now: connected, clean for 9m 23s (no outage or degradation since Sat 05:50) · checked Sat 06:00
Uptime
99.83%
external hosts reachable
Full outages
4
3m 12s offline
Degraded spells
4
6m 35s of loss / lag
Avg latency
6 ms
to external hosts
Packet loss
0.17%
ISP hop: 147 lost of 84,576
Last speed test
931↓ 857↑
Mbps at Sat 05:06

Verdict per minute

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

okdegradedDNS failureinternet outagehome networkspeed testmonitor off

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

015304560 ms06:0010:0014:0018:0022:0002:0006:00

Home routerCloudflareGoogle DNSOpenDNSModem hopISP hop

Packet loss (%, worst minute)

01020304050 %06:0010:0014:0018:0022:0002:0006: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
151 of 85,2401342 (1%)132 (87%)17 (11%)

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
Sat 05:4859sInternetoutageISP outage — router reachable, all external hosts unreachable
Sat 05:481m 55sInternetdegradedDegraded connection — 63% packet loss
Fri 19:351m 0sInternetdegradedDegraded connection — 20% packet loss
Fri 19:3512sInternetoutageISP outage — router reachable, all external hosts unreachable
Fri 17:501m 2sInternetoutageISP outage — router reachable, all external hosts unreachable
Fri 17:501m 57sInternetdegradedDegraded connection — 68% packet loss
Fri 06:111m 42sInternetdegradedDegraded connection — 65% packet loss
Fri 06:1159sInternetoutageISP outage — router reachable, all external hosts unreachable

Throughput (Mbps)

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

DownloadUpload

TimeDown MbpsUp MbpsPing idle msPing under load ms
Sat 05:069318576643
Sat 01:069308825388
Fri 21:069298916177
Fri 17:069288916562
Fri 13:068979035152
Fri 09:069128846493

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.