A sudden Starlink speed drop almost always has one specific cause — and that cause determines the fix entirely. Rebooting when the problem is congestion accomplishes nothing. Checking obstructions when the problem is a background device uploading cloud backups wastes 20 minutes. This guide gives you the 60-second diagnostic first, then the fix that matches what you find.
Most people immediately reboot the router or call support when speeds drop. Both are premature — the reboot fixes maybe 10% of speed drops, and support will ask you to run the same diagnostics in this guide before escalating. Start with these answers.
Not usually. The most common cause of a sudden speed drop is network congestion during peak evening hours — 5 PM to 11 PM — when many subscribers in your Starlink coverage cell are online simultaneously. If your speed is slow right now and it’s evening, run a quick test at 2 AM or early morning. If speed is normal at off-peak hours, nothing is broken — your cell is simply busy. Other common sudden-drop causes include a new tree obstruction that grew into the dish’s sight line, a firmware update that triggered a reboot, or a background device (security cameras, cloud backup, gaming console) consuming your entire upload pipe. Actual hardware failure causing speed drops is relatively rare.
Run two tests back to back. First, run a speed test directly in the Starlink app — it tests the satellite link. Then run the same test on a device connected to the router by Ethernet cable. If both show similar low speeds, the problem is in the satellite connection. If the Ethernet test is fast but your Wi-Fi device shows slow speeds, the entire problem is in your home’s wireless network — not in Starlink at all. This distinction is critical because no amount of dish adjustment, rebooting, or calling Starlink support will fix a Wi-Fi bottleneck. The Gen 3 router’s Wi-Fi tops out around 400–600 Mbps in ideal conditions; real-world conditions like walls and interference cut that significantly.
This is the textbook pattern for cell congestion. Starlink organizes subscribers into geographic coverage cells. When evening hits and many users stream video simultaneously, the satellite serving your cell has more requests than it can prioritize equally. Under Starlink’s Fair Use Policy, Standard plan users get deprioritized during congested periods in busy cells. This is not a malfunction — it’s how the system works by design. Evening speeds of 15–50 Mbps while morning speeds reach 100–180+ Mbps are normal in moderately congested cells. The fix options are: upgrade to a Priority plan ($250/month, unlimited priority data), schedule bandwidth-heavy tasks for off-peak hours, or simply accept this is the service’s natural variation in your area.
Yes — and this is one of the most common causes of gradual-but-sudden-feeling speed drops. Trees that were bare in winter put out new foliage in spring and summer, growing directly into the dish’s sight line. Even 1–2% sky obstruction causes repeated brief dropouts that your device averages as reduced overall speed rather than showing as a visible outage. Check the Starlink app’s obstruction tool seasonally — open the app, go to Starlink → Obstruction, and look for red or yellow zones in the sky view. A zone that wasn’t there last fall but appears now is almost certainly foliage. The app needs 12–24 hours of accumulated satellite pass data to build an accurate picture, so let it run overnight if you haven’t checked in a while.
Yes, in two ways. First, the firmware update process itself causes a brief reboot that can feel like a sudden disconnection. Second, occasionally a new firmware release introduces a regression that affects speeds in specific regions or hardware generations — this is uncommon but documented. The symptom of a firmware-related slowdown is a speed change that doesn’t line up with weather, time of day, obstruction, or background device activity, and often started almost overnight. The fix: power-cycle the router once (unplug 30 seconds, replug), let the system idle overnight, and retest. If speeds recover after a day or two, the firmware likely self-corrected with a follow-up patch from Starlink’s automatic update system.
Absolutely — and it happens more often than people expect. Security camera systems uploading event clips, Ring doorbells streaming video to the cloud, gaming consoles downloading large updates in the background, smart home hubs pushing telemetry, iCloud or Dropbox syncing photos, and cloud backup services running on a schedule all silently consume bandwidth. A saturated upload connection is particularly harmful because it raises latency and jitter for every device on the network simultaneously, making everything feel slow even if download is fine. To check: run a speed test immediately after disconnecting every device from your network except the one you’re testing on. If speed jumps back to normal, a connected device was the culprit.
No — weather-related speed drops are always temporary. Heavy rain absorbs and scatters Starlink’s Ka-band signal (a phenomenon called rain fade), causing speed drops of 30–50% during the storm, with occasional brief dropouts during the most intense rainfall. Light to moderate rain typically causes no noticeable effect. Speeds fully restore within minutes of the storm easing — this is not a configuration problem and no settings change will help during an active storm. Snow on the dish is different: the dish has a built-in heater that handles light snow accumulation automatically. In heavy snowfall where accumulation exceeds the heater’s melting rate, speeds will drop until the snow is cleared. Never use metal tools to clear the dish; a soft brush works safely.
Possibly, but only during peak hours. Starlink’s Standard Residential plan includes 1 TB of priority-access data per billing cycle. After crossing that threshold, your traffic becomes deprioritized — it moves to the back of the queue behind subscribers who still have priority data remaining. In an uncongested or rural Starlink cell, you may never notice this at all. In a moderately busy cell, evening speeds after crossing the 1 TB mark can drop from 80–120 Mbps to 15–50 Mbps during peak hours. Morning and midday speeds remain unaffected regardless of priority data status. Check your usage in the Starlink app under Account → Data Usage. If you’re past 1 TB with most of the billing cycle remaining, that’s likely the evening slowdown’s cause.
Three quick checks tell you more than 30 minutes of rebooting and cable-checking. Run them in order — each one narrows the field of possible causes.
Open the Starlink app and tap Statistics or the performance screen. Note three things: (1) obstruction percentage — any number above 0% is meaningful; (2) your current download speed reading; and (3) the time of day. These three numbers together point to the most likely cause. If obstruction is above 0%, start there. If obstruction is 0% and it’s 6–11 PM, congestion is the first suspect. If it’s mid-morning with zero obstruction and speeds are still low, look at background devices and Wi-Fi next. The outage log in Statistics is also valuable — it records every drop event with duration and type, which tells you whether outages are happening continuously or only at specific times.
Plug a laptop or desktop directly into the Starlink router using an Ethernet cable. The Gen 3 router has two built-in Ethernet ports on the back panel. Run a speed test from that wired device with no other devices active on the network. Compare this to your normal experience on Wi-Fi. Three possible outcomes tell you exactly where the problem lives: wired is fast → your Wi-Fi or a specific device is the bottleneck, not Starlink; wired is also slow → the satellite link itself has the problem; wired is fast but one specific device is slow → that device has a local issue, an outdated driver, or is connected on 2.4 GHz. Knowing which layer the problem is in prevents spending money on the wrong fix entirely.
Run the same wired speed test at three different times: once in the morning (8–11 AM), once mid-afternoon, and once in the evening (7–10 PM). Record the results. A speed that’s high in the morning but collapses in the evening is classic cell congestion — nothing is broken and no fix will change it except upgrading your service tier or shifting heavy usage to off-peak hours. A speed that’s consistently low at all hours points to a persistent issue — obstruction, hardware, or a device permanently saturating the connection. One data point is not a diagnosis. A pattern across times of day is.
Every significant cause of a sudden Starlink speed drop, with the pattern that identifies it, the correct fix, and how long the fix takes. Match your symptom on the left to the row that fits.
| # | Cause | Telltale Pattern | Fix | Time to Fix |
|---|---|---|---|---|
| 1 | Peak-hour congestion | Fast 8 AM; slow 7 PM; 0% obstruction | Shift heavy tasks to off-peak hours or upgrade to Priority plan | Instant (scheduling) or plan change |
| 2 | New tree/foliage obstruction | Brief dropouts; app shows obstruction; worse since spring | Trim branches or relocate dish to clearer sight line | Minutes to hours (trimming) |
| 3 | Background device saturating upload | All devices slow; restores when specific device is off | Identify and reschedule or limit the offending device | Under 15 minutes to identify |
| 4 | Wi-Fi bottleneck (not Starlink) | Wired speed fine; Wi-Fi slow; problem on far devices | Reposition router; add mesh node; use Ethernet for key devices | 5 minutes (reposition) to 1 hour (mesh) |
| 5 | Heavy rain / rain fade | Slow only during storm; fully restores when rain stops | Wait it out — no fix needed, always self-resolves | Minutes after storm passes |
| 6 | Snow or ice on dish | Slow or disconnected in winter; restores after heating/clearing | Allow dish heater to work; soft-brush heavy accumulation | 30–60 minutes (heater); immediate (brushing) |
| 7 | Priority data exhausted (1 TB) | Slow evenings only; mid-billing cycle; data-heavy household | Check usage in app; shift heavy usage to 11 PM–7 AM off-peak | Immediate (scheduling) |
| 8 | Firmware regression / update | Started overnight; no weather/obstruction/congestion pattern | Power-cycle once; wait 24–48 hrs for follow-up patch | 24–48 hours (auto-patch) |
| 9 | Dish cable damaged | Slow at all hours; app shows frequent dropouts; recent wind/animals | Inspect cable ends; order replacement from Starlink shop | Same day (inspection) to days (shipping) |
| 10 | Router hardware failure | Wired also slow; reboot doesn’t help; red LED persists | Contact Starlink support; free warranty replacement within 1 year | Days (support ticket + shipping) |
If your speeds are fine during the day but reliably slow between 5 PM and 11 PM, this is almost certainly the cause. It’s not a malfunction — it’s how satellite network capacity works, and understanding it properly saves you from buying hardware or calling support for a problem that has a different solution.
Starlink organizes subscribers into geographic coverage cells, each served by satellites passing overhead. Each satellite has finite capacity to serve everyone in the cell simultaneously. When evening hits and hundreds of households in your cell start streaming, gaming, and video-calling at the same time, that capacity gets shared. Under Starlink’s Fair Use Policy, Standard Residential plan users receive priority bandwidth — but during highly congested periods, even priority users compete for available capacity. The result: morning speeds of 120+ Mbps that drop to 20–60 Mbps in the evening in busy cells. This is documented, expected behavior — not a service failure.
- Schedule heavy usage for 11 PM–7 AM. Starlink’s off-peak window (11 PM to 7 AM) typically has far lower cell loads. Large downloads, cloud backups, game updates, and software patches all run perfectly well overnight. Setting automatic schedules in your router or on individual devices routes this traffic away from the peak window entirely.
- Upgrade to Starlink Priority. At $250/month, the Priority plan provides unlimited priority-access data. During congested periods, Priority traffic is served before Standard traffic. Many users in moderately congested cells see roughly double the peak-hour throughput after upgrading. This is a service-tier solution, not a hardware fix — it will not help if the problem is obstruction or Wi-Fi.
- Accept it as the service’s natural behavior. In uncongested or rural cells, Standard plan users often never notice congestion at all. In denser suburban and semi-rural cells, evening variation is the tradeoff for the plan price. Running the morning/evening comparison test confirms which situation you’re in.
Rebooting the router does nothing for cell congestion — the router comes back online to the same congested satellite. Checking obstructions is useful but won’t explain why speeds are fine at noon. Calling Starlink support will not get congestion removed from your cell — it’s a network-wide capacity issue, not a per-account problem. If a support agent tells you to reboot and retest at 2 AM, this is why — they’re asking you to confirm the time-based pattern, not suggesting rebooting fixes it.
A dish that had clear sky last fall may have a completely different sight line this summer. Trees grow, neighbors add structures, and antennas shift over time. Even a small amount of obstruction causes repeated brief signal interruptions that average out as significantly reduced speed — without ever showing as a complete outage.
Open the Starlink app, tap the dish icon or the menu, and select Obstruction. The app shows a sky map with your dish’s current view — red zones are hard blockages (buildings, your own roofline, chimneys), orange zones are soft blockages (tree branches, foliage). Any color in this view is significant. Starlink’s own threshold for optimal performance is 0% obstruction — even 1–2% of blocked sky causes brief handoff interruptions when satellites pass through that zone, which your speed test records as reduced average throughput. Let the map accumulate data for 12–24 hours before drawing conclusions — it builds accuracy with more satellite passes over time.
For orange foliage zones, trimming the specific branches visible in the obstruction map often resolves the problem immediately. For red zones caused by your own home’s roofline or chimney, the dish needs to be raised or moved — a higher mount or different mounting location gives the dish a wider clear view of the sky. Trees that were dormant in winter and fully leafed out in summer are the most common seasonal cause of a speed drop that users attribute to Starlink problems. Check the obstruction map every spring after trees leaf out fully — new foliage that didn’t exist during installation is the most predictable cause of a previously-fast system slowing down with no other obvious explanation.
Weather gets blamed for Starlink slowdowns more than it deserves — and sometimes it gets ignored when it’s the real cause. Knowing which weather actually affects performance stops you from troubleshooting the wrong thing during a storm.
Starlink uses Ka-band and Ku-band radio frequencies that water absorbs and scatters — a phenomenon called rain fade. The effect is proportional to rainfall intensity: light rain causes essentially no impact, moderate rain causes minor reduction on some satellite passes, and heavy rain (above about 0.5 inches per hour) can cause noticeable speed drops and occasional brief dropouts lasting 10–30 seconds during peak intensity. Rain fade is always temporary — speeds fully restore within minutes of the storm easing. There is no fix during active heavy rain, and no configuration change helps. If your speed drops during every severe thunderstorm and returns fully afterward, this is rain fade behaving exactly as expected.
The Starlink dish has a built-in heater designed to melt light snow accumulation automatically. For normal winter snowfall, you generally don’t need to do anything — the heater keeps the dish surface clear. In heavy, sustained snowfall or freezing rain, accumulation can exceed the heater’s melting rate and temporarily block the dish’s sky view. The symptom is a sudden complete or near-complete loss of connection during a winter storm that returns to normal when the dish clears. If speed drops during heavy snowfall, wait for the heater to work first. If it persists, use a soft brush — never metal — to gently clear visible accumulation. Never use hot water (thermal shock risk) or anything that would scratch the dish surface.
Dense cloud cover alone has minimal impact on Starlink performance — independent tests in the Pacific Northwest found less than 3% signal degradation during sustained heavy overcast with no precipitation. If your connection is slow on a cloudy day with no rain, clouds are almost certainly not the cause. Strong wind is only a problem if it physically moves the dish out of its alignment — a well-mounted dish on a solid surface should not shift in typical wind. If you suspect wind caused an alignment shift, look at the dish from the ground and compare its angle to how it was positioned originally. A shift of more than a few degrees warrants checking the mount hardware and tightening any loose fasteners.
One of the most common misdiagnoses is blaming Starlink for a speed problem that lives entirely inside the home network. A fast satellite connection delivering 150 Mbps to the router can be completely masked by a weak Wi-Fi signal, a background device consuming bandwidth, or a router placement issue. The wired speed test from the diagnostic section tells you which world you’re in.
Ring and Nest cameras upload video clips to the cloud continuously after motion events — a busy household with multiple outdoor cameras can generate significant sustained upload traffic. Game consoles (PlayStation, Xbox) download multi-gigabyte updates in the background on a schedule. iCloud, Google Photos, Dropbox, and similar services sync photos and files automatically. Cloud backup applications run on their own schedules. A saturated upload path is the most damaging scenario because it raises latency for every device on the network simultaneously — even streaming on a device that isn’t uploading anything will buffer because the upload congestion raises overall network latency. To identify: disconnect one device at a time while watching the speed test in real time. When the slow device is identified, schedule its activity for the 11 PM–7 AM off-peak window.
When a laptop in the back bedroom has slow internet and the primary TV in the living room works fine, the problem is almost never Starlink — it’s Wi-Fi signal strength between the router and the distant device. The Gen 3 Starlink router is rated for 3,200 square feet under ideal conditions; real-world coverage in a home with plaster walls or multiple floors can be much less. 2.4 GHz interference from neighboring Wi-Fi networks in an apartment building also degrades performance significantly for all devices. The test: bring the slow device next to the router and retest. If speed is fine next to the router and poor in the problem room, the issue is in-home Wi-Fi range — a mesh node, router repositioning, or Ethernet cable to that room will fix it, not any Starlink setting.
Run the morning/evening comparison test first. If morning is fast and evenings are slow, this is congestion — more subscribers have joined or become active in your Starlink cell recently. Nothing in your home changed; the network got busier. The practical response: schedule your largest downloads and cloud backups for the 11 PM to 7 AM off-peak window. If the congestion pattern is severe enough to be genuinely disruptive, check your data usage in the Starlink app — if you’re past 1 TB for the month, your traffic is also being deprioritized during evening hours, compounding the cell congestion. Rebooting the router, adjusting dish angle, or calling support will not resolve cell-level congestion.
This is the foliage pattern. Open the Starlink app’s obstruction checker (Starlink → Obstruction) and look for new orange zones that correspond to tree canopy. A branch that was bare in February and fully leafed in June may now be sitting in the path the dish uses to communicate with satellites at certain times of day. The fix is trimming the specific branches visible in the obstruction map, or raising the dish above the foliage line. Even one or two percent of sky blocked causes enough signal interruption during satellite handoffs to measurably drop average speed. Check the obstruction map on a warm afternoon when foliage is at its densest rather than early morning.
When a speed drop starts suddenly with no corresponding weather event, no new obstruction, and at a time of day that previously worked fine, firmware is a reasonable suspect. Starlink pushes updates automatically, typically during overnight reboot windows. Occasionally an update introduces a performance regression in specific regions or hardware generations. The response: power-cycle the router once (unplug 30 seconds, replug), let it sit idle overnight, and retest in the morning. If speeds recover over the following 24–48 hours, Starlink’s follow-up patch likely resolved whatever the update introduced. If speed remains consistently low at all hours after 48 hours, open the Starlink app, check Statistics for outage patterns, and contact support with those results.
This is where background devices are almost always the culprit. “We didn’t change anything” usually means a device updated its software and started running more aggressively, a new security camera was installed, a game console started a large update, or an app’s backup schedule intensified. Check your router’s connected device list — many routers show real-time bandwidth usage per device. Look specifically for any device using significant upload bandwidth, not just download. Security cameras, smart NVR recorders, and cloud backup services are the most common offenders. Disconnect the highest-bandwidth device and retest immediately. If speed recovers, you’ve found the issue.
During a storm: this is rain fade or snow accumulation — wait for it to pass, speeds restore on their own. After a storm that has passed: check the dish physically. Strong wind can shift a dish that wasn’t fully secured on its mount, slightly changing its alignment. Look at the dish from the ground and note whether it appears to have moved from its original position. Check that all mount fasteners are tight. Also inspect the cable for any visible damage from wind or debris. If the dish appears undisturbed and the cable looks intact, check the Starlink app for obstruction or outage alerts — ground station issues occasionally linger after major storm events and resolve without any action on your part.
Contact Starlink support through the app (Support → Contact Us) when all of the following are true: the wired speed test is consistently slow at all hours including 2–6 AM; the obstruction map shows 0% blockage; no background devices are active during the test; no weather event is in progress; and the problem persists after a full power-cycle. When you file the ticket, include the time-of-day results from three separate tests, your current obstruction percentage, and your dish cable’s physical condition. This information prevents support from walking you through the same diagnostics you’ve already done and gets you directly to hardware evaluation. Within the first year of ownership, Starlink replaces defective hardware at no cost under the standard warranty.
Starlink network performance varies by geographic location, plan tier, time of day, weather conditions, and satellite constellation capacity. Speed figures cited reflect published data and independent speed tracking reports and represent typical ranges rather than guaranteed performance. Starlink’s fair use policy, plan pricing, and data thresholds are subject to change — verify current terms at starlink.com. This content is entirely original and provided for general informational purposes only.