Independent · not affiliated with SpaceX or StarlinkReport: logger not startedFacts checked

Troubleshooting

Five ways work internet fails on Starlink, and the fixes

Each problem below runs the same way: what you see, why it happens, a two-minute check, the fix, and the full guide. Start with the one that matches your symptom.

Quick answer

Most work problems on Starlink come from five causes: a VPN type that can’t pass CGNAT, short drops from obstructions, Wi-Fi calling settings, no automatic failover, and uploads filling the line during calls. Match your symptom below; each fix is cheap or free to try.

Facts checked Research-based, not measured by us

VPN fails
Check the VPN type
Calls freeze
Check obstructions and uploads
Wi-Fi calling
Phone settings, then carrier
Outage stops work
Add a failover router

1. The work VPN won’t connect, or keeps dropping

Symptom: the VPN client spins and fails, or connects and then dies with no error.

Cause: Residential and Roam plans use carrier-grade NAT (checked Oct 5, 2026). Starlink says VPNs over TCP or UDP work if they support NAT traversal. It lists Client VPN protocols Starlink lists as generally working well with CGNAT: SSTP, OpenVPN, WireGuard. It also lists Client VPN protocols Starlink lists as generally not working well with CGNAT: PPTP and L2TP. Also GRE and IPsec without NAT-T for site-to-site. And: CGNAT drops VPNs relying on IP protocols 47 (GRE), 50 (ESP), 51 (AH) and 115 (L2TP).

Quick check: ask IT, or look in the VPN app’s settings, for the protocol name. Then try the VPN from a phone hotspot: if it works there and not on Starlink, the protocol is the likely cause.

Fix: ask IT to switch you to an SSL/TLS, OpenVPN, WireGuard or IPsec-with-NAT-T profile. Starlink says it can’t troubleshoot VPN issues itself (checked Oct 5, 2026), so this goes through your IT team.

Full guide: Starlink and VPNs: what works behind CGNAT.

2. Calls freeze for a few seconds, a few times an hour

Symptom: video freezes, audio cuts out for one to a few seconds, then the call recovers. Speed tests look fine.

Cause: usually something in the dish’s view of the sky: a tree, a roof edge, a chimney. As satellites move across the sky, they pass behind it and the link drops briefly. Satellite handovers also shift latency on a schedule; one researcher measured it every 15 s (not ours). Calls can ride through handovers; they can’t ride through a blocked view.

Quick check: open the Starlink app’s Statistics page, which shows latency, outages and alerts while you’re on the Starlink router (checked Oct 5, 2026). Short outages that line up with your call freezes point at the sky view. Then run the app’s obstruction check.

Fix: move or raise the dish to a clear view. Use Ethernet for the work computer so Wi-Fi drops don’t add to it.

Full guide: Zoom and Teams calls on Starlink.

3. Wi-Fi calling won’t connect or drops calls

Symptom: the phone never shows Wi-Fi calling, calls fail to connect, or they drop when you walk around the house.

Cause: Starlink says Wi-Fi Calling is sensitive to IP geolocation, and that problems can come from device settings, network glitches or carrier restrictions (checked Oct 5, 2026). Often it’s simpler: Wi-Fi calling isn’t turned on, or the emergency address isn’t set.

Quick check: in the phone’s settings, confirm Wi-Fi Calling is on and the emergency address is filled in. Then run a short ping test; Starlink’s guide says to note latency over 200 ms or any loss.

Fix: Starlink’s advice: For VoIP/Wi-Fi Calling problems Starlink says to contact your carrier first, then open a Starlink ticket with IP and ping results. Restart the phone after changing settings, and make sure Wi-Fi reaches every room you take calls in.

Full guide: VoIP and Wi-Fi calling on Starlink.

4. When Starlink goes down, nothing switches over

Symptom: an outage, and you’re scrambling for a phone hotspot in the middle of a call.

Cause: no second line, or a second line with nothing to switch to it. A hotspot in a drawer isn’t failover.

Quick check: unplug the Starlink cable during a quiet hour. If your computer doesn’t get back online by itself within a few seconds, you have no failover.

Fix: a dual-WAN router with Starlink on WAN 1 and a backup (cellular or a second provider) on WAN 2, set to failover with a health check to a public address. Put all three boxes on a UPS. Calls and VPNs will reconnect, because the address changes, but you won’t lose the day.

Full guide: Failover Builder.

5. Video freezes when someone uploads

Symptom: your video turns to blocks or freezes, and others say you’re breaking up, while someone in the house is uploading a file or a phone is backing up.

Cause: upload is the small side of the line. Starlink’s spec for its Residential 100 Mbps plan is Residential 100 Mbps: download capped at 100 Mbps (spec 80-100 Mbps), upload 15-35 Mbps. A big upload grabs most of it, and your call’s packets wait in line.

Quick check: run a speed test with nothing else uploading, then again with the upload running. If upload drops near zero and latency jumps, that’s it.

Fix: pause big uploads during calls, schedule backups overnight, or use a router with smart queue management (SQM) set a little under your measured upload. Lots of devices can also hit the CGNAT limit of 1,200 sessions; Starlink says that can freeze video meetings too.

Full guide: Uploads and large files on Starlink.

IT For your IT person: quick diagnostics
  • VPN: identify the protocol. CGNAT drops VPNs relying on IP protocols 47 (GRE), 50 (ESP), 51 (AH) and 115 (L2TP). Use IPsec with NAT-T, or a TLS- or UDP-based client.
  • Drops: correlate call-freeze timestamps with the app’s outage history; persistent short outages with a clear sky suggest Wi-Fi or local equipment.
  • Upload saturation: test latency under load; enable SQM (CAKE or fq_codel) on a router in bypass mode.
  • Failover: health-check a public IP, not the gateway; set short SIP re-registration timers.

Common mistakes

  • Blaming the satellite before checking Wi-Fi. Plug in with Ethernet first; it’s the cheapest test.
  • Buying a public IP plan for a VPN problem. Most VPN problems are the protocol, not the address.
  • Rebooting the dish over and over. It hides the pattern you need to see.
  • Calling Starlink about the work VPN. Starlink says it can’t troubleshoot VPNs; start with IT.

Questions people ask

Why does my work VPN not connect on Starlink?

Usually because it uses a VPN type that can’t pass through carrier-grade NAT. Starlink lists PPTP and L2TP as generally not working well, and SSTP, OpenVPN and WireGuard as generally fine (checked Oct 5, 2026). Ask IT which type yours is.

Why does my Zoom or Teams call freeze for a few seconds on Starlink?

Most often a small obstruction in the dish’s view of the sky, or an upload elsewhere in the house filling the line. Check outages in the Starlink app’s Statistics page and run its obstruction check.

Why is Wi-Fi calling not working on Starlink?

Starlink says Wi-Fi Calling is sensitive to IP geolocation and that you should contact your carrier first (checked Oct 5, 2026). Check that your phone’s Wi-Fi Calling and emergency address are set, then call your carrier.

Sources

  1. What are CGNAT session limits and how do they affect my connection? (Starlink support), checked Oct 5, 2026
  2. Does Starlink work with VPNs? (Starlink support), checked Oct 5, 2026
  3. Will enterprise site-to-site VPN or SDWAN appliances work on Starlink? (Starlink support), checked Oct 5, 2026
  4. How can I monitor my Starlink's performance? (Starlink support), checked Oct 5, 2026
  5. Geoff Huston (APNIC), ISP Column: A Transport Protocol's View of Starlink (May 2024) (secondary), checked Oct 5, 2026
  6. Additional FAQs - Troubleshooting (VoIP and WiFi Calling Issues) (Starlink support), checked Oct 5, 2026
  7. Starlink Specifications (US, published 2026-03-11), checked Oct 5, 2026