Streaming and VoIP

Geo-blocked content, region mismatches, and calls that will not connect over WiFi.

Last updated Aug 18, 2026View as Markdown

Overview

Streaming and calling problems on Starlink usually come from one of two places: IP geolocation, which puts you somewhere you are not, or CGNAT, which limits inbound connections and concurrent sessions.

Streaming services

Match your symptom first, because the fixes differ.

Symptom Likely cause
The site or app will not load at all Connection or restriction problem
Specific content buffers while your speeds test fine Latency on the path to that service
Content shows as unavailable or “not in your region” IP geolocation mismatch

Steps

  1. Restart the hardware. Unplug the dish and router for 30 seconds, then plug them back in.

  2. Clear the browser cache, including cookies, and restart the browser.

  3. Check your geolocation. Visit whatismyipaddress.com or iplocation.net and note the country, region and IP. Starlink IPs sometimes route through data centres in other regions, so a mismatch here explains most geo-restriction problems. See Networking.

  4. Run a traceroute, particularly for slow or partial access.

    Platform Command
    Windows tracert netflix.com in Command Prompt
    macOS traceroute netflix.com in Terminal
    Linux traceroute netflix.com in a terminal
    iOS and Android An app such as Network Analyzer or PingTools

    Let it run 30 to 60 seconds and keep the whole output, asterisks and high latency numbers included.

If it is still broken, open a ticket with the service names, when it started, your IP location, and the full traceroute output.

If you also contact the streaming provider, note the name, email or phone number of whoever you speak to and any reference number, and pass that to Starlink.

VoIP and WiFi calling

Calls that will not connect, drop, have poor audio, or report “not supported”. WiFi calling in particular is sensitive to IP geolocation.

First, read CGNAT session limits. On Residential and Roam plans the 1,200-session cap causes exactly these symptoms, and no amount of device troubleshooting fixes it.

On the device

  1. Restart and toggle WiFi calling. Power off 30 seconds, then on. Toggle it off and on again in iOS: Settings → Phone → WiFi Calling, or Android: Phone app → Settings → Calls → WiFi Calling. Restart VoIP apps.
  2. Update the device and the app.
  3. Disable any VPN or third-party router temporarily.
  4. Test on another network. If it works on a mobile hotspot, the problem is on the Starlink side.

On the network

  1. Restart Starlink. Unplug the dish and router for 30 seconds, reconnect, wait 5 to 10 minutes and test.
  2. Check geolocation at whatismyipaddress.com or iplocation.net and note any mismatch.
  3. Run a ping test for 30 seconds: ping 8.8.8.8 on Windows, macOS or Linux, or PingTools on mobile. Note latency above 200 ms and any packet loss.

Getting help

Contact your carrier first. Give them the IP and geolocation, the symptoms and any error messages, and mention Starlink in case they need to whitelist something. Note their contact details and case reference.

If that does not resolve it, open a Starlink ticket with the carrier or VoIP service, affected devices, symptoms, a timeline, recent changes, the IP and geolocation, ping results and what you have already tried.