A computer plugged in by cable checks the building's internet every second, day and night.
Every apartment's internet goes through the building's router first. It's in the same building, so it should reply almost instantly, every time. Times are in ms, thousandths of a second.
| What we check | Should be | Right now |
|---|
Each square is one second. Each row is one minute, read left to right, with the newest at the bottom. Red and black squares are moments when the internet froze or dropped out. A blue dot at the end of a row means this computer was running its own speed test that minute, which can slow things a little.
Each bar shows how much of that stretch of time was good, slow or broken. Red and black means the internet was unusable.
Lower is better. The coloured zones show what each reply time feels like. Each gridline is 10 times the one below, so huge spikes still fit. Blue stripes mark this computer's speed tests.
Reply times from four places: the building's router, the next stop on Lightning Broadband's network, and Cloudflare and Google out on the internet. The lines rise and fall together, so the delay is already there at the building's router. Everything further away just inherits it.
Measured every 5 minutes. The plan is 100 Mbps.
Apple's responsiveness score, measured while the connection is busy downloading. Higher is better. A healthy connection scores over 1,000.
A minute counts as bad when at least 1 in 10 replies from the building's router took over half a second, or more than 5% of replies never came back. Back-to-back bad minutes are joined into one bad patch.
| Started | Lasted | Lag at its worst | Slowest reply |
|---|