Network / 01
Six signals, one bounded run.
A run is a short, fixed piece of work. It measures the path your connection takes, finishes in seconds, and costs a negligible amount of data.
What is measured
The six signals.
Each one answers a question a single speed test cannot.
-
ms
Latency
Round-trip time to a regional reference endpoint, measured as a distribution rather than a single ping.
-
%
Packet loss
Share of probe packets that never arrived, counted over a fixed number of probes so the denominator is known.
-
ms
Jitter
Variation between consecutive round trips. The number that decides whether a call or a game holds together.
-
Mbps
Throughput
Sustained rate over a short bounded transfer, capped so a run never costs a meaningful amount of data.
-
ms
DNS
Time to resolve a cold name through whichever resolver the connection is actually using.
-
%
Stability
Share of the measurement window the connection stayed usable, which a single speed test cannot see.
How a run works
Bounded, scheduled, and visible to you first.
-
01
Schedule
The device picks a run from its schedule. You set how often, and you can pause it at any time.
-
02
Probe
Each signal is measured against a regional reference endpoint, in a fixed order, with a hard time budget.
-
03
Show
The result appears on your own dashboard before it goes anywhere else.
-
04
Sign
The device signs the result with its own key, so the reading can be traced back to the device that took it.
-
05
Submit
The signed reading is submitted for verification. What happens next is on the verification page.
Cost
What a run actually uses.
Per run, target figures
- Duration
- Under 10 seconds
- Data used
- Single-digit megabytes, capped
- Default frequency
- Once per hour, adjustable
- Runs while idle
- Yes, and skipped while the line is busy
- Battery
- Deferred on battery unless you allow it
Sample dataThese are the design targets the client is being built to, not measurements of a shipped client. Nothing is running yet.
Privacy
What is never collected.
A run measures the path, not the payload.
-
No browsing history
The client never reads which sites you visit, and never sees a URL you requested.
-
No content
Nothing you send or receive is inspected. Probes carry their own synthetic payload.
-
No precise location
Readings are aggregated to a regional cell. A reading is never published at a street address.
Measure your own internet
The network is not live yet. This is where it starts.