teststarlink analysis
CSV SQLite
Tests per day
Median download per day (Mbps)
Download distribution (Mbps)
Latency distribution (ms, idle)
Percentiles — Starlink vs not
Where the tests were run

Position used by the model (GPS / ADS-B / manual); tests without a position fall back to the exit point. Blue = Starlink, orange = other.

Model RTT vs measured idle latency (Starlink)

Each dot is one test; the hairline is y = x. Points above the line: measured worse than the free-space + fibre model (queueing, PoP → server distance).

Page loads

Latest 200 loads
Starlink PoP codes seen in reverse DNS

Every Starlink test records the PoP code from the IP's reverse DNS (customer.<CLLI>.isp.starlink.com). Codes not in assets/data/pops.json are the ones to add (the app then falls back to the PoP nearest to the IP geolocation).

Aircraft ↔ in-flight provider registry

One row per (registration, provider) episode, learned from tests run on board tracked flights (airborne, fix < 15 min, device GPS within 50 km of the aircraft). A new row opens when the provider read from the IP differs from the previous one — that is a supplier change. Prior = what the airline contracted for that fleet type (assets/data/ifc_contracts.json, dated). Export: JSON · CSV.

Recent tests

Analysis

This page reads the measurement database — for owner accounts.

Loading…