Broadband speed-test history. Seeded 2026-07-05 with
example rows — replace them with real speedtest-cli output and edit the
ISP/plan block in build.py, then re-deploy.
Current ISP / Plan
Connection
— (cable / fiber / 5G)
Download Throughput
download throughput · peak 612 Mbps
Speed-test History
| When | Download | Upload | Ping | Server | Device |
|---|
| 2026-07-05 21:00 ET | 612.4 Mbps | 41.8 | 11 ms | Verizon — Newark, NJ | RSJ_NUC (wired) ex |
| 2026-07-04 09:15 ET | 588.1 Mbps | 40.2 | 13 ms | Comcast — New York, NY | RSJ_NUC (wired) ex |
| 2026-07-02 18:30 ET | 471.9 Mbps | 39.6 | 15 ms | Verizon — Newark, NJ | Pi-Primary (wired) ex |
How to Wire Live Logging
Wire live logging (speedtest-cli cron on a Pi). Run scheduled tests on
Pi-Primary or Pi-Secondary and append CSV rows this page can read.
sudo apt install speedtest-cli # Ookla CLI also works: 'speedtest'
# /home/pi/speedlog.sh
#!/usr/bin/env bash
OUT=/home/pi/speedtests.csv
TS=$(date '+%Y-%m-%d %H:%M %Z')
speedtest-cli --csv >> "$OUT.raw"
# columns: down/up are bits/s in --csv output; convert to Mbps in build.py
# crontab -e (every 6 hours)
0 */6 * * * /home/pi/speedlog.sh
Then point build.py's
RESULTS list at the CSV (parse it in place of the
seeded rows) and re-deploy. Keep the newest-first ordering the renderer expects.