A static IP address for business broadband is one of those line items that sits quietly on a connectivity quote, costs a few pounds a month, and then turns out to matter enormously the day a firewall rule, a supplier’s allow-list or a remote-access VPN stops working because the address changed overnight. For many UK small and mid-sized businesses it is the difference between a connection that simply browses the web and one that can reliably host services, accept inbound connections and prove its identity to partners.
This guide explains what a static (fixed) IP address actually is, when your business genuinely needs one and when it does not, what UK providers typically charge for a single address or a /29 block, how the global shortage of IPv4 addresses is pushing prices up, and how to plan sensibly for IPv6 so you are not caught out when a supplier, cloud platform or regulator expects it. You will also find a readiness checklist, the mistakes we see most often during office moves and ISP switches, and a short anonymised case study from a multi-site professional services firm.
What is a static IP address? Definition and context
Every device that talks across the internet needs a public IP address so that traffic can find its way back. On most consumer and many entry-level business broadband packages, your router receives a dynamic public address from the provider’s pool using DHCP or PPP. That address can change when the router reboots, when the line resyncs after a fault, or simply when the provider re-balances its network. For browsing, email and Microsoft 365 that is irrelevant: outbound connections work regardless of which address you happen to hold.
A static IP address is a public IPv4 (and increasingly IPv6) address that your provider permanently assigns to your connection. It does not change unless you change provider or ask for it to be changed. Providers sell them individually (a “single static IP”, often written as a /32) or in small blocks — most commonly a /29, which is eight addresses of which five are usable once the network address, broadcast address and the provider’s gateway are accounted for. Leased lines frequently include a /29 or /30 as standard; FTTP and SoGEA business broadband usually treats it as a paid add-on.
The reason this matters more in 2026 than it did a decade ago is scarcity. RIPE NCC, the regional internet registry that serves the UK and Europe, allocated its last free block of IPv4 addresses in November 2019. Since then, providers that need more IPv4 space must buy it on the secondary transfer market or recover it from existing customers. That has driven three visible trends: more providers using carrier-grade NAT (CGNAT) on cheaper tiers, so customers share a public address; static IPs moving from “free on request” to a chargeable extra; and a slow but steady push towards IPv6, which has effectively unlimited address space. If you are reviewing your wider connectivity, our network capacity planning guide covers how addressing fits into a broader bandwidth and resilience plan.
Before buying a static IP, check whether your current connection is behind CGNAT. Log in to the router and compare the WAN address it shows with the address reported by a “what is my IP” site. If the router shows an address in the 100.64.0.0/10 range, or the two do not match, you are sharing a public address — and inbound services such as VPNs and CCTV remote viewing will not work reliably until you move to a dedicated or static address.
Static IP by the numbers — the UK 2026 reality check
Static addressing is a small topic with some surprisingly concrete numbers attached. The figures below are drawn from published RIPE NCC policy, typical UK business broadband and leased line price lists, and the patterns Cloudswitched sees across client connectivity reviews. Treat price ranges as indicative: every provider bundles differently, and the same address can be “free” on one tariff and £10 a month on another.
The headline takeaway is that IPv4 is now a priced, finite resource rather than a free utility. On the transfer market, a single IPv4 address has traded in the region of tens of US dollars over the past few years, and providers pass part of that cost on. Meanwhile IPv6 has quietly become mainstream: the large UK consumer networks have run dual-stack IPv6 for years, mobile networks use it heavily, and the major cloud platforms all support it. The practical question for a business is no longer “IPv4 or IPv6?” but “how many IPv4 addresses do we genuinely need, and is our IPv6 configuration safe and intentional?”
Do you actually need a static IP? Readiness scoring
Not every business needs a fixed address, and buying one “just in case” can create a false sense of security if it is then used to expose services that should sit behind a cloud gateway. The score cards below map common requirements against how strongly they depend on a static IP. A “high” badge means the requirement will be unreliable or impossible without one; “low” means a dynamic address, or a cloud-based alternative, is perfectly adequate.
If most of your requirements sit in the left-hand card, a static IP is a genuine operational dependency and should be treated as part of the connectivity specification, not an optional extra. If they sit mostly in the middle card, it is worth asking whether a cloud-delivered alternative — a zero-trust remote access service, a vendor’s cloud relay for CCTV, or SMTP authentication through Microsoft 365 — would be more secure than opening a port on a fixed address. And if your estate is fully cloud-based, a dynamic address on a well-chosen broadband service may be entirely sufficient.
Why UK businesses request static IPs — the common drivers
When Cloudswitched reviews connectivity for a new client, the reason a static IP is on the order is usually one of a handful of recurring drivers. The chart below shows the indicative share of static IP requirements we see by primary reason across typical SME connectivity projects. Many sites have more than one reason, so the bars show how often each appears as a stated requirement rather than adding up to 100%.
Two points stand out. First, VPNs and allow-lists dominate: a fixed address is most often about identity — letting another system recognise your office — rather than about hosting anything. Second, roughly a quarter of requests have no current technical driver at all; the address was simply carried over from a previous contract. That is worth auditing, because every static IP that is no longer needed is a small recurring cost and, if it still has ports forwarded to it, a potential attack surface.
The Conditional Access driver deserves particular attention. Many organisations use the office IP as a “trusted named location” in Microsoft Entra ID so that staff in the office are prompted for MFA less often. That works well, but it creates a hidden dependency: if the address changes during a broadband upgrade or office move and nobody updates the policy, users suddenly face MFA prompts everywhere, or worse, a policy that blocks sign-in from untrusted locations locks the whole office out. Our office downsizing and consolidation guide covers how to sequence these changes during a move.
Static IP cost breakdown — what UK providers charge
Pricing for static IPs varies widely depending on the type of connection, the provider’s own IPv4 holdings and how aggressively they bundle. The table below shows typical UK ranges in 2026 for the most common options. Always check whether a quoted price is per address or per block, whether there is a one-off set-up fee, and whether the addresses are tied to the line or can be ported to a new circuit at the same premises.
| Connection type | Typical static IP offer | Indicative monthly cost | Common set-up fee | Notes |
|---|---|---|---|---|
| Business FTTP / SoGEA broadband | Single static IPv4 (/32) | £0–£10 | £0–£25 | Often included on “pro” tiers; chargeable on entry-level tariffs |
| Business FTTP / SoGEA broadband | /29 block (5 usable) | £10–£25 | £0–£50 | Some providers require a justification form for larger blocks |
| Leased line (EFM / Ethernet) | /29 or /30 included | Usually included | Included | Larger blocks (/28) typically £15–£40 extra with RIPE justification |
| 4G / 5G business router | Static public IPv4 APN | £5–£20 | £0–£30 | Default mobile data is almost always CGNAT; static APN must be requested |
| IPv6 allocation | /48 or /56 prefix | Usually free | None | Offered by most business ISPs; check it is static rather than delegated dynamically |
The monthly cost of a static IP is rarely the deciding factor in choosing a provider, but the terms often are. A few clauses to look for: whether the provider will let you keep the same addresses if you upgrade from FTTC to FTTP or from broadband to a leased line with them; whether addresses are recovered immediately at contract end or held for a grace period; and whether reverse DNS (PTR records) can be set for you, which matters if any system sends email directly from the office. Our guide to choosing a business ISP and contract goes into the wider contract terms in detail.
It is also worth costing the hidden alternative. If a single static IP is needed only so that one supplier portal recognises you, a £6-a-month add-on is clearly cheaper than re-engineering the process. But if the static IP is there to expose a remote desktop server to the internet, the true cost includes the security risk, the monitoring and the patching discipline that exposure demands. In that case a cloud-based remote access service may cost more per month on paper and far less in practice.
The static IP and IPv6 rollout timeline — what a real project looks like
Adding or changing a static IP sounds like a five-minute job. In practice, the address is woven into firewall rules, VPN configurations, DNS records, third-party allow-lists and cloud identity policies. The timeline below reflects a typical change for a 30–80 person office moving to a new provider, including enabling IPv6 properly for the first time.
The single biggest time saver is starting the third-party notifications early. Banks and payment processors in particular can take ten working days or more to process an allow-list change, and some insist on the request coming from a named account holder. If the new address is only known on install day, you will either delay the cutover or accept a period where critical portals refuse connections from the office.
Static IP vs dynamic IP with cloud services — how the options compare
For most businesses the real decision is not “static or dynamic” in isolation, but whether to anchor security and connectivity to a fixed office address or to identity and cloud services that work wherever staff happen to be. Both approaches are valid, and many organisations use a blend. The comparison below summarises the trade-offs.
Dynamic IP + cloud-first
No fixed address; identity and cloud services do the work
Static IP + layered security
Fixed address used for identity, not for exposure
The highlighted option reflects what we most often recommend for established UK SMEs: buy a static IP where an external party or a VPN genuinely needs to recognise you, but do not use it as an excuse to publish internal services directly to the internet. Pair it with MFA everywhere, a modern firewall with intrusion prevention, and remote access delivered through a VPN or zero-trust broker. That combination keeps the operational benefits of a fixed address without making it a target.
For organisations running several offices, cloud-managed SD-WAN changes the calculation again. Platforms such as Cisco Meraki can build site-to-site tunnels automatically even when branches sit on dynamic addresses, using a cloud registry to find each peer. In that model, a static IP at head office and dynamic addresses at small branches is often a sensible, cost-efficient mix.
Static IP and IPv6 readiness gauge
Cloudswitched scores connectivity estates against a simple addressing readiness benchmark covering documentation, dependency mapping, IPv6 configuration, exposure and change process. The gauge below shows the typical score for a UK SME at the start of a connectivity review — before any remediation work.
A score around 40 usually means the static IP is known to one person, recorded in an old email from the ISP, and referenced in more places than anyone realises. IPv6 is either disabled entirely or, more worryingly, enabled by default on the router with no deliberate firewall policy. Neither is a crisis on its own, but both create risk during exactly the moments businesses tend to change things: office moves, provider switches and security certification.
Moving from the low 40s to the 75–85 range is rarely about buying anything. It is about writing down the addresses and their dependencies, deciding deliberately how IPv6 should behave, closing any port forwards that no longer have an owner, and adding the public address to your change process so that nobody upgrades a line without checking the register first.
Addressing benchmarks and KPIs
The progress rows below show how often each good-practice control is in place across typical UK SME estates at first review. They are a useful way to prioritise: the lowest bars are generally the cheapest and quickest wins.
Share of UK SMEs with each addressing control in place at first review
The weakest areas are consistently the third-party register and IPv6. The register is weak because allow-list requests are usually handled by whoever needed access at the time — finance for the bank, operations for a logistics portal — rather than by IT. IPv6 is weak because it often “just works” silently: modern routers, Windows and macOS will all prefer IPv6 when it is available, so traffic can be leaving the office on an address nobody has thought about.
That last point has a direct security implication. If your Conditional Access trusted location contains only the office IPv4 address, but staff devices reach Microsoft 365 over IPv6, the policy will treat office sign-ins as untrusted. Depending on how the policy is written, that either causes needless MFA prompts or, if someone has “fixed” it by loosening the rule, quietly weakens your security. Including the office IPv6 prefix in named locations is a small change with a meaningful effect.
How quickly is IPv6 arriving for UK businesses?
IPv6 adoption in the UK has moved from a niche concern to the default for large parts of the internet. The major consumer broadband networks and the mobile operators carry a substantial share of their traffic over IPv6, and the large platforms — Microsoft, Google, Meta, Cloudflare and the main CDNs — all serve content natively over it. Business-grade connections lag behind consumer ones, largely because firewalls and legacy line-of-business systems were configured for IPv4 only, but the gap is closing as providers include a prefix by default.
For a business, the practical consequence is twofold. First, IPv6 is not something you can indefinitely ignore: when you buy a new FTTP line or 5G router, it may well arrive with IPv6 enabled, and the router’s default behaviour will decide your security posture unless you decide it first. Second, IPv6 removes the scarcity that makes IPv4 static addresses valuable. A typical business IPv6 allocation is a /48 or /56 prefix — enough for thousands or millions of subnets — and it is normally static and free. Over time that will make “static IP” a much less meaningful upsell, but only once every supplier and partner you integrate with can accept IPv6 as well.
Until then, dual-stack — running IPv4 and IPv6 side by side — is the sensible norm. Keep your small, priced IPv4 allocation for allow-lists and legacy integrations, and adopt IPv6 deliberately for everything else, with firewall policy, monitoring and documentation that treat both protocols equally.
Real-world example — a multi-site firm’s static IP migration
A Leeds-headquartered accountancy practice with 62 staff across three offices engaged Cloudswitched ahead of a planned move from FTTC broadband to a leased line at head office and FTTP at its two smaller sites in Harrogate and York. The original brief was simply “keep the same static IP”. The existing provider could not port the address to the new circuit, so the practice needed a new /29 at head office and had to decide what to do at the branches.
The dependency audit took two days and turned up more than anyone expected. The head office address was allow-listed by two banks, an HMRC-recognised practice management platform, a payroll bureau and the building’s access-control supplier. It was also used as a Conditional Access trusted location and as the peer address for two IPsec VPN tunnels to the branches. Separately, the old router still had a port forward to a decommissioned remote desktop server, and IPv6 had been enabled on one branch router by default with no inbound filtering.
The new design gave head office a /29 on the leased line, with one address dedicated to the firewall’s outbound NAT and another reserved for a future hosted service. The branches moved to FTTP with dynamic addressing and joined head office over cloud-managed SD-WAN, which removed their need for static IPs entirely. Third parties received the new head office address three weeks before cutover and were asked to add rather than replace. On cutover day, every item on the register was tested from the office before the old line was ceased, and IPv6 was enabled on all three sites with a mirrored firewall policy and the new prefixes added to Conditional Access.
“We thought we were changing a broadband line. It turned out we were changing the way six outside organisations recognised us. Having the list in front of us before the engineer arrived is the only reason the move was a non-event for our clients.” — Practice Manager, Yorkshire accountancy firm
The branch static IP charges were dropped, the forgotten remote desktop exposure was closed, and the practice now has a one-page addressing register that sits alongside its Cyber Essentials evidence. Closing unmanaged inbound exposure is directly relevant to certification — see our Cyber Essentials guide to unsupported software and end-of-life risks for the related controls on firewalls and boundary devices.
Common static IP and IPv6 mistakes to avoid
Most addressing problems are not technical failures; they are planning gaps that surface at the worst possible moment. These are the mistakes we see most often when picking up an estate from another provider or helping a business through an office move.
- Assuming the static IP will move with you. Addresses usually belong to the provider and the specific circuit. Changing provider, technology (FTTC to FTTP, broadband to leased line) or even exchange can mean new addresses. Confirm in writing before signing.
- Not knowing who allow-lists you. If there is no register, the first sign of a change is a payment run that fails or a supplier portal that refuses to load. Build the register before you need it.
- Using the static IP to publish internal services. Remote desktop, NAS management pages and older VPN appliances exposed on a fixed address are actively scanned within minutes. Use a VPN or zero-trust access instead, and keep boundary devices patched.
- Leaving IPv6 on its router defaults. Some consumer-grade and older business routers enable IPv6 with permissive inbound rules. Either configure it deliberately with a firewall policy matching IPv4, or disable it intentionally and document the decision.
- Forgetting IPv6 in Conditional Access. Devices prefer IPv6 when available, so a trusted location that lists only the IPv4 address no longer recognises the office.
- Buying a /29 when one address will do. Larger blocks cost more and often require a RIPE justification. Size the allocation to real requirements, with one spare for growth.
- Ignoring CGNAT on backup connections. A 4G or 5G failover line almost always uses CGNAT by default, so VPNs and allow-listed services fail over to an address nobody recognises. Order a static APN or design failover around it.
- Ceasing the old line before testing. Without dual running, there is no fallback if a forgotten dependency breaks. Keep the old circuit live until every item on the register is tested.
The failover mistake catches many businesses out. If your primary leased line fails and traffic moves to a 4G backup on a shared CGNAT address, every system that relies on your static IP — bank portals, VPN tunnels, Conditional Access — will treat you as a stranger at exactly the moment you are already under pressure. Test failover against the dependency register, not just against “can we browse the web”. Our broadband failover and redundancy guide explains the design options.
Static IP and IPv6 checklist — the 12-point essentials
Use this checklist whenever you order a new connection, change provider, move office or prepare for a Cyber Essentials assessment. It is deliberately short enough to run in an afternoon.
- Confirm whether each site’s connection is on a dedicated public address or behind CGNAT.
- Record every public IPv4 address and IPv6 prefix, per site and per circuit, in your network documentation.
- Build a register of every third party, cloud service and internal policy that references those addresses.
- Decide, per site, whether a static IP is a genuine requirement or a carry-over that can be dropped.
- Size the allocation — single address or /29 — to actual needs, with one spare for growth.
- Check contract terms for address portability on upgrades and the grace period at contract end.
- Close any port forwards without a named owner and a documented business reason.
- Ensure no remote desktop, NAS admin page or unpatched VPN appliance is exposed directly to the internet.
- Configure IPv6 deliberately: enabled with a firewall policy mirroring IPv4, or disabled with the decision documented.
- Add office IPv6 prefixes alongside IPv4 addresses in Microsoft Entra ID named locations and other allow-lists.
- Order a static APN, or design around CGNAT, for any 4G or 5G failover connection.
- Add “public address change” as a trigger in your change process, with the register as a mandatory check.
Cyber Essentials requires that boundary firewalls block unauthenticated inbound connections by default and that any permitted inbound rule is approved and documented with a business need. A clear addressing register and a reviewed list of port forwards make that evidence straightforward to produce — and they apply equally to IPv6 if it is enabled.
Static IP at a glance — key facts summary
| Topic | Key fact |
|---|---|
| What it is | A public IP address permanently assigned to your connection by the provider |
| Typical block sizes | Single address (/32) or /29 with five usable addresses |
| Typical broadband cost | £0–£10 a month for one address; £10–£25 for a /29 |
| Leased lines | Usually include a /29 or /30 as standard |
| IPv4 scarcity | RIPE NCC free pool exhausted in November 2019; addresses now traded |
| CGNAT | Shared public address used on cheaper tiers and most mobile data; blocks inbound services |
| IPv6 allocation | Typically a static /48 or /56 prefix, usually free |
| IPv6 adoption | Roughly half of UK traffic to major platforms; dual-stack is the norm |
| Main reasons to buy | VPNs, supplier allow-lists, Conditional Access, on-premises VoIP |
| Main risk | Using the fixed address to expose internal services directly |
| Portability | Addresses usually stay with the provider and circuit, not the customer |
| Failover gotcha | 4G/5G backup lines use CGNAT unless a static APN is ordered |
| Change lead time | Allow two to three weeks for bank and supplier allow-list updates |
How Cloudswitched handles static IPs and IPv6
Cloudswitched treats public addressing as part of the connectivity design rather than a tick-box on an order form. That means auditing what depends on your current addresses, specifying the right allocation for each site, coordinating third-party allow-list changes ahead of install day, configuring IPv6 deliberately on your firewalls, and leaving you with a documented register that survives the next provider change or office move.
Planning a new line or switching provider?
Our connectivity team can audit your current addressing, size static IP and IPv6 requirements, and manage the cutover so suppliers, VPNs and security policies keep working.
Talk to us about Business ConnectivityFrequently Asked Questions
Does my business really need a static IP address?
Only if something depends on recognising your office address. The common cases are site-to-site VPNs, supplier or bank portals that allow-list your IP, Microsoft Entra ID Conditional Access trusted locations, on-premises phone systems with IP-registered SIP trunks, and any inbound service you host yourself. If your estate is fully cloud-based — Microsoft 365, cloud telephony, SaaS line-of-business apps — a dynamic address on a good business broadband line is usually perfectly adequate, and you can avoid the extra monthly charge and the temptation to expose services directly.
How much does a static IP cost in the UK?
On business FTTP or SoGEA broadband a single static IPv4 address typically costs between nothing and around £10 a month, with some providers charging a small one-off set-up fee. A /29 block with five usable addresses is commonly £10–£25 a month. Leased lines usually include a /29 or /30 in the price. Static addresses on 4G or 5G business routers require a static APN and typically cost £5–£20 a month. Prices have generally risen since the European IPv4 pool ran out in 2019.
Can I keep my static IP if I change broadband provider?
Usually not. Static IPv4 addresses belong to the provider’s allocation and are tied to their network, so switching provider almost always means new addresses. Even staying with the same provider, upgrading from FTTC to FTTP or from broadband to a leased line can change the address. The only common exception is a business that holds its own provider-independent address space and announces it via BGP, which is uncommon for SMEs. Plan for a change and start notifying third parties early.
What is CGNAT and why does it matter?
Carrier-grade NAT lets a provider share one public IPv4 address between many customers. It is common on cheaper broadband tiers and almost universal on mobile data. Outbound browsing and cloud apps work normally, but anything that needs to reach your office from the internet — a VPN, remote CCTV viewing, a hosted service — will not work reliably, and allow-lists cannot identify you because other customers share the same address. If your router’s WAN address is in the 100.64.0.0/10 range, you are behind CGNAT.
Is a static IP a security risk?
The address itself is not a risk, but what you expose on it can be. Attackers continuously scan the whole IPv4 internet, so a fixed address with an open remote desktop port or an unpatched VPN appliance will be found quickly. Used purely for outbound identity — VPN peering and allow-lists — with inbound connections blocked by default, a static IP adds very little risk. Keep boundary devices patched, enforce MFA and review port forwards regularly.
Should my business enable IPv6?
For most businesses, yes — deliberately. Much of the internet now runs over IPv6, the major cloud platforms support it natively, and new lines increasingly arrive with it enabled. The key is to configure it intentionally: a firewall policy that allows outbound and blocks unsolicited inbound traffic, equivalent rules for any published services, monitoring that covers both protocols, and Conditional Access locations that include your IPv6 prefix. If a legacy system cannot cope, disabling IPv6 temporarily is acceptable, provided the decision is documented and revisited.
What is a /29 block and how many addresses do I get?
A /29 is a block of eight consecutive IPv4 addresses. One is the network address, one is the broadcast address and one is normally used by the provider’s gateway, leaving five usable addresses for your equipment. Businesses use the extras to separate outbound traffic for different purposes, to host a service on its own address, or to give guest Wi-Fi a different public identity from staff traffic. If you only need one address for VPNs and allow-lists, a single static IP is usually sufficient.
Do I need a static IP for Microsoft 365 or Teams Phone?
No. Microsoft 365, Teams and Teams Phone are designed to work from any internet connection, including dynamic and CGNAT addresses. A static IP becomes useful only if you want to use the office address as a trusted named location in Conditional Access policies, or if you run a direct-routing session border controller on site. Even then, remember to add the office IPv6 prefix as well as the IPv4 address, otherwise sign-ins that travel over IPv6 will not be recognised as coming from the office.
How does a static IP affect 4G or 5G backup connections?
Mobile data connections almost always sit behind CGNAT by default, so when your primary line fails and traffic moves to a 4G or 5G router, your public address changes to a shared one. VPN tunnels, bank allow-lists and trusted-location policies can all fail at that point. Options include ordering a static APN from the mobile provider, using cloud-managed SD-WAN that can rebuild tunnels from dynamic addresses, and asking suppliers to allow-list the backup address too.
How long does it take to change a static IP safely?
The technical change takes minutes, but a safe migration typically takes three to six weeks end to end. Most of that time is the dependency audit and the third-party notifications: banks, payment providers and some software vendors can take ten working days or more to update allow-lists. Running the old and new circuits in parallel for a short period, and testing every item on your dependency register before ceasing the old line, is the most reliable way to avoid disruption.
Related reading
Static addressing touches capacity planning, office moves, security certification and wider IT strategy. These guides cover the adjacent decisions:
- Network Capacity Planning: A UK Business Guide to Forecasting Growth Before Your Network Becomes the Bottleneck
- Office Downsizing and Consolidation: Moving to a Smaller Office Without Losing IT Capability
- Cyber Essentials and Unsupported Software - The UK Guide to End-of-Life Devices
- Virtual CIO Onboarding: What the First 90 Days Should Actually Look Like
- Business Broadband Outages: Building Failover and Redundancy Into Your Internet Connection
Get your business connectivity specified properly
From single-site FTTP to multi-site leased lines with SD-WAN, Cloudswitched designs connectivity around what your business actually depends on — including the addresses everyone forgets until they change.
Explore Cloudswitched Connectivity








