Why Your Starlink Keeps Rebooting (and the Solutions)

When your Starlink keeps rebooting in Nigeria, the app often blames 'connecting' or 'searching' while your household blames the installer. In our field logs across Lagos, Abuja, and Port Harcourt estates, the majority of reboot loops trace to power quality, overheating enclosures, damaged cables, or obstruction hunts — not mysterious satellite gremlins. Nigerian grid context matters: NEPA flickers, estate generator changeovers, and shared neutral issues reboot consumer routers multiple times per day if you skip conditioning.

This guide walks through the failure modes we see weekly and the fixes that stick. Work the list in order — power first, thermal second, cable third, sky view fourth — before factory reset or RMA chatter online wastes your week.

NEPA flickers and voltage sag

Brief grid drops cause hard reboots. Starlink dish and router draw modest wattage but surge during satellite search after power returns. If your estate shares a thin feeder cable or long extension cord from a neighbour's generator tap, sag during motor starts drops voltage below what the router tolerates. Symptoms: reboot at the exact moment neighbours start AC units or the borehole pump.

Fix: dedicated socket on a known-good circuit, shorten extension paths, and add a line-interactive UPS sized for router plus dish inrush. A 600–1,000 VA UPS is common for home kits — minutes of runtime, not hours, but enough to ride through flickers. For longer outages, pair with inverter or generator — but see generator section below.

UPS sizing honesty

UPS marketing promises hours; physics delivers minutes at combined dish+router load. Document expected runtime. Our power backup article covers Nigerian estate scenarios without pretending a ₦40,000 UPS replaces fuel planning.

Generator changeover reboots

Estates that switch from AEDC or EKEDC to diesel often blackout networking gear for 10–30 seconds during transfer. Every device reboots; Starlink searches satellites again; WhatsApp calls drop. Fix: UPS on networking gear, coordinate with estate engineers for faster transfer switches, or segregate a dedicated circuit for ICT loads that stays up during changeover where wiring allows.

Modified sine inverters — common in Nigerian home setups — cause odd router behaviour even when voltage looks fine on a cheap meter. Pure sine output matters for sensitive electronics. If reboots correlate with inverter mode, test router on grid-only power for a day.

Overheating router and dish placement

Starlink routers in closed TV consoles, metal boxes, or direct afternoon sun through Nigerian windows thermal-throttle or reboot. Dish electronics tolerate outdoor heat better than indoor routers stuffed behind curtains. Ensure ventilation, shade indoor gear, and don't stack router on top of a hot AV receiver.

Roof-mounted networking boxes without airflow are a Lagos special — sun-baked enclosures hit 50 °C by 2 p.m. Use ventilated outdoor-rated cabinets or bring termination indoors with proper glands.

Cable faults and intermittent PoE

The integrated dish cable on Gen 3/4 kits is not field-serviceable cheaply. Pinches from door frames, sharp bends through wall glands, or rodent damage cause reboot loops that look random. Inspect the full run: gentle bend radius, no kinks, glands intact. Intermittent contact at the router port triggers power cycles during wind vibration on long exterior runs.

Professional installs route cable away from generator exhaust and rat paths. Rework after DIY pinches costs more than conduit planned on day one.

Obstruction hunts and firmware updates

After reboot, the dish motors search satellites. High obstruction scores prolong 'searching' — users perceive endless reboots. Run the app's obstruction tool at the mount location; trim trees or raise the mast if score rose after new construction. Firmware updates occasionally require power cycle — do one clean reboot, not ten angry ones.

Double NAT, mesh conflicts, and bypass mode

Adding a third-party router without understanding bypass mode can cause DHCP fights — less often a true reboot, more often 'offline' cycling. Document topology: Starlink router in bypass, single DHCP server, mesh controller on wired backhaul. Estate IT in Lekki sometimes stacks two consumer routers from different vendors; pick one firewall.

When to contact support vs your installer

If power is clean on a meter, cable inspects fine, obstruction is low, and reboots persist across swapped router power supplies, log app errors and contact Starlink support. If reboots correlate with generator hour or rain only, fix environment first. DataGram handover packages include baseline obstruction screenshots and power notes so support calls aren't guessing.

Estate-wide patterns — not just your flat

If every flat on the same generator feeder reboots together at 7 p.m., the fix is estate engineering, not twelve individual Starlink tickets. Document timestamps, compare with neighbours, escalate to facility management with meter readings. We've seen Lekki blocks where neutral issues caused weekly evening reboots until the estate upgraded transfer switch timing — Starlink was innocent.

Harmattan dust season adds another layer: static discharge and dirty earth bonds cause mysterious gremlins on outdoor mounts. Inspect glands and earth connections in February before March rains — preventive maintenance beats emergency ladder calls.

Logging for intermittent faults

Enable router syslog to a local NAS if you run bypass mode with capable gear. Note exact times of reboots against generator logs, rain radar, and who started the borehole pump. Intermittent faults without logs waste everyone's time — including Starlink support reading 'it just stops sometimes' without timestamps.