daltonsbaker/speed-watch repository overview

⁠Speed Watch

Docker Hub⁠ · GitHub⁠

A lightweight, self-hosted speed test tracker. Runs scheduled tests against either Ookla or Cloudflare, stores every result in SQLite, and displays the truth — especially failures — in a clean dashboard with charts.

⁠Features

• Scheduled and on-demand speed tests
• Two providers: Ookla and Cloudflare (one active at a time)
• SQLite persistence — every attempt recorded: successes, failures, timeouts, partials, and skipped runs
• Line charts for download / upload / ping / jitter with failure markers
• Time range filtering, run detail modal, recent runs table, and a full history page
• Configurable via UI; settings saved to a JSON file alongside the database
• Simple REST API for integrations

⁠Quick start

⁠docker run

docker run -d \
  --name speed-watch \
  --restart unless-stopped \
  -p 6100:6100 \
  -v $(pwd)/data:/data \
  daltonsbaker/speed-watch:latest

Then open http://localhost:6100⁠.

⁠docker compose

Create a docker-compose.yml:

services:
  speed-watch:
    image: daltonsbaker/speed-watch:latest
    container_name: speed-watch
    restart: unless-stopped
    ports:
      - "6100:6100"
    volumes:
      - ./data:/data

Then run:

docker compose up -d

⁠Data volume

Everything is stored under /data inside the container:

Mount this to a persistent host directory so data survives restarts and image updates.

⁠Environment variables

These are bootstrap-only settings. All normal configuration is done through the UI and saved to config.json.

⁠First-time setup

1. Open the app at http://<host>:6100
2. Go to Config
3. Choose your provider (Ookla or Cloudflare), set a cron schedule, and save

Defaults out of the box:

• Scheduled tests enabled
• Cron: */10 * * * * (every 10 minutes)
• Active provider: cloudflare
• Test timeout: 120 seconds

The scheduler reloads automatically after saving a valid config.

⁠Running behind a reverse proxy

The container speaks plain HTTP on port 6100. Drop it behind Caddy, Traefik, nginx, or similar and add authentication there if needed.

⁠API

All timestamps are Unix epoch milliseconds. JSON keys are camelCase.

⁠Building from source

See DEVELOPMENT.md⁠.