One of the most common Starlink questions we get is about IP addressing: what IP will my router get, is it public, and why can't I reach my equipment from outside? This article explains how Starlink hands out addresses and what it means for your setup. For how to physically connect Starlink to a router, see our guide "Using Starlink as a WAN on Your Peplink."
The default: CGNAT
Standard Starlink Residential service places you behind carrier-grade NAT (CGNAT). Your router's WAN typically receives a private address in the 100.64.0.0/10 range rather than a public IPv4 address. Starlink shares its public IPv4 pool across many customers, and that shared, carrier-side address is what the internet actually sees.
This is fine for normal, outbound use (browsing, streaming, video calls, VPN clients, cloud services). It only becomes a limitation when you need inbound access.
What CGNAT blocks
Because unsolicited inbound connections stop at Starlink's NAT, these will not work directly on a standard Residential plan:
- Port forwarding to a device behind your router.
- Hosting a server, NVR/camera, or service that outside users connect to.
- Some site-to-site VPNs that expect a reachable public IP.
- Reaching your router's admin page directly from the internet by IP.
IPv6
Starlink does provide IPv6, and IPv6 addresses are globally routable (subject to firewall rules). If your remote endpoint and your local devices both support IPv6, that can be a path for reachability that IPv4 CGNAT blocks. IPv4 inbound, however, remains behind CGNAT on Residential service.
Getting a public / routable IPv4
- SpeedFusion / SpeedFusion Connect (recommended on Peplink): the most reliable way around Starlink CGNAT. Your router builds a tunnel to a Peplink-hosted endpoint and exits from a reachable address, giving you stable remote access regardless of Starlink's addressing. See our SpeedFusion Connect articles.
- Starlink Priority / Business plans: these tiers can offer a public IP option, which removes the CGNAT limitation at the dish. Availability and terms are set by Starlink.
- Llama Networks Starlink plans with a public IP: we can provide Starlink service that includes a public IP, so you don't have to source or manage that yourself.
Public IP is not the same as a static IP
This is a common point of confusion. A public IP is reachable from the internet, but it can still change over time. A static IP is one that stays the same. Starlink does not offer static IP addresses on any plan — even where a public IP is available, it is dynamic. So if you need a fixed address (to allowlist it on a firewall, point DNS at it, or terminate a VPN), a Starlink public IP alone will not guarantee it.
Need a static IP? Llama Networks can host it
Llama Networks offers hosted services that deliver one or more static IP endpoints over Starlink, cellular, or SpeedFusion bonding. Your traffic exits from a fixed, reachable address that we manage, so you get a stable static IP regardless of what Starlink (or a cellular carrier) hands out underneath, and you can bond multiple links together for resilience. Reach out to sales[at]llamanetworks[dot]com to set this up.
How to check what you have
- In your router's status page, look at the Starlink WAN's assigned IP. A 100.64.x.x address indicates CGNAT.
- From a device behind the router, run a "what is my IP" lookup and compare. If the public IP differs from your WAN IP, you're behind CGNAT.
Quick summary
- Residential Starlink = CGNAT, private WAN IP, no direct inbound IPv4.
- Outbound everything works normally.
- For inbound/remote access, use SpeedFusion (Peplink), a Starlink plan with a public IP (we can provide one), or IPv6 where supported.
- Public IP does not mean static. Starlink has no static IP option; for a fixed address, use Llama Networks' hosted static IP service over Starlink, cellular, or SpeedFusion bonding.
Questions about Starlink addressing for your deployment, or which option fits your remote-access needs? Reach out to sales[at]llamanetworks[dot]com.