Complete Guide to Starlink Speed Tests
Complete Guide to Starlink Speed Tests: a normal Residential result in 2026 is often 100-250 Mbps download, 10-40 Mbps upload, and 25-60ms ping. Check your numbers at noon and again at 9pm, because congestion, Wi-Fi limits, and obstructions can change the result by 2x or more.
What 100 Mbps actually means, how to run a test that gives you real answers, and why your results swing by 3× between noon and 9pm.
A speed test result is a single number pretending to be a verdict. You run it, see 183 Mbps, and either smile or start a support ticket. But that one number hides four different things happening at once, and the real question is whether your Starlink is performing normally for your plan, in your location, at this hour. An 80 Mbps reading in a remote Alaskan cabin at 9pm is spectacular. The same 80 Mbps in downtown Austin at noon on Residential is a red flag.
This guide walks through what your test actually measures, what to expect by region and plan, how to run a test that isn't lying to you, and the thresholds where support becomes worth your time. If you want to skip the theory and get a baseline right now, our free in-browser speed test measures download, upload, ping and jitter against servers on three continents and logs your history so next week's test actually means something.
What a speed test actually measures
Every legitimate speed test reports four numbers. Most people only look at the first one. Here's what each one really tells you:
Download speed (Mbps) measures how fast a big chunk of data can come toyou. This is the headline number, and it's what matters for streaming Netflix, loading web pages, downloading game updates, and almost every consumer use. A single 4K Netflix stream needs about 25 Mbps. A family with three devices streaming at once needs roughly 75 Mbps. Anything beyond 200 Mbps is essentially indistinguishable for typical home use — the bottleneck is your device, not your pipe.
Upload speed (Mbps)measures the reverse direction — you sending data out. This matters for video calls (Zoom uploads your webcam), cloud backups, uploading photos, and live streaming. Starlink's upload is structurally slower than its download because the spectrum allocation is asymmetric. 10 Mbps upload is enough for HD video calls; 25 Mbps is comfortable for simultaneous calls and backups; below 5 Mbps is where calls start freezing.
Ping / latency (ms)is the round-trip time for a tiny packet to reach a server and come back. This is not about bandwidth — it's about responsiveness. Low ping matters for video calls, gaming, and anything interactive. Starlink's floor is around 20ms thanks to its 550km orbit; a typical Residential ping sits between 25 and 60ms. Traditional geostationary satellite (HughesNet, Viasat) has 600ms+ ping, which is why video calls over those services are miserable.
Jitter (ms) is the variation between consecutive ping samples. A steady 40ms is fine. A wild swing between 20ms and 180ms — even if the average is 40ms — will destroy a voice call. Jitter is the best early-warning signal that a cell is congested or a dish is losing satellite handoffs. Healthy Starlink jitter is under 10ms.
Typical Starlink speeds by region and plan
These are the ranges you should see in well-served cells during normal conditions, pulled from community benchmark datasets and our own logged results across the last 12 months. Note these are Ethernet-wired numbers; WiFi will generally run 20-40% lower.
| Region | Plan | Download | Upload | Ping |
|---|---|---|---|---|
| US (rural) | Residential | 150–250 Mbps | 15–40 Mbps | 25–45 ms |
| US (suburban) | Residential | 100–200 Mbps | 10–30 Mbps | 30–55 ms |
| US | Priority | 250–400+ Mbps | 30–45 Mbps | 20–30 ms |
| Canada / Northern EU | Residential | 120–220 Mbps | 10–35 Mbps | 30–60 ms |
| Australia / NZ | Residential | 100–200 Mbps | 10–30 Mbps | 35–65 ms |
| Latin America | Residential | 80–180 Mbps | 8–25 Mbps | 40–70 ms |
| Africa / MENA | Residential | 60–150 Mbps | 5–20 Mbps | 45–80 ms |
| Roam (global, tourist areas) | Roam Regional | 60–150 Mbps | 5–20 Mbps | 40–90 ms |
If your numbers land inside these bands, Starlink is working normally for your location. If they don't, the next sections tell you where to look. To see exactly where your results fall against your specific region and plan, plug them into our ISP comparison tool which benchmarks against 20+ alternatives.
Why your speed varies hour to hour
Starlink is a fundamentally different beast from fiber or cable. With fiber, you get a dedicated pipe and your speed is essentially constant. With Starlink, you share a radio cell with hundreds or thousands of other subscribers, and the satellite overhead changes every few minutes. Four things drive most of the variation you'll see on any given day:
Satellite handoff and pass geometry. Starlink satellites are in low Earth orbit — they move. Every 2–4 minutes your dish hands off to a new satellite. During the handoff, you may see a 1–3 second latency spike or a brief bandwidth dip. If one handoff glitches, your next speed test will show it. Run the test three times in a row and take the best number.
Obstructions.Even partial sky blockage — a branch that grew over summer, a new building, a flagpole — can drop your dish's effective uptime from 99.9% to 95% and hammer your test results. The Starlink app shows an obstruction map, and our obstruction planner lets you simulate different mount heights and positions before you drill holes. Fixing obstructions is the single highest-leverage improvement for a slow dish.
Time of day and cell congestion. Every Starlink cell has a finite capacity. Between 7pm and 11pm local time, demand peaks — kids home from school, parents streaming, gamers online. A cell that delivers 220 Mbps at noon routinely drops to 60–90 Mbps at 9pm. This isn't a fault; it's the design. If you run a speed test only at 8pm and panic about the number, you're sampling the worst-case window. Always test at least once at noon to know your ceiling.
Weather. Heavy rain, snow accumulation on the dish, and extreme heat all affect performance. Rain fade is usually 10–20% drop; a snow-covered dish with failed self-heating can drop to zero. Extreme heat (dish surface above 140°F / 60°C) triggers thermal throttling that can cut speeds by half until things cool down.
How to run a proper test
If you're going to complain to Starlink support, or make a keep-or-cancel decision, you need numbers you trust. Here's the methodology that removes most of the noise:
1. Wired, not WiFi.Plug directly into the Starlink router via the Ethernet adapter, or use a third-party router in bridge mode. WiFi introduces so much variability (interference, client NIC, wall penetration) that it masks what's actually arriving at your dish. Test wired first to know the ceiling, then test WiFi to measure how much your home network is costing you.
2. Quiet the network. Pause cloud backups, stop streams, close browser tabs, and make sure no one is downloading game updates. A single background 4K stream will eat 25 Mbps of your test bandwidth and make the result look 25 Mbps lower than reality.
3. Reboot the router and dish.If it's been a week since the last reboot, power-cycle both and wait 5 minutes for reacquisition. This clears accumulated routing-table cruft and forces a fresh satellite handoff.
4. Run three tests, take the median. Back-to-back tests catch transient handoff dips. Three tests in a five-minute window gives you a median that filters out one-off glitches.
5. Test at three times of day.Morning (8-10am), mid-afternoon (1-3pm), and evening peak (8-10pm). The spread between these three tests tells you more about your connection than any single number. A healthy Residential connection might show 220 / 180 / 90 Mbps — the evening dip is normal. A sick connection shows 90 / 80 / 40 Mbps — it's bad even off-peak.
6. Log your results. A single test tells you nothing; a month of weekly baselines tells you everything. Our speed test stores your history locally in the browser so you can watch trends over time instead of reacting to noise.
Starlink speeds vs the alternatives
A 150 Mbps Starlink connection looks slow next to gigabit fiber and looks like magic next to HughesNet. Context matters. Here's how Starlink Residential stacks up against the realistic alternatives most rural and semi-rural users are actually comparing:
| Service | Typical down | Typical up | Ping |
|---|---|---|---|
| Starlink Residential | 150–250 Mbps | 15–40 Mbps | 25–60 ms |
| Fiber (FTTH) | 500–1,000 Mbps | 500–1,000 Mbps | 5–15 ms |
| Cable (DOCSIS 3.1) | 200–500 Mbps | 10–50 Mbps | 15–35 ms |
| 5G Home Internet | 100–300 Mbps | 10–30 Mbps | 20–50 ms |
| Fixed wireless (WISP) | 25–100 Mbps | 5–20 Mbps | 20–60 ms |
| HughesNet / Viasat (GEO) | 15–50 Mbps | 3–5 Mbps | 600–800 ms |
| DSL | 10–50 Mbps | 1–10 Mbps | 30–80 ms |
The story the table tells: Starlink beats every other rural option on both speed and latency, loses to fiber on raw speed but matches it on real-world usability, and crushes legacy satellite by an order of magnitude on ping. Walk through your specific scenario in the ISP comparison tool to see which alternative — if any — would serve you better at your address.
When to actually worry (and what to do about it)
Most slow speed tests aren't a Starlink problem — they're a WiFi problem, a time-of-day problem, or an expectation problem. But some results genuinely warrant action. Use these thresholds:
Under 50 Mbps download on Residential, wired, at noon, with clear sky: this is a real issue. Either you have an unreported obstruction, your dish firmware needs a reset, or your cell is oversubscribed beyond what Starlink should allow. File a support ticket with your timestamped speed-test screenshots.
Ping above 100ms sustained with high jitter: your dish is likely struggling with satellite handoffs. Check the obstruction map in the Starlink app and run our obstruction simulator to check whether a different mount location would fix it. Most of these cases are solved by raising the dish 4–8 feet or moving away from a tree line.
Frequent dropouts (connection lost for 10+ seconds, multiple times per hour):check the Starlink app's outage log. If it attributes the drops to obstructions, fix the view. If it attributes them to “no satellites,” you're in an edge-of-coverage zone and may need to wait for more satellites to deploy — or accept the reality. If outages are unattributed, try a dish reboot and a router-bypass test.
Upload consistently under 5 Mbps: this one is almost always a cell-congestion issue on Residential, since the uplink is the first thing throttled under load. Test upload at 3am; if it jumps to 15+ Mbps, congestion is confirmed. Priority plan is the only real fix.
Before contacting support, also check our total cost calculator to make sure the plan you're on matches what you actually need — some of what people call “slow Starlink” is really “wrong plan for my usage.”
FAQ
How fast should Starlink actually be in 2026?
On the Residential plan in a decently served cell, expect 100–250 Mbps download, 10–40 Mbps upload, and 25–60ms ping as your normal range. Priority customers routinely see 250–400+ Mbps down, 30–45 Mbps up, and 20–30ms ping. Roam users in crowded tourist corridors fall lower — often 60–150 Mbps. If you're consistently under 50 Mbps download on Residential during off-peak hours with a clear sky view, something is wrong: either obstructions, a congested cell, or a router/cable issue worth investigating.
Why is my Starlink speed slower at night?
Because Starlink cells are oversubscribed, just like every ISP. Between 7pm and 11pm local time, everyone in your coverage cell — which can span 50+ miles — comes home and streams. Residential traffic is also deprioritized relative to Priority and Maritime tiers once you exceed your monthly priority data. A cell that delivers 220 Mbps at noon can easily drop to 60–90 Mbps at 9pm. This is normal and expected; it's not a fault. If you need consistent evening speeds, upgrade to a Priority plan or shift bandwidth-heavy work to daytime.
Should I test over WiFi or Ethernet?
Always test wired (Ethernet) first to know what Starlink itself is delivering. The stock Gen 3 router's WiFi tops out around 400–600 Mbps in practice, and real-world conditions (wall penetration, 2.4GHz interference, older client devices) easily cut that in half. If your wired speed is 220 Mbps but WiFi shows 90 Mbps, the issue is your WiFi environment, not Starlink. Use the Starlink Ethernet adapter ($25) or disable the built-in router and use your own. Run both tests to diagnose where a bottleneck lives.
What's a good Starlink ping?
Anything under 50ms is good for Starlink. The physics-imposed floor is about 20ms because signals travel up to a 550km satellite and back — roughly 4ms each way — plus queueing and backbone routing. Priority customers often see 20–30ms; Residential users typically see 25–60ms; congested cells can push ping to 80–120ms with visible jitter. For gaming or real-time voice, under 40ms is comfortable. Over 100ms sustained with high jitter (variation between pings) means a congested cell or a dish that's losing satellite handoffs.
Why is my upload so much slower than download?
Because Starlink's radio spectrum allocation is asymmetric — the downlink gets a much larger slice than the uplink. Consumer users download far more than they upload, so this matches typical demand. Residential upload is capped in practice around 10–40 Mbps and rarely goes higher regardless of how fast your download runs. Priority plans raise this to 30–45 Mbps. If your work involves heavy uploads (video production, large backups, live streaming), this asymmetry matters more than the headline download number, and Priority or a Business plan becomes the right choice.
How often should I run a Starlink speed test?
Once a week for a baseline if everything feels fine. Run additional tests any time you notice a change — buffering, laggy calls, or a new obstruction (tree growth, construction). Test at three times of day: morning, mid-afternoon, and evening peak. Log the numbers somewhere simple. A month of weekly baselines makes it obvious when something real changes, versus normal cell congestion drift. If you're troubleshooting, test every 15 minutes for an hour to separate a one-off satellite handoff glitch from a persistent degradation.