Zzoomm 1Gig Full Fibre, SandhurstLast 24h

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

8 full internet outages in the last 24h
8m 20s with the provider's network unreachable, plus 8 spells of packet loss or lag (15m 16s)
Right now: connected, clean for 41m 44s (no outage or degradation since Thu 18:18) · checked Thu 19:00
Uptime
99.57%
external hosts reachable
Full outages
8
8m 20s offline
Degraded spells
8
15m 16s of loss / lag
Avg latency
6 ms
to external hosts
Packet loss
0.43%
ISP hop: 360 lost of 84,538
Last speed test
909↓ 904↑
Mbps at Thu 17:06

Verdict per minute

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

okdegradedDNS failureinternet outagehome networkspeed testmonitor off

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

01530456075 ms19:0023:0003:0007:0011:0015:0019:00

Home routerCloudflareGoogle DNSOpenDNSModem hopISP hop

Packet loss (%, worst minute)

015304560 %19:0023:0003:0007:0011:0015:0019: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
368 of 85,2473430 (0%)336 (91%)32 (9%)

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
Thu 18:161m 4sInternetoutageISP outage — router reachable, all external hosts unreachable
Thu 18:161m 59sInternetdegradedDegraded connection — 58% packet loss
Thu 06:421m 2sInternetoutageISP outage — router reachable, all external hosts unreachable
Thu 06:421m 58sInternetdegradedDegraded connection — 62% packet loss
Thu 05:191m 41sInternetdegradedDegraded connection — 67% packet loss
Thu 05:191m 0sInternetoutageISP outage — router reachable, all external hosts unreachable
Thu 03:211m 2sInternetoutageISP outage — router reachable, all external hosts unreachable
Thu 03:211m 57sInternetdegradedDegraded connection — 65% packet loss
Thu 01:461m 3sInternetoutageISP outage — router reachable, all external hosts unreachable
Thu 01:461m 58sInternetdegradedDegraded connection — 62% packet loss
Wed 23:511m 0sInternetoutageISP outage — router reachable, all external hosts unreachable
Wed 23:511m 57sInternetdegradedDegraded connection — 67% packet loss, OpenDNS unreachable
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

Throughput (Mbps)

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

DownloadUpload

TimeDown MbpsUp MbpsPing idle msPing under load ms
Thu 17:069099045113
Thu 13:069298296551
Thu 09:069328116822
Thu 05:069327926650
Thu 01:069139146486
Wed 21:069258585497

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.