Fast during the day, sluggish after dinner — Starlink’s evening slowdowns affect users across the country, and most of the time there’s a real fix. This guide covers every reason your speeds drop when the sun goes down, ranked by how often they’re the actual culprit.
Most people assume slow Starlink at night is just a service problem they can’t do anything about. That’s not accurate. There are usually two or three specific causes stacking on top of each other — and most of them have a direct fix.
It’s genuinely common — but “common” doesn’t mean you’re stuck with it. Peak-hour congestion is the most frequently reported Starlink complaint, and it happens because every dish in your coverage cell shares the same pool of satellite bandwidth. When dozens or hundreds of households stream video between 6 PM and 11 PM, available bandwidth gets divided among all of them. That said, users on Priority plans in less-congested areas often see little or no slowdown, while Residential Lite users and those in dense suburban cells experience it most. The network is unevenly loaded — your neighbor two miles away may see no slowdown at all.
Congestion typically builds starting around 6 PM local time and peaks between 7 PM and 10 PM in most U.S. regions. Speeds usually begin recovering after 11 PM — and usage between 11 PM and 6 AM is genuinely off-peak, with many users seeing daytime-equivalent or better performance. If you need to do large downloads, software updates, or cloud backups, 11 PM to 5 AM is the practical sweet spot. The Starlink app can schedule downloads automatically during off-peak hours if you use a compatible device.
Yes — this is one of the most overlooked causes. Starlink’s Residential Lite plan carries fully deprioritized data all the time, not just at night. That means during any period of congestion, Residential Lite traffic sits at the back of the queue behind every other plan type. Standard Residential customers get priority access during normal usage — but once their monthly priority allotment runs out, their traffic drops to the same deprioritized tier. Priority plan holders maintain first-in-line status on the network regardless of congestion. If your plan’s data tier has changed at any point this billing cycle, nighttime slowdowns will be noticeably worse.
Yes, and this is one of the trickiest problems to diagnose. Obstructions interact with satellite position — your dish connects to satellites as they move across the sky, and a tree or chimney that’s irrelevant when a satellite passes to the east can completely block signal when the satellite arc moves through a section you’d otherwise use heavily in the evening. A partial obstruction can look fine all morning and become a real problem after 5 PM depending on which satellites your dish is actively using. The Starlink app’s obstruction scan, run from the dish location, shows exactly where your sky view is blocked.
Both — and they compound each other. Evening hours happen to coincide with afternoon storm patterns in many parts of the country, particularly in summer. Heavy rain absorbs and scatters signal on the Ku and Ka frequency bands Starlink uses, and unfavorable weather can temporarily cut throughput by up to 50% in some locations. When that weather-related signal degradation combines with peak-hour congestion, speeds can fall very sharply — not because either problem alone is catastrophic, but because both are hitting simultaneously. Light rain has minimal impact. A genuine downpour on top of peak-hour congestion is where users report the worst evenings.
Starlink’s low-earth orbit satellites move constantly — they’re not stationary. Your dish switches from one satellite to the next approximately every 15 seconds. During that handoff, packets can be lost or delayed for anywhere from a fraction of a second to a few seconds. Streaming and browsing usually survive it without noticeable disruption. Video calls freeze. Online gaming shows rubber-banding. At night, these handoffs hurt more because the base connection is already under stress from congestion — a packet loss event that’s invisible at 150 Mbps becomes a buffering wheel at 30 Mbps. The handoffs themselves don’t get more frequent at night; the congested baseline makes them more painful.
Absolutely. Evening is when every device in the house is awake simultaneously — smart TVs, streaming sticks, game consoles, phones, and laptops — all competing for the same Wi-Fi airspace. The Starlink dish can be delivering 80 Mbps to your router while your router is delivering 12 Mbps to your laptop because the 2.4 GHz band is saturated with competing devices. The test: run a speed test from a laptop plugged directly into the Starlink router via ethernet cable. If ethernet speeds are significantly higher than Wi-Fi speeds at the same time, your problem is local network congestion, not Starlink. Adding a mesh node, separating the 2.4 GHz and 5 GHz bands, or switching devices to ethernet where possible solves this entirely.
The trajectory is genuinely positive. SpaceX has been expanding the constellation continuously — the company surpassed 6,000 active satellites and has been launching more regularly. Real-world speed test data from early 2026 shows Starlink’s median U.S. download speed sitting between 65 and 100 Mbps, with roughly 80% of users pulling above 40 Mbps most of the time. Third-generation Starlink satellites, expected to begin launching in 2026 on Starship, are designed to provide over 1 Tbps of throughput per satellite — a dramatic capacity increase. Users who experienced severe evening congestion in 2022 and 2023 have generally reported better performance as the constellation has grown — though congested suburban cells in high-demand areas continue to see peak-hour variation.
These are the actual causes, ordered from most common to least. Most nighttime slowdowns involve two or three of these stacking. The fix for each one is specific and described directly.
Every Starlink dish in your coverage cell shares a finite pool of bandwidth from the satellites passing overhead. Between 6 PM and 11 PM local time, when streaming, gaming, and video calls peak across a neighborhood, that bandwidth gets divided among far more active users simultaneously. A cell that delivers 150 Mbps to your dish at 2 PM may deliver 35 Mbps at 9 PM because the same capacity is now split among ten times as many active sessions. This is the single most common reason Starlink slows at night, and it’s most pronounced in suburban areas and dense rural markets where Starlink has a large local subscriber base. Users in genuinely remote locations — a single farmhouse, miles from the nearest neighbor — often see no congestion effect at all because there’s no one else sharing their cell.
Starlink’s network has a priority queue. When the network is congested, higher-priority traffic moves first — and deprioritized traffic waits. The Residential Lite plan ($80/month) carries fully deprioritized data at all times, meaning any congestion at any hour pushes that traffic to the back of the line. Standard Residential customers ($120/month) receive priority access — but if their monthly priority data allotment has been exhausted, remaining usage that month drops to deprioritized status as well. Check your data usage in the Starlink app before assuming congestion is the only issue. If you’re mid-month on Residential with heavy early-month usage, you may already be in deprioritized territory. Priority plan holders maintain first-queue status and experience congestion effects least.
Starlink’s satellites orbit at roughly 550 kilometers and are constantly moving. Your dish follows them and switches from one satellite to the next on a fixed global schedule — approximately every 15 seconds, with handovers at the 12th, 27th, 42nd, and 57th second of every minute. Each handoff involves a brief period where packets may be dropped or delayed. During daytime at full speed, these interruptions are generally invisible. At night, when base speeds are already reduced by congestion, the same packet loss becomes a buffering event or a call drop. Handoffs happen equally often at all hours — the congested baseline is what makes them painful at night specifically.
An obstruction that appears irrelevant in the morning can become a real problem in the evening because the satellite arc your dish depends on at any given time changes throughout the day. A chimney or tree branch to the southwest of your dish might be completely out of the active satellite path at 10 AM but directly in the path of the satellites your dish needs from 6 PM to 9 PM. Even brief obstructions — a branch swaying in the wind — can cause packet loss that reads as slow speeds without any obvious indication of why. Open the Starlink app, go to the obstruction map, and run the check at the actual dish location — not from inside the house. Look for any marked obstruction in the southern or southwestern sky quadrant, which is where satellites are most frequently active for U.S. locations. Moving the dish even one or two meters can sometimes eliminate the problem entirely.
Starlink operates on Ku and Ka frequency bands, both of which are susceptible to rain fade — signal absorption by heavy precipitation. Light rain has minimal effect. A genuine downpour can temporarily reduce throughput by roughly 50% in some locations. Snow accumulating on the dish itself blocks the physical line of sight, though the dish has a built-in heater that handles light snowfall; heavy accumulation can still overwhelm it. Dense storm cloud and thunderstorms overhead raise packet loss and compound latency. Evening hours happen to coincide with afternoon storm patterns in many U.S. regions, particularly in summer — which is why weather-related slowdowns are often mistaken for pure congestion. If your slowdown correlates precisely with visible storm activity and clears once weather passes, weather is your cause, not the network.
Evening is when every connected device in the household is active at once — smart TVs, streaming devices, game consoles, tablets, phones, and laptops all competing for Wi-Fi airspace simultaneously. The 2.4 GHz Wi-Fi band has limited capacity and degrades sharply when saturated with devices; 5 GHz has more throughput but shorter range. The critical diagnostic: plug a laptop directly into your Starlink router with an ethernet cable and run a speed test at the same time your Wi-Fi feels slow. If ethernet shows strong speeds while Wi-Fi is poor, the problem is entirely within your home network — the Starlink connection itself is fine. Fixes include separating 2.4 GHz and 5 GHz networks in the Starlink app, adding a mesh node, or wiring high-bandwidth devices (TV, desktop, console) directly.
Hardware issues can mimic or worsen congestion-related slowdowns. Older rectangular Starlink dish models (Gen 1 and some Gen 2 units) had motor-based actuators that physically tilt the dish; a motor issue can prevent the dish from tracking the satellite arc correctly, which becomes more apparent when satellite angles change with different arc paths in the evening. Damaged cables — from animals chewing them, physical stress, or water intrusion at connectors — degrade signal quality in ways that worsen under any added network load. Thermal throttling occurs when the dish overheats in summer: the dish reduces output to protect itself, most commonly late afternoon into early evening before temperatures drop. The Starlink app shows dish status alerts — check for “motor error,” “mast not vertical,” or “thermal throttle” notifications. Contact Starlink support if hardware issues appear; some users have received replacement units after support confirmed a hardware diagnosis.
Use this table to match your specific symptoms to the most likely cause. If speeds drop only at night, start with congestion. If speeds are slow all day but worse at night, check your plan tier and obstructions first.
| Cause | When It Happens | Severity | You Can Fix It? | First Action |
|---|---|---|---|---|
| Peak-Hour Congestion | 6–11 PM nightly | High (varies by area) | Partially | Schedule downloads after 11 PM |
| Plan Deprioritization | All hours on Lite; anytime after cap on Standard | High | Yes | Check data usage in Starlink app |
| Satellite Handoffs | Every ~15 seconds, all day | Medium (compounds congestion) | Partially | Switch to wired ethernet where possible |
| Partial Obstruction | Specific sky quadrant / time-dependent | High if unaddressed | Yes | Run obstruction scan in Starlink app |
| Rain Fade / Weather | During storms or heavy precipitation | Medium (temporary) | No (wait it out) | Confirm it clears when weather passes |
| Local Wi-Fi Congestion | Evening when all devices are active | Medium–High | Yes | Ethernet speed test vs Wi-Fi comparison |
| Hardware Issue | Persistent / not tied to time of day | High if present | Via Starlink support | Check app for motor / thermal / cable alerts |
Run these in order. Each one takes under five minutes. The combination usually identifies the problem within the first two or three steps.
Before anything else, eliminate your home network as the cause. Plug a laptop directly into the Starlink router with an ethernet cable — not connected to Wi-Fi at all — and run a speed test at speedtest.net. Do this at the same moment your Wi-Fi devices are experiencing slow speeds. If the wired ethernet connection is fast (40 Mbps or above) while Wi-Fi is slow, your problem is entirely local: device overload, Wi-Fi congestion, or router placement. The Starlink connection itself is working fine. If both wired and wireless are slow at the same time, proceed to the next steps — the problem is at the Starlink level, not inside your home.
Open the Starlink app on your phone, go to the app’s main menu, and select the obstruction check feature. Walk to where your dish is physically installed — the scan must be done at the dish location, not from inside the house. The app uses your phone’s camera to map the sky above and shows which areas are blocked. Look specifically at the southern and southwestern quadrants, as these cover the satellite arcs most active for U.S. locations during peak evening hours. Any marked obstruction in these zones is a direct cause of your evening slowdown. The fix is to move the dish to a location where the obstruction is out of the satellite path — sometimes this requires raising the dish on a mast or relocating it by just one or two meters.
In the Starlink app, navigate to your account’s data usage section. Check how much priority data you’ve used this billing cycle relative to your plan’s allotment. If you’re on Residential Lite, your data is fully deprioritized at all times — this won’t change within your current plan. If you’re on standard Residential and have exceeded your priority data allotment for the month, your remaining traffic this cycle runs deprioritized. This is fixable: additional priority data can be purchased in increments through the app, or you can simply know the situation and wait for the next billing cycle to reset. If you consistently exceed your priority allotment, upgrading to a higher-tier plan is the structural fix.
The Starlink app displays status alerts when hardware problems are detected. Look for notifications about motor errors (on older dish models with actuators), “mast not vertical” warnings, or thermal throttle alerts. A thermal throttle is particularly common in summer and early evening — the dish reduces its output to protect internal components when it overheats in afternoon sun, and may still be throttled into the early evening hours. If hardware alerts are showing, contact Starlink support through the app. Replacement units have been provided to users where support confirmed a hardware fault — particularly for older dish generations. Starlink support is handled through the app; there is no public phone number for residential support.
If congestion is confirmed as your cause and your local setup checks out fine, the most practical action available is scheduling high-bandwidth tasks outside peak hours. Large software updates, game downloads, cloud backups, and video uploads all consume significant bandwidth. Scheduled between 11 PM and 6 AM, they run on an essentially uncongested network and complete faster while not competing with your household’s evening streaming and video calls. Many operating systems, game platforms, and cloud backup tools have native scheduling options. Smart home devices on a schedule can also shift their bandwidth usage automatically. This is not a workaround — it’s genuinely effective, and many Starlink users in congested areas report that their daytime and late-night experience is completely satisfactory while only peak hours cause issues.
Your specific plan determines how the network treats your traffic when satellite cells are congested. Understanding this is essential — the same physical setup behaves very differently depending on which plan is active.
The Residential Lite plan uses fully deprioritized data by design — not just at peak hours, but at all times. This means any congestion on any satellite cell, at any hour of the day, places Lite traffic behind all Standard and Priority users. Evening peak hours compound this because the network is already strained and your traffic gets the least favorable queue position. Residential Lite is designed for households with low bandwidth needs that can tolerate variable performance — it is not a good fit for households that stream video, participate in video calls, or play online games regularly, particularly in the evening. If you’re on Residential Lite and experiencing consistent evening slowdowns, the plan itself is a contributing cause. Upgrading to standard Residential restores priority queue access.
Standard Residential customers receive priority queue status on the network — until their monthly priority data allotment is exhausted. Once that cap is crossed mid-month, remaining usage for the cycle drops to deprioritized status. For households with moderate usage, this is rarely a problem. For households with multiple heavy streamers, remote workers on video calls all day, or avid online gamers, the allotment can be consumed in the first two weeks of a billing cycle — leaving the final two weeks of every month in a deprioritized state that’s often mistaken for congestion. Check your usage in the Starlink app to know exactly where you stand. Additional priority data is purchasable in increments when needed.
Priority plan holders maintain first-queue network status regardless of how congested the cell is. During peak hours when Residential and Lite users see 30–40 Mbps, Priority users on the same cell may still see 120–200 Mbps depending on overall cell load. Priority plans are tiered by the amount of priority data purchased, ranging from lower-volume options to multi-terabyte tiers for high-usage businesses and households. The practical median U.S. download speed on Priority in less congested areas reaches 150–220 Mbps. Priority is not immune to all congestion — a severely overloaded cell affects everyone to some degree — but it is by far the most resilient plan during peak hours. It’s also the plan Starlink explicitly recommends for households with high bandwidth needs.
This pattern points directly at peak-hour congestion. Start with the wired ethernet test — plug a laptop into the router and run a speed test at speedtest.net while your TV is buffering. If wired speeds are also slow (under 25 Mbps), the problem is at the network level: congestion, deprioritization, or obstruction. Check your data usage in the Starlink app to confirm you haven’t crossed your priority cap. If you’re on Residential Lite, you’re always deprioritized — the plan itself is a factor. Practical fix for streaming specifically: Netflix, Disney+, and most streaming services have a quality setting. Dropping from 4K to 1080p or 720p during peak hours requires roughly one-quarter the bandwidth — that alone often eliminates buffering on a congested connection without affecting other users in the house.
Gaming is hit by two separate Starlink mechanisms at once — congestion-raised latency and satellite handoff packet loss. The handoffs occur every 15 seconds regardless of congestion; at night, the higher base latency from congestion turns handoff packet loss into visible rubber-banding. Wired ethernet makes a measurable difference for gaming specifically — Wi-Fi adds jitter that compounds handoff effects. If you’re already wired, check your ping using the Starlink app’s real-time statistics: latency above 60 ms during gaming indicates network congestion beyond the normal handoff pattern. Games with large update downloads (100 GB+ patches) also absorb bandwidth even when running in the background — schedule all game updates for after 11 PM through your console’s power settings.
Video calls are particularly sensitive to packet loss — even a single handoff drop of a fraction of a second causes a freeze, and congestion-raised latency above 80 ms makes audio feel out of sync. Run your video calls in a room close to the router and use a wired ethernet connection if at all possible. If wired ethernet is not an option, ensure your device is connected to the 5 GHz Wi-Fi band (not 2.4 GHz) — the 5 GHz band is less congested from other household devices even though it has shorter range. On Zoom, Microsoft Teams, and Google Meet, you can manually lower your outgoing video quality to “Standard” in settings — this reduces upload bandwidth consumption and makes calls far more stable on a marginal connection. Upload on Starlink is limited to 10–15 Mbps at the best of times, and conserving it during calls matters.
When speed changes dramatically from one night to the next with no changes to your setup, weather is usually the first thing to rule out — and the simplest to confirm. Check whether there’s a storm, rain, or dense cloud cover in your area. If conditions are clear and speeds are still dramatically worse than the previous night, run the obstruction scan in the Starlink app — trees move seasonally and a branch that wasn’t blocking your dish last month may now be in the satellite path. Also check the Starlink status page or the r/Starlink community for reports of outages or maintenance in your region. Network-level outages do occur occasionally — if the problem resolves within an hour or two with no action on your part, it was likely a brief satellite or ground station issue.
A steady multi-month degradation pattern — rather than a single-night event — usually indicates that subscriber density in your coverage cell has been increasing faster than SpaceX has added satellite capacity for your region. This is a documented pattern in areas where Starlink has aggressively added customers without proportional constellation expansion in that specific coverage zone. Practical options: First, check whether upgrading to a Priority plan restores acceptable performance — Priority holders are insulated from much of the subscriber-growth impact. Second, contact Starlink support through the app and report the degradation pattern with speed test data across multiple days and times. Third, if you’re in a rural area with cellular service, compare Starlink to current 5G fixed wireless options in your market — providers like T-Mobile Home Internet have expanded availability significantly and may now serve your address.
This is the clearest possible signature of pure peak-hour congestion with no other compounding factors. Your dish, cable, router, and satellite connection are all working correctly. Your coverage cell is simply overloaded between 6 PM and midnight, and traffic eases after that. This tells you several things: your plan is receiving priority service as expected (otherwise you’d see slow speeds even after midnight), and the fix is about timing rather than hardware. Schedule your largest downloads, cloud syncs, and software updates for after midnight. For streaming in the evenings, lower streaming quality settings to reduce per-stream bandwidth. If your work requires consistent, high-speed performance in the evening, the Priority plan is the only Starlink option that reliably improves this — or consider whether a backup 4G/5G cellular connection makes sense for evening-only use when Starlink is congested.
This guide is for general informational purposes only. Starlink performance varies by location, coverage cell density, plan type, time of year, and network conditions. Speed figures and plan details are based on publicly available information and real-world data from independent sources current as of mid-2026. Plan pricing, data allotments, and prioritization rules are subject to change by SpaceX without notice — always verify current details at starlink.com. This content is entirely original.