Starlink Slow at Night? How to Diagnose Peak-Hour Congestion
Speed & Performance
Starlink can feel fast during the day and suddenly struggle in the evening. That pattern is useful evidence: it may point to local Wi-Fi traffic, several devices sharing the connection, or high demand in your wider Starlink service area.
This guide gives you a repeatable way to identify the bottleneck before you move the dish, replace equipment, or change your plan.
What “slow at night” usually looks like
Peak-hour trouble often appears between late afternoon and bedtime, when more households are streaming, gaming, downloading updates, and making video calls. You may notice:
- lower download speed while upload speed changes less;
- higher latency under load;
- buffering that starts at roughly the same time each day;
- good results in the morning but poor results in the evening;
- one device performing badly while another remains usable.
A single speed test cannot tell you which cause applies. Compare results over time and control as many variables as possible.
Start with a three-time test
Choose one device and run the same test in the morning, early evening, and late evening. Repeat this for at least two days if possible.
For each test:
- Pause large downloads, cloud backups, game updates, and 4K streaming.
- Stand near the router, or use Ethernet if your setup supports it.
- Run the Starlink app’s advanced speed test when available. This can help separate the internet-to-router result from the router-to-device Wi-Fi result.
- Record download speed, upload speed, latency, the time, and whether anyone else was using the connection.
- Check the app’s outage and obstruction information for events during the same period.
Do not chase the highest number. You are looking for a repeatable pattern.
Separate Starlink performance from Wi-Fi performance
A slow phone or laptop does not always mean the satellite link is slow.
If the router-to-device part of the advanced test is weak but the internet-to-router result is healthy, focus on Wi-Fi. Move closer to the router, try the other Wi-Fi band if your network exposes separate bands, and avoid placing the router inside a cabinet or behind a television. Test Ethernet where practical.
If both parts slow down at the same evening times, the cause is more likely upstream or related to total household demand.
If Ethernet is fast while Wi-Fi is slow, adding internet capacity will not fix the real problem. Improve router placement, add a well-positioned mesh node, or use wired connections for fixed devices.
Check what your own network is doing
Evening congestion can begin inside your home. One console update, computer backup, security-camera upload, or television stream can consume enough bandwidth to affect everyone else.
During a slow period:
- pause streaming on other televisions and tablets;
- stop cloud photo and computer backups temporarily;
- check consoles and computers for automatic updates;
- disconnect unused devices for ten minutes;
- rerun the same test on your chosen device.
If performance immediately improves, reconnect activities one at a time. This identifies the heavy user without guessing.
Third-party routers may show real-time traffic by device. If yours supports traffic monitoring, look for sustained downloads or uploads. A saturated upload can make ordinary browsing and calls feel slow even when download capacity remains available.
Rule out obstructions and equipment faults
Obstructions and cable faults can occur at any hour, so do not label the problem “congestion” until you check them.
Open the Starlink app and review the obstruction map and recent outage events. A repeating event tied to a tree, roofline, or other object needs a placement fix. Random disconnections or a “disconnected” state deserve a cable, connector, and power check.
Also confirm that:
- dish and router connectors are fully seated;
- the cable has no sharp bends, crush points, cuts, or water exposure;
- the router has airflow and is not unusually hot;
- a wired connection has negotiated its expected link speed;
- no power-saving timer or smart plug is interrupting the system.
Moving the dish will not solve shared network demand, but it can solve a genuine obstruction. Let the evidence choose the action.
How to recognize likely peak-hour congestion
Shared-capacity congestion becomes more likely when all of these are true:
- morning and off-peak tests are consistently much better;
- evening slowdowns recur at similar times;
- Ethernet and the app’s router-level result are both affected;
- there are no matching obstruction or outage events;
- pausing activity on your own devices does not restore performance;
- cables, power, and router health appear normal.
No individual result proves congestion. The pattern across several controlled tests is what matters.
Practical fixes that can help tonight
You cannot directly control demand outside your home, but you can reduce its impact.
Schedule heavy traffic
Move operating-system updates, game downloads, cloud backups, and large file transfers to quieter hours. Many apps, backup tools, and routers include schedules or bandwidth limits.
Protect calls and interactive traffic
If you use a compatible third-party router, enable its quality-of-service or smart queue feature. Prioritize work calls, voice traffic, and gaming above bulk downloads. Start with conservative settings based on the speed you can reliably sustain during the slow period, not the best speed you have ever measured.
Poorly configured QoS can reduce performance, so change one setting at a time and keep notes.
Wire important devices
Ethernet cannot remove upstream congestion, but it removes Wi-Fi interference and variability. A wired work computer, console, or television gives limited capacity a cleaner path.
Lower streaming demand
Set televisions to a lower resolution during the busiest hours, disable autoplay, and avoid several simultaneous high-resolution streams. This often creates more noticeable headroom than repeatedly rebooting the router.
Keep a backup for critical work
For essential meetings or business systems, maintain a tested mobile hotspot or second connection where coverage permits. Test the backup before you need it, and keep its data limits in mind.
What usually does not fix peak-hour congestion
Repeated factory resets erase settings and rarely help a time-based capacity problem. Buying a new mesh system will not improve the satellite link if the router-level result is already slow. Repositioning an unobstructed dish is also unlikely to change a slowdown that appears only during busy hours.
A normal reboot is reasonable if the system has developed a new fault, but do not use rebooting as the main diagnostic method. It changes conditions without showing which condition mattered.
Build a useful support record
If the problem is persistent, collect evidence before contacting support:
- dates and exact test times;
- morning and evening advanced-test results;
- screenshots of relevant outages or obstruction data;
- whether the test used Ethernet or Wi-Fi;
- which household activity was paused;
- any error or alert shown in the app.
Describe the pattern plainly: for example, “router-level download performance falls every evening, while morning tests are consistently better; local traffic was paused and no obstruction events matched the tests.” This is more useful than reporting that the connection is simply slow.
A simple decision checklist
Use this order:
- Test the same device at several times.
- Compare Wi-Fi performance with the router-level or wired result.
- Pause other household traffic.
- Review outages and obstructions.
- Inspect power, cables, and connectors.
- Apply traffic scheduling, wiring, or QoS where appropriate.
- Document repeatable evening degradation and contact support if it continues.
The goal is not to produce a perfect speed-test score. It is to find the limiting part of the connection and make the busiest hours more predictable.