Starlink Troubleshooting: Top 10 Common Issues & How to Fix Them
Starlink troubleshooting usually starts with a 30-second reboot, then checking app status, obstructions, and cable health. Most common failures come down to power, alignment, WiFi, or congestion, and many clear without support if you test speeds and outage logs before opening a ticket.
The ten failures that actually happen, what is really causing each one, and the fixes veteran installers use before picking up the phone to support.
Before you call support, try this 30-second diagnostic
Nine out of ten Starlink support tickets get closed with "please reboot and retest." Before you burn 48 hours waiting for that reply, do the same thing yourself first. Unplug the router, count to 30, plug it back in, wait 3 minutes. Then open the Starlink app and check three things: the status bar (online / offline / searching), the obstruction percentage, and the outage log. If the status is online and the outage log is empty, the issue is almost certainly a WiFi, DHCP, or device-side problem rather than Starlink itself. If status says searching or offline after a clean power cycle, you have a real satellite-link issue worth digging into. Run a baseline test with our free speed test before and after. The numbers tell you whether the reboot actually fixed anything or just hid the symptom.
The top 10 issues (and how to fix each one)
Every failure below is framed the same way: the symptom you actually notice, the likely cause, and the fix in order of what veteran users try first. Do not skip steps. The cheap fixes genuinely resolve most cases, and the expensive fixes rarely help when the cheap ones did not.
Issue 1: Completely offline, router red light
Symptom: No internet on any device. Router LED glows solid red or is fully dark. Starlink app shows "Disconnected" or cannot reach the dish at all. Likely cause: power delivery problem at the router, a damaged dish cable, or a software hang that crashed the router firmware and it did not auto-recover. Fix: unplug the router from the wall, wait a full 30 seconds (capacitors need to drain), plug it back in, and watch. A solid white LED within 3 minutes means you are back. Still red after 5 minutes means either the dish cable is damaged (inspect both ends for bent pins or cuts) or the router itself has failed. Swap the dish cable if you have a spare. If the router LED stays dark with the power cable confirmed good, the router is dead. Starlink warranty replaces it free within the first year.
Issue 2: Dish says "obstructed"
Symptom: App shows a red or orange obstruction banner, frequent brief dropouts during video calls, speed looks fine off-peak but hitches under load. Likely cause: a tree branch, chimney, or new construction has crept into the 25-degree cone the dish needs. Obstructions become severe at >20% sky blocked. Fix: open the app, go to Visibility, and wait 12 to 24 hours so it accumulates enough satellite-pass data to draw a real map. Red arcs are hard obstructions (buildings, chimneys); orange blobs are soft obstructions (trees, branches). Fixing obstructions is the highest- leverage improvement for a sick dish. Use our sky photo analyzer to simulate a different mount location before you drill holes, and check our full obstruction guide for pole-mount specs that actually clear residential canopy.
Issue 3: Slow speeds during the day but fast at night
Symptom: Noon speed tests show 60 to 90 Mbps; 3am tests show 250+ Mbps; everything feels sluggish during working hours. Likely cause: unusual for Starlink. The normal pattern is fast days and slow evenings. If your pattern is inverted, the cause is usually a background uploader on your own network (cloud backup, security camera, CCTV NVR) or a scheduled OS update saturating upload at the worst time. Fix: run a speed test with nothing else on the network. If it is normal, walk through every connected device and check its scheduled tasks. The usual suspects: Dropbox or iCloud midday backup, Ring cameras uploading event clips, a thermostat or security hub pushing telemetry. Reschedule heavy uploaders to 2 to 5am, which is also when Starlink firmware updates normally push and the network is emptiest anyway.
Issue 4: WiFi works, but internet doesn't (DHCP issues)
Symptom: Devices connect to the Starlink WiFi fine, but web pages never load. Ping to 8.8.8.8 times out. Ping to the router (192.168.1.1) works. Likely cause: the dish is offline while the router is still serving WiFi and DHCP, a classic failure mode after a firmware update that rebooted the router but left the dish stuck. Fix: open the Starlink app. If it shows "Searching" or "Offline" for the dish, this is confirmed. Power-cycle the router, wait 3 minutes. If the dish still will not come online, check the cable at both ends (dish side first, since the connector is a common failure point because of weather exposure). Second-line DHCP issue: your own device has a stale lease. On the client, turn WiFi off and on, or release-and-renew the DHCP lease in network settings.
Issue 5: Can't log in to the Starlink app
Symptom: App opens but refuses to sign you in, or signs you in but shows "No dish connected" even though internet works fine. Likely cause: either your Starlink account session expired (happens every 30 to 60 days), or the app is trying to reach the dish over a path that is blocked. This happens when your phone is on a different WiFi network than the Starlink router, or when a VPN is intercepting local traffic. Fix: force-quit the app, turn off any active VPN, make sure your phone is connected to the Starlink WiFi (not a cellular hotspot, not a neighbor's network), and relaunch. If the sign-in itself fails, go to starlink.com in a browser, complete the web login, and come back. The app picks up the fresh session. For persistent failures, uninstall and reinstall the app; this clears the corrupt auth cache that sometimes survives sign-out.
Issue 6: Connection drops every few minutes
Symptom: Video calls freeze briefly every 2 to 4 minutes, streaming rebuffers on a schedule, online games disconnect during matches. Likely cause: a marginal obstruction is catching you during satellite handoffs. Starlink hands off between satellites every 2 to 4 minutes, and if any chunk of the handoff arc is blocked, you get a brief dropout right on that cadence. A typical healthy user sees 0 to 2 brief drops per day as normal. More than that is a real problem. Fix: check the app's outage log. If drops are all attributed to "Obstructed," fix the view. If they are attributed to "No satellites," you are at an edge-of-coverage site. If they are unattributed, power-cycle, then check the dish cable connector for corrosion.
Issue 7: Stuck on "Searching for satellites"
Symptom: App shows "Searching" indefinitely, usually more than 10 minutes. Dish motors may or may not have moved. Likely cause: dish is physically pointed wrong (moved by wind or vandalism), has lost its orientation calibration, or is in an area where no satellite is currently visible. Fix:go outside and look at the dish. It should have tilted and rotated on its own during boot. If it is stuck flat, the motor may be jammed. Check for ice, debris, or a bird nest underneath. Second, power-cycle and watch it boot: the dish should audibly move during the first 2 minutes. If it is silent and flat, the motor has failed. Third, in the app, Settings, Stow & Unstow, force a stow cycle, wait 60 seconds, unstow. This forces recalibration.
Issue 8: Router rebooting randomly
Symptom: WiFi drops for 30 to 60 seconds every few hours, at no particular time of day. LED briefly goes dark and returns to white. Likely cause: a thermal issue (router in a hot cabinet with no airflow), a marginal wall outlet, or a firmware bug that the next update will fix. Fix: move the router to an open shelf with 10cm clearance on all sides. If it lives in a media cabinet, add a small USB fan. Second, plug it directly into a wall outlet rather than a power strip or UPS because some UPS units produce modified sine wave output that upsets switching power supplies. Third, check the firmware version: if you are more than 30 days behind current, a reboot plus 48 hours of uptime usually pulls the latest update. If none of the above helps, the router has a hardware fault worth an RMA.
Issue 9: Speeds dropped since last firmware update
Symptom: You were consistently seeing 200+ Mbps, a firmware update rolled out overnight, and now you are stuck at 80 to 120 Mbps no matter what time of day. Likely cause: a regression in the new firmware, or a new congestion-control algorithm that penalizes your specific cell. Firmware normally pushes between 2am and 4am local time, and the dish auto-reboots afterwards. Fix: first, confirm it is actually the firmware. Check the Starlink subreddit for your date; if others in your region are complaining the same way, it is firmware. Second, do a full power cycle, not just an app reboot. Some regressions only clear with a cold boot. Third, if a hot-fix ships within a few days, it will auto-install overnight. If the issue persists past a week, file a support ticket with before-and-after speed test logs; the engineering team tracks this data and occasionally rolls back.
Issue 10: No internet after moving locations
Symptom: You relocated the dish to a new house, RV park, or travel stop, and it will not connect at all, or only connects with very slow speeds. Likely cause: your service address has not been updated, or you moved outside your service area on a Residential plan (Residential is geo-locked to one cell; Roam is portable). Fix: open the app, Settings, Service Address, and update to your new location. For short trips, Roam is the right plan. Residential will sometimes work outside home for a few days then throttle to dial-up speed as penalty. If you are between houses or comparing what you actually need, walk through our plan picker . It asks the six questions that actually determine whether Residential, Roam Regional, or Roam Global is the fit.
Quick symptom to fix lookup
When you just need the one-line answer without the explanation, this table is the cheat sheet. Scan the left column for what you are seeing, read the middle column for what it probably means, and act on the right column.
| Symptom | Likely cause | One-line fix |
|---|---|---|
| Router red LED | Power or firmware hang | Unplug 30 sec, repower |
| Router dark LED | PSU or outlet failure | Test outlet, swap PSU |
| Stuck on "Searching" | Motor jam or calibration | Force stow / unstow in app |
| Dropouts every 2-4 min | Handoff obstruction | Fix sky view or raise mount |
| Slow evenings only | Cell congestion | Upgrade Priority or wait |
| Slow days, fast nights | Local uploader saturating | Audit background apps |
| WiFi up, internet down | Dish offline, router OK | Power-cycle, wait 3 min |
| Can't log into app | Session expired or VPN | Disable VPN, web sign-in |
| Upload under 5 Mbps | Cell oversubscription | Retest at 3am to confirm |
| Ping over 100ms sustained | Congested cell or obstruction | Check obstruction map |
| Jitter spikes >30ms | Satellite handoff failures | Survey sky view |
| Frequent random reboots | Thermal or firmware bug | Improve airflow, update FW |
| Dish won't boot at all | Cable or PoE injector fail | Swap dish cable |
| Speed drop post-update | Firmware regression | Cold power cycle, wait a week |
| No service after move | Wrong plan or unupdated address | Update service address in app |
| Snow on dish, no signal | Self-heat failed or off | Enable snow-melt in app |
| Thermal shutdown summer | Dish surface over 60°C | Shade or paint white matte |
| WiFi slow but wired fast | WiFi environment issue | Check 5GHz band, clients |
| App won't find dish | Phone on wrong network | Connect to STARLINK SSID |
| New install wildly slow | First-day obstruction map noise | Wait 24 hours, retest |
When to contact support vs community
A lot of Starlink tickets that got filed should have been Reddit posts, and a smaller number of Reddit threads that dragged on for days should have been support tickets. Use the table below to route yourself correctly the first time. The rule of thumb: if the symptom is unique to your hardware serial number, go to support; if it is a general pattern others would recognize, go to the community.
| Symptom persistence | Official support response | What info to include |
|---|---|---|
| Hardware dead on arrival | 24-48h, RMA issued | Order number, photo of LED state |
| Intermittent dropouts >1 week | 48-72h typical | Outage log screenshot, obstruction map |
| Speed under 50 Mbps sustained | 48h, diagnostic remote pull | Three speed tests at 10am, 2pm, 9pm |
| Billing or plan issue | 24h, ticket escalation | Invoice number, account email |
| Firmware regression | 3-7 days if confirmed widespread | Before/after speed logs, FW version |
| Obstruction score disagreement | Not a support issue | Take to Reddit instead |
| "Is this normal?" | Not a support issue | r/Starlink answers in <2h |
| Dish physically damaged | 24h, warranty check | Photos, serial number, purchase date |
When you do open a ticket, format matters. A short, specific ticket with attachments gets answered faster than a long emotional one. Good ticket template: one sentence describing the symptom, one sentence stating what you already tried (reboot, cable check, obstruction review), three screenshots (speed test, app dashboard, outage log), and your firmware version. Do not open multiple tickets for the same issue — it resets your queue position and annoys the agents who eventually pick it up.
Diagnostic tools you already have
The Starlink app is the primary diagnostic surface, and most users never open the pages that actually matter. Three sections are worth learning:
Statistics. Settings, Advanced, Statistics shows a 12-hour rolling graph of download, upload, ping, and outage seconds. The outage graph is the single best signal for whether you have a dropout problem versus a slow-speed problem — the two get confused constantly. Ten brief outages in a day reads as "slow internet" to most people even though the speed tests are fine between drops.
Speed tests. Run the built-in test for a baseline, but also run a third-party test to sanity-check it. The Starlink app tests against Starlink's own backhaul, which is the best-case path. A third-party test against a server 500 miles away tells you what users actually experience. Our in-browser speed test measures against servers on three continents and logs history so next week's number is comparable to this week's.
Obstruction map. Settings, Visibility. Wait 12 to 24 hours after install before trusting the map — the first-hour reading is always optimistic because not enough satellite passes have happened yet. Our sky photo analyzer gives you the same read from a phone photo in under 30 seconds, which is useful before install or when planning a mount relocation. For broader planning, the coverage map shows where satellites pass densely versus sparsely in your region, and our total cost calculator helps you decide whether the plan you have matches your actual usage.
Community resources: where the real answers live
Starlink's official support is fine for hardware RMAs and billing. For everything else, the community answers faster and more accurately because the sample size is larger. The three places worth bookmarking:
r/Starlink on Reddit. 500,000+ members, median first-reply time under 2 hours, and a saved-post tradition of documenting firmware regressions in real time. Search before posting — your issue has almost certainly been covered. The subreddit mods pin current firmware status at the top during rollouts.
Official Starlink Discord. Text-channel format, more immediate than Reddit, stronger for live debugging. Regional channels for US, EU, AU, and LATAM mean you get advice from people on your same satellite cell.
Regional user groups. Facebook groups, WhatsApp groups, and forums specific to RV, boating, and off-grid communities. These are the best sources for install advice on niche setups — marine mounts, overlanding rigs, solar-off-grid sites. The generalist forums will give you generalist advice; the niche ones give you the install photo that solves your specific problem.
FAQ
How do I reboot my Starlink?
The fastest reboot is a simple power cycle: unplug the router from the wall outlet, wait 30 seconds, and plug it back in. The dish draws power through the router, so this reboots both units together. Normal boot time is 2 to 3 minutes — the dish repositions, searches for satellites, and re-registers with the network. If a power cycle does not resolve the issue, use the Starlink app: Settings, Advanced, Reboot. That triggers a clean software restart without interrupting power. Avoid rebooting more than once every 10 minutes, because repeated reboots can delay firmware updates that only push during idle windows.
Why is my Starlink offline?
The three most common causes, in order: a tripped outlet or loose cable at the router (check the wall plug first, then the dish cable); a software hang that clears with a 30-second power cycle; or an ongoing regional outage. Before doing anything else, open the Starlink app — if the whole dashboard shows an outage banner, it is not your hardware. If the app says your dish is offline but no outage banner appears, power-cycle the router, wait 3 minutes, and watch the router LEDs. Solid white means online. Red or no light after 5 minutes means a hardware, cable, or obstruction problem worth investigating further.
What's the factory reset for Starlink?
The Gen 3 router factory reset is a physical button on the underside — press and hold it for a full 20 seconds with the router powered on. You will see the LEDs flash and then go dark as the unit wipes its configuration and reboots. Factory reset clears your custom WiFi name, password, and any port-forwarding rules, but it does NOT unpair the dish from your Starlink account. After reset, reconnect to the default WiFi network (“STARLINK” unsecured), open the app, and walk through setup again. Only do this if a normal reboot and app-based reboot have both failed.
Why is Starlink slow at night?
Every Starlink coverage cell has a finite per-satellite capacity shared among hundreds or thousands of subscribers. Peak congestion runs 7pm to 11pm local time, when everyone in the cell streams and games simultaneously. Residential traffic is also deprioritized once you cross your monthly priority-data cap, which typically happens mid-month for heavy users. A cell that delivers 220 Mbps at noon can easily drop to 60 to 90 Mbps at 9pm. This is normal, not a fault. If consistent evening speeds matter, upgrade to a Priority plan, or shift bandwidth-heavy tasks (backups, large downloads) to overnight hours when cells sit idle.
How do I contact Starlink support?
Open the Starlink app, tap Support at the bottom, and submit a ticket — this is the only official channel. Phone support does not exist for residential customers. Typical response time is 24 to 48 hours, sometimes longer during firmware rollout windows. Include: a timestamped screenshot of the speed test, the obstruction map, the outage log from the app, and your router and dish firmware versions (found under Settings, Advanced). Do NOT open multiple tickets — it resets your queue position. For faster community answers, the r/Starlink subreddit and the official Starlink Discord respond within 2 hours on average, and veteran users there have seen every failure mode.
Can I use my old Starlink Gen 2 dish with Gen 3 router?
Yes, but with caveats. The Gen 3 router ships with a USB-C to proprietary dish cable that works with both Gen 2 rectangular and Gen 3 standard dishes. You will need either the original Gen 2 cable or an adapter (Starlink sells one for $25). Mixing generations means you get Gen 3 WiFi 6 performance but Gen 2 dish specs — same throughput ceiling as before, slightly lower efficiency than a matched Gen 3 setup. If you are already paying for Priority and running a business, the dish swap is worth it. For Residential users with working Gen 2 hardware, the Gen 3 router alone is the most cost-effective upgrade.
The short version
Before you call, reboot. Before you reboot, check the app dashboard. Before you panic about the speed number, run three tests at three different times and compare. Most Starlink issues are cell congestion, WiFi noise, or one obstruction nobody surveyed properly. The hardware itself is genuinely reliable — when it fails, it fails in the obvious way (dead LED, dead dish), not the subtle one. Use the tools below to rule out the common causes in minutes instead of days.
Run a Speed Test
Baseline your connection in under 30 seconds. Measures download, upload, ping and jitter, and saves history locally so next week's number actually means something.
Start testSky Photo Analyzer
Upload one wide-angle sky photo from your dish location. Get an exact obstruction percentage and a heatmap of what is blocking your view, in about ten seconds.
Analyze my sky