Can You Get a Fixed IP Address with Starlink?
A business guide to Starlink fixed IP options, secure remote access and resilient integration across low Earth orbit (LEO) satellite connectivity
Starlink’s higher-tier Priority and other eligible commercial service plans can offer an optional publicly routable IPv4 address, whereas lower-cost Residential plans use carrier-grade network address translation (CGNAT) by default and do not include that option. Starlink still assigns the public IPv4 address dynamically, so it can change. At APC Communications Solutions, we can provide a managed static public IPv4 address for businesses that need one consistent address, independent of Starlink’s own public IP option.
Starlink is a low Earth orbit (LEO) satellite service. Other LEO platforms, including Eutelsat OneWeb and Amazon Leo (formerly Project Kuiper), broaden the satellite connectivity options available to organisations, but the addressing detail in this guide is specific to Starlink and should not be assumed to apply to every LEO service.
Routine browsing and cloud applications usually work without a fixed IP. A Starlink fixed IP becomes relevant when someone outside the site or an automated system must reach equipment at the site, or when a supplier accepts traffic only from an approved source address. In those cases, the internet connection can remain available while the required application cannot connect.
We can integrate Starlink into a fully managed connectivity solution. Where required, our design can include a MultiConnect+ router, a single static public IPv4 address, secure, encrypted site-to-site connectivity and additional paths using 4G, 5G, fibre or microwave internet. Within a managed MultiConnect+ configuration, we monitor connection performance and can redirect traffic across the available paths when conditions change.
Does Starlink provide a static IP address?
Starlink’s public IPv4 option provides a publicly routable address rather than a guaranteed static IPv4 address. Eligible Priority and other qualifying commercial plans can use an optional publicly routable IPv4 policy, while lower-cost Residential plans remain behind CGNAT by default. The public IPv4 address is dynamically assigned and can change.
Starlink assigns the public IPv4 address through Dynamic Host Configuration Protocol (DHCP). Its reservation system may retain the address for long periods and through reboots, but relocation or software changes can result in a different address. That makes the option more stable than CGNAT for inbound access, but it should not be treated as equivalent to a managed static public IP.
Key distinction: Starlink’s optional public IPv4 can make a site directly reachable, but it is available only on eligible higher-tier plans and the address may change. Our managed static public IPv4 gives approved systems one consistent address across the managed solution.
Because APC provides the fixed IP at the managed network layer, the service does not depend on Starlink’s own public IPv4 feature. This means we can provide a consistent fixed IP with suitable lower-cost Starlink packages that do not offer a public IPv4 option as standard, subject to the plan being appropriate and permitted for the deployment. It also gives us greater flexibility over routing, security and consistent addressing across backup connections.
When does a business need a Starlink fixed IP?
A Starlink fixed IP matters when an address change interrupts a business process. Typical requirements include remote monitoring, secure network access, supplier allowlisting and consistent addressing during failover.
What should international deployments consider?
At some international sites, organisations may use satellite connectivity because local terrestrial routing, filtering or access controls affect approved business systems. A managed fixed IP and independent satellite path can form part of that connectivity design, but the deployment must be assessed against local law, licensing, service availability, contractual terms and the customer’s security policy. We can design the routing and fixed-IP architecture for legitimate business use, but the service should not be positioned as a means to evade lawful restrictions.
Can you access CCTV remotely over Starlink?
Yes, depending on how the CCTV platform connects. Some systems establish outbound connections to a vendor’s cloud platform and may work through CGNAT. Direct access to a network video recorder or private monitoring link may require a public IP or managed private route. An allowlisted platform may also require a consistent source address.
We can provide secure, encrypted site-to-site connectivity over Starlink. This gives authorised teams a controlled access path without exposing traffic directly over the public internet.
Can Starlink support site-to-site VPNs and remote support?
Starlink supports VPNs that use TCP or UDP, provided the VPN supports Network Address Translation (NAT) traversal. An outbound tunnel may work through CGNAT. A design that expects an external peer to connect directly into the site may require Starlink’s public IP option or a managed static public IP.
Where the VPN design needs a stable peer address, we can provide a single static public IPv4 address across the managed solution. Remote teams can then use that address instead of tracking Starlink’s current public IP.
Can Starlink provide a consistent IP for firewall allowlisting?
Many cloud platforms and suppliers accept connections only from approved source IP addresses. If Starlink changes its address, the supplier may reject legitimate traffic until someone updates the rule.
A managed Starlink fixed IP gives authorised traffic a consistent external address. It can reduce unplanned allowlist changes and the risk of an address change interrupting the service.
Can the same fixed IP remain during internet failover?
It can, when the design provides one static public IP across the available connections. A basic switch from fibre to Starlink may restore internet access but change the site’s public address. That change can disrupt allowlists, VPNs or inbound access.
We can combine Starlink with 4G, 5G, fibre or fixed wireless access through MultiConnect+ and provide a single static public IP across those connections. Test each application during commissioning because failover may interrupt active sessions, depending on the routing design and application behaviour.
Planning to use Starlink for CCTV, VPN access or business internet backup?
Confirm the addressing, router and failover design before you order equipment, configure supplier allowlists or commission the site. Discuss your Starlink fixed-IP requirements with us.
Do you actually need a Starlink fixed IP?
Many Starlink deployments work without a fixed IP. General browsing, cloud software and applications that initiate outbound connections will often work through the default configuration. Review the design when external users must connect into the site, a supplier requires an allowlisted address or the same public identity must continue across failover.
| Business requirement | Likely approach |
| Web access, cloud software and video calls | The standard Starlink configuration may be sufficient. |
| CCTV that connects through a vendor cloud platform | The default configuration may work. Confirm the platform behaviour and security policy. |
| Inbound access where an occasional address change is acceptable | Starlink’s optional public IPv4 on an eligible Priority or commercial plan may be appropriate when an occasional address change is acceptable. |
| Supplier allowlisting or a stable VPN peer | Use a managed static public IP that does not depend on Starlink’s current address. |
| Direct access to CCTV or operational equipment | Use a managed VPN or private route rather than exposing equipment directly. |
| Consistent addressing across internet failover | Use a managed hybrid design with one static public IP across the available connections. |
How do we provide a fixed IP over Starlink?
We design and manage Starlink for business use. For a Starlink fixed IP requirement, our design must account for the application’s connection behaviour and the operational effect of losing access.
1. Define what must remain accessible
Identify who needs access, which direction the traffic flows and whether the application expects a fixed source or destination IP. Account for VPN compatibility, cloud-relay behaviour, security policy and acceptable interruption before selecting the Starlink plan and router.
2. Add managed routing and a fixed public IP
For a Starlink fixed IP deployment, we can deliver a single static public IPv4 address across a managed Starlink solution and provide secure, encrypted site-to-site connectivity where required. Our design can support fixed firewall policies and secure VPN access. It can also give inbound services a consistent destination for external systems.
3. Add an independent connection where the site needs resilience
For a business-critical site, we can combine Starlink with fixed wireless access, mobile connectivity or fibre. MultiConnect+ uses software-defined wide area networking (SD-WAN) to combine and manage multiple connections. When the design includes a single static public IP, external systems can continue to use the same address across those connection types.
4. Test, monitor and support the complete service
Before handover, test the service from outside the site and force traffic onto the backup path where the design includes resilience. Check VPN recovery and remote access to the actual application, then confirm the firewall allowlists. A speed test alone does not prove that these services will work during failover.
We continuously monitor performance within our managed Starlink and MultiConnect+ services and can redirect traffic when a connection underperforms. MultiConnect+ also offers an optional 24/7 UK-based support desk.
Can you use port forwarding with Starlink?
Conventional IPv4 port forwarding does not work through Starlink’s default CGNAT policy. Starlink requires a public IP assignment and a third-party router that supports port forwarding.
Direct internet exposure can increase the security risk for CCTV and other operational equipment, including servers. A managed VPN or private route can provide controlled access instead, depending on the application and security policy.
What is the difference between a public IP, static IP and CGNAT?
These terms describe different capabilities:
| Address type | What it means | Business implication |
| Private or CGNAT address | Starlink shares public IPv4 capacity across customers and blocks unsolicited inbound IPv4 traffic. | Works for normal outbound use. Conventional inbound IPv4 access and port forwarding do not work. |
| Public dynamic IP | The site can accept inbound internet traffic, but Starlink may change the address. | Can support inbound access when the business can manage an occasional change. |
| Static or managed fixed IP | The network presents one consistent external address. | Supports stable VPN peers, firewall allowlisting and controlled remote access. |
Does dynamic DNS bypass CGNAT on Starlink?
No. Dynamic DNS updates a hostname when a public address changes, but it cannot bypass CGNAT. It also cannot satisfy a supplier that requires a fixed numeric address for allowlisting.
Can IPv6 replace a fixed IPv4 address?
Starlink supports native IPv6 and delegates IPv6 addressing to compatible routers. IPv6 may provide end-to-end addressing when the application and firewall support it throughout the connection. Many business integrations still rely on IPv4, so confirm compatibility before selecting IPv6 as the access method.
Need a Managed Starlink Fixed IP Solution?
Review your Starlink plan, fixed-IP requirement, router and failover design with our connectivity team. We can determine whether the application needs Starlink’s optional public IPv4 policy or a managed static public IPv4 address, then recommend a configuration based on how users and systems must reach the site. Where resilience forms part of the requirement, we can integrate Starlink with MultiConnect+ and additional paths using 4G, 5G, fibre or microwave internet. Discuss a managed Starlink solution before the site becomes dependent on the connection, so the addressing and routing design supports the services your business needs to keep accessible.
Frequently asked questions
Do all Starlink business plans include a public IP?
No. Starlink’s public IPv4 policy is limited to eligible Priority or other qualifying commercial plans; lower-cost Residential plans use CGNAT by default and do not include the option. Starlink’s public IPv4 is also dynamically assigned rather than guaranteed static. Our managed fixed IP can provide a consistent address independently of that Starlink feature, subject to the underlying plan being suitable for the deployment.
Can you add a Starlink fixed IP to an existing installation?
Potentially. We can add a managed static public IPv4 address to an existing Starlink deployment without relying on Starlink’s own public IPv4 option, subject to the current plan, equipment, routing design and application requirements.