Starlink Speed Test & Conditioned Performance Benchmark
Accurately measure your Starlink download speed, upload bandwidth, ping latency, and jitter. Compare your live dish results against the calculated average of users with the exact same hardware model, weather conditions, service tier, and sky obstruction profile.
You appear to be connected via a terrestrial ISP or VPN. For pristine telemetry accuracy, connect directly to your Starlink dish Wi-Fi, or enable bypass testing below.
Step 1: Set Testing Conditions & Hardware Profile
Required to calculate your precise peer benchmark under identical atmospheric and hardware conditions.
~50 - 220 Mbps nominal clear sky
Roam plans run at lower cell scheduling priority than fixed residential.
Rain clouds directly absorb 12-14 GHz microwave signals.
Obstructions interrupt 15-second satellite handoffs, lowering average throughput.
* Click "Using VPN or Bypass? Test Anyway" above if you are on an active VPN or bypass bridge.
My Recent Speed Tests (Local Browser Cache)
Your last 5 speed test runs stored securely in this browser for quick comparison.
Zero Private Data Retention: When you complete a speed test, our server only ingests anonymous physical RF indicators (throughput Mbps, RTT latency, selected hardware model, general metropolitan area, and weather classification). We never record or store your exact street address, subscriber account ID, complete IP addresses, or browsing activities.
Client-Side Storage: The 5 recent test records shown above reside strictly in your private web browser (localStorage). No cookies are used to track your speed tests across other websites, and you can instantly wipe this history at any time using the "Purge Local Cache" button above.
Average Starlink Speeds by Monitored City (43 Hubs)
Strictly aggregated from genuine user speed test submissions in our database. Cities with 0 submitted tests display -- awaiting community contributions.
| Rank / City | State / Region | Avg Download | Avg Upload | Avg Gateway Ping | Real Tests Logged | City Hub Telemetry |
|---|---|---|---|---|---|---|
| #1Amsterdam | North Holland, Netherlands | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #2Atlanta | Georgia, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #3Auckland | Auckland Region, New Zealand | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #4Austin | Texas, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #5Berlin | Berlin, Germany | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #6Boston | Massachusetts, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #7Brussels | Brussels-Capital Region, Belgium | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #8Cape Town | Western Cape, South Africa | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #9Chicago | Illinois, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #10Dallas | Texas, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #11Denver | Colorado, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #12Dublin | Leinster, Ireland | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #13Frankfurt | Hesse, Germany | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #14Houston | Texas, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #15Johannesburg | Gauteng, South Africa | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #16Las Vegas | Nevada, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #17London | Greater London, UK | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #18Los Angeles | California, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #19Madrid | Community of Madrid, Spain | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #20Manchester | Greater Manchester, UK | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #21Melbourne | Victoria, Australia | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #22Miami | Florida, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #23Montreal | Quebec, Canada | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #24New York | New York, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #25Osaka | Kansai, Japan | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #26Paris | Île-de-France, France | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #27Phoenix | Arizona, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #28Portland | Oregon, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #29Rio de Janeiro | Rio de Janeiro, Brazil | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #30Rome | Lazio, Italy | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #31San Diego | California, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #32San Francisco | California, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #33São Paulo | São Paulo, Brazil | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #34Seattle | Washington, USA | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #35Seoul | Seoul Capital Area, South Korea | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #36Singapore | Singapore | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #37Sydney | New South Wales, Australia | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #38Taipei | Taiwan | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #39Tokyo | Kanto, Japan | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #40Toronto | Ontario, Canada | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #41Vancouver | British Columbia, Canada | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #42Wellington | Wellington Region, New Zealand | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
| #43Yokohama | Kanagawa, Japan | -- | -- | -- | 0 (Awaiting real tests) | Live Status |
How to Accurately Diagnose Starlink Satellite Speed Drops
1. Wi-Fi Router Bottleneck vs. Satellite Downlink
Before assuming your satellite dish has poor signal, check your local Wi-Fi connection. Older 2.4 GHz Wi-Fi bands max out between 30 to 50 Mbps due to household channel interference. To verify true satellite capacity, test your speeds on the 5 GHz Wi-Fi band or via a hardwired Ethernet adapter connected directly into your Starlink router power supply.
2. Rain Fade & Storm Atmospheric Attenuation
Starlink user terminals communicate with orbiting satellites using Ku-band (12–14 GHz) and Ka-band (20–30 GHz) frequencies. Dense precipitation absorb microwave radio frequency beams. During severe thunder cells or heavy snowstorms, download throughput can drop by 20% to 40% until the weather system moves past your local sky azimuth.
3. Peak Cell Congestion Hours (7:00 PM – 11:00 PM)
Each Starlink orbital beam covers a geographic cell roughly 15 miles (24 km) wide. During evening peak hours, hundreds of subscribers in the same cell stream 4K video simultaneously. Standard Residential plans share dynamic transponder capacity, which can temporarily reduce throughput from 200+ Mbps down to 80–120 Mbps.
4. Tree Line Obstructions & Micro-Interruptions
Because Starlink satellites traverse the sky rapidly every 15 minutes, phased-array electronically steered beams must switch between spacecraft seamlessly. Even a single tree branch obscuring 2% of the northern horizon will cause TCP packet retransmissions, leading to sudden latency spikes of 150+ ms and momentary throughput stalls.
Experiencing complete disconnections or "Searching for Satellite"? Check our troubleshooting guides: