Speedtape

Local network monitor

Know your line.

Scheduled tests across peak and off-peak hours. Evidence you can take to your ISP.

24 hour signal Sample data

Every run stays in the record.

An ok hour keeps the numbers. A failed hour keeps the gap.

Noon 12:00

#12

Ok

Down

110.0 Mbps

Up

12.0 Mbps

Ping

9.0 ms

Jitter 2.0 ms

Loss 0.0%

This city / Local server

Home ISP

ST-0012

Evening 18:00

#18

Failed

Down

-

Up

-

Ping

-

Cannot open socket

ST-0018

How it runs

Click a command to copy it. Then open the dashboard on this computer or the LAN IP.

    Show your provider the record.

    One slow test is easy to dismiss. A week of independent samples, on-peak and off-peak, is harder to ignore.

    1. Baseline the day

      Sample across one day, including hours when everyone is online and hours when they are not. A collector does this while you sleep.

    2. Keep testing after you call

      Providers often need a week of independent results, not a single screenshot. Stay on the schedule until the ticket closes.

    3. Export CSV

      Download the house record as a spreadsheet you can attach, chart, or print. Each run also has its own line pass.

    4. Mark the outage

      Failed samples stay in the tape. Open one to see when the line went down and when it came back.

    Close the dashboard. This computer keeps testing.

    macOS and Windows. Official Ookla Speedtest CLI. Not a test inside the browser.

    Peak and off-peak
    Collectors fire on an interval or at clock times, so busy evenings and quiet mornings both land in the record.
    CSV for your ISP
    Export every sample as a spreadsheet. Share it, chart it, or keep it with the ticket.
    Failed runs stay
    When a test cannot finish, the tape keeps the gap. Open the run to see when the line went down and when it came back.
    This computer only
    Samples never leave this house. Phones on the same Wi-Fi can still watch the tape.