Donate

Port Forwarding Not Working? CGNAT Is Usually Why (Fixes)

If port forwarding fails no matter what you configure, carrier-grade NAT at your ISP is likely blocking inbound traffic before it reaches your router. Confirm it in two minutes, then fix it with public IPv4, IPv6, or a tunnel.

CGNAT port forwarding is not working because your ISP, not your router, controls the public IPv4 edge. Carrier-grade NAT breaks inbound reachability before traffic ever reaches your local forwarding rule, so the router rule is correct but the packet never arrives. The four working fixes are: ask the ISP for a public IPv4 address, switch the service to native IPv6, use a reverse tunnel like Cloudflare Tunnel or Tailscale, or move to a different ISP plan that does not use CGNAT. This guide shows how to confirm CGNAT in under a minute, then pick the right fix for your use case.

Lily opening a blocked router path from a home network through a carrier gateway to the public internet

Confirm it first: the interactive CGNAT Test auto-detects your public IP and ASN, then classifies your router WAN IP so you know whether CGNAT is actually the reason port forwarding fails.

Fast answer: why CGNAT prevents inbound connections

Carrier-grade NAT prevents inbound connections because the ISP, not your home router, controls the public IPv4 edge. Your router port forwarding rule can only forward traffic that reaches the router. Under CGNAT, the incoming packet stops at the ISP translation layer first, so normal customer-side port forwarding is not possible unless the ISP gives you a public IPv4 address, native IPv6 reachability, or a special inbound forwarding service.

The exact error messages that mean CGNAT or upstream NAT

Routers, mesh systems, and remote-access apps report this condition with slightly different wording. If you searched for one of these messages word for word, they all describe the same situation: a NAT layer you do not control sits between your router and the internet.

  • "Upstream NAT detected. Port forwarding and direct remote access may be unavailable." Your device compared its WAN address with its real public IP and found a translation layer above it. That layer is either ISP carrier-grade NAT or a second router in front of yours.
  • "Your ISP is using CGNAT. Port forwarding and direct remote access are unavailable." The app detected a WAN address inside 100.64.0.0/10 or a WAN/public mismatch and concluded the ISP shares one public IPv4 address across many subscribers. Your forwarding rule is fine; the inbound packet never reaches it.
  • "Carrier-grade NAT prevents inbound connections. Port forwarding is not possible." Same diagnosis, stated at the protocol level: unsolicited inbound TCP/UDP stops at the ISP translation pool, so no customer-side configuration can make the port reachable over IPv4.
  • "Double NAT detected." This one is often local and fixable: an ISP modem/router and your own router are both translating. Bridge mode on one of them usually resolves it without calling the ISP. How to tell the two apart is covered below.

Whichever wording you saw, the next step is identical: run the CGNAT test to classify your WAN address against the ranges in the CGNAT IP address range guide, then pick a fix from the list below.

Why port forwarding fails under CGNAT

Normal home port forwarding assumes your router controls the public internet-facing address for the connection. An outside client reaches that public IP, the router receives the packet, and your forwarding rule sends it to the correct internal device and port. CGNAT breaks that model because the ISP adds another NAT layer upstream of your router.

In other words, the internet is not talking directly to your router's public address because your router may not have one in the usual sense. The ISP is translating many subscribers behind a shared address pool. Your local rule still exists, but the traffic never arrives there from the outside world unless the ISP also forwards it, which consumer CGNAT normally does not.

How to tell whether CGNAT is the problem

  1. Check the router's WAN or internet-facing IP in the admin interface.
  2. Compare it with the public IP shown on the homepage lookup.
  3. If they do not match, there is an upstream translation layer between your router and the public internet.
  4. If the WAN IP is inside 100.64.0.0/10, CGNAT is strongly indicated.

That single comparison answers a huge amount. If the router thinks its WAN IP is 100.72.x.x but the public checker shows a totally different address, then your router is not the public edge. Any inbound forwarding expectation needs to account for that.

To see the symptom directly, run the open port checker against the port you forwarded. Under CGNAT it will report the port as filtered no matter how the router is configured, because the connection never reaches your router in the first place.

Useful commands while troubleshooting

On a local machine, these checks help separate routing from service issues:

ipconfig
netstat -ano
tracert 1.1.1.1

ipconfig helps confirm the internal destination IP and gateway. netstat -ano helps verify whether your service is actually listening on the expected port. Traceroute is not a direct CGNAT detector, but it helps you understand whether the path is behaving strangely or going through additional layers.

The key point is this: before blaming CGNAT alone, confirm the local service is running and listening on the intended port and protocol. A closed local port and a CGNAT problem can look similar from the outside.

Other reasons port forwarding can fail even without CGNAT

  • Double NAT. An ISP modem/router and your own router may both be translating traffic.
  • Wrong destination IP. DHCP may have changed the local device address since you created the rule.
  • Host firewall blocks the traffic. The router can forward correctly while the server itself still rejects the connection.
  • Wrong protocol. Forwarding TCP when the app expects UDP, or vice versa, is common.
  • ISP-level port filtering. Some providers block inbound traffic on specific ports regardless of your local rule.
  • The service is not bound to the right interface. Applications can listen only on localhost or the wrong internal IP.

Where this matters in practice

  • Game hosting. Friends cannot join a self-hosted game server even though the local firewall and router rule look correct. For Minecraft Java, the official server instructions identify port 25565. Confirm the edition and server configuration before choosing a tunnel; a web-only proxy is not a universal game relay. Joining somebody else's server and publishing your own server are different reachability problems.
  • Remote desktop and SSH. Home-lab access fails from outside because the line is not directly reachable.
  • Self-hosted dashboards and media servers. Services work internally but not from mobile data or another outside network. For Plex, the Remote Access troubleshooting guide uses TCP 32400 on the server. An external mapped port may differ and must match Plex's manual public-port setting. Test from outside your home network after establishing a reachable public endpoint; Plex account and subscription requirements are a separate check.
  • Cameras and NVRs. Legacy "port forward to view remotely" advice often breaks completely under CGNAT.
  • Home automation. Webhooks or outside callbacks cannot reach the internal service directly.
  • Peer-to-peer applications. NAT traversal can degrade or fail when multiple translation layers exist.

Practical fixes that actually help

  • Ask the ISP for a real public IPv4 address. Some providers offer this on request or on a business/static-IP plan.
  • Use bridge mode if double NAT is also present. This will not solve CGNAT by itself, but it removes one local complication.
  • Use native IPv6 if the service and clients support it. IPv6 often avoids the same inbound IPv4 constraints.
  • Use an overlay VPN or reverse tunnel. For remote access, this is often more practical than fighting ISP policy.
  • Use a cloud relay or public edge service. Some apps are better published through a managed reverse proxy than through raw home forwarding.
  • Use a VPN that offers port forwarding. Your device opens the tunnel outbound, which CGNAT permits, and the provider maps a reachable port on its own public IP back to you. The port number is usually assigned rather than chosen, and the address belongs to the VPN rather than to you, but for hosting a game server, seeding, or reaching a home service it is the closest equivalent to real port forwarding that does not depend on the ISP. Few providers offer it, and the VPN port forwarding table below shows which ones and on what terms.

Testing from inside the house can give a false sense of success

One of the most common debugging mistakes is testing the forwarded service from the same LAN and assuming that result reflects the public internet. Some routers support NAT loopback or hairpin NAT, which lets internal clients reach the service using the public address even though the outside world still cannot. Other routers fail that exact test even when the public path works, which is the opposite kind of confusion.

The reliable test is from a truly external network such as mobile data, a different household connection, or a trusted outside monitoring path. That is the only way to know whether the internet can actually reach the forwarded service.

How to talk to ISP support without wasting time

Support calls go better when you bring specific facts. The useful evidence is: the router WAN IP, the public IP seen on the web, the fact that they differ, and whether the WAN IP is in the CGNAT range. Also note whether you need inbound TCP, UDP, or both.

That moves the conversation away from "my router is broken" and toward the real question: does this line have a customer-usable public IP or not? Once support confirms the connection sits behind CGNAT, you can ask whether the provider offers public IPv4, static IP, bridge mode, business plans, or IPv6 alternatives.

Reverse tunnels and overlay VPNs are often the practical answer

If the ISP will not provide a public IPv4 address, the best solution is often to stop thinking in terms of classic home port forwarding. Overlay VPNs, reverse tunnels, and cloud-published edges let the internal device initiate the outbound connection first and then maintain a reachable path through that established session.

This is why many modern self-hosting guides recommend Tailscale, Cloudflare Tunnel, WireGuard-based relays, or managed reverse proxies instead of telling users to fight consumer CGNAT indefinitely. The goal is reachability, not loyalty to one old troubleshooting model.

Why CGNAT and double NAT are easy to confuse

Both create reachability problems, but they are not the same. Double NAT means you have two local translation layers you may still control or partly control, such as an ISP gateway plus your own router. CGNAT means the ISP is performing translation upstream in infrastructure you do not control. You can often fix double NAT locally; you usually cannot remove CGNAT without ISP help or a different connectivity model.

Which ISPs use CGNAT (real examples by region)

CGNAT deployment varies by ISP, plan tier, and country. The pattern below is what subscribers actually report, but check your own router WAN IP before assuming it applies to your line.

  • Singapore: Singtel mobile and Simba (TPG) home broadband both commonly issue CGNAT addresses in the 100.64.0.0/10 range. StarHub residential plans usually give a public IPv4 by default.
  • United States: T-Mobile Home Internet, Verizon 5G Home, and most mobile carrier plans use CGNAT. Comcast/Xfinity and AT&T fiber residential plans typically give public IPv4. Cox and Spectrum vary by market.
  • United Kingdom: Three UK mobile and BT mobile use CGNAT. Sky Broadband, Virgin Media, and BT fixed-line broadband generally provide public IPv4 on request or by default.
  • India: Reliance Jio and Airtel mobile broadband almost always use CGNAT. ACT Fibernet and Excitel fixed-line plans usually give public IPv4.
  • Europe: Vodafone Italy mobile, Orange mobile in most EU countries, and many fixed-wireless ISPs use CGNAT. Most incumbent fibre operators (Deutsche Telekom, Telefonica, KPN, Orange fibre) provide public IPv4 by default.
  • Mobile broadband globally: If your connection is delivered over 4G/5G with a USB modem, MiFi, or phone tether, assume CGNAT unless the carrier explicitly sells a static-IP add-on.

If your Starlink connection uses shared IPv4 behind CGNAT, a port rule on your home router cannot make that upstream shared address accept incoming traffic for you. Starlink's published technical transparency table lists CGNAT for Residential plans, an optional public IPv4 address on Local Priority and Global Priority, and IPv6 availability. Check your current plan and region with Starlink before paying for a different service; a plan name alone is not proof that public addressing is enabled on your connection.

Start by comparing your router WAN address with the public address on our CGNAT checker. If public IPv4 is available, confirm inbound restrictions, then configure the router and host firewall. Otherwise consider IPv6 when the server and outside clients both support it, a private overlay for your own devices, or an outbound tunnel with the TCP/UDP support your service needs. A VPN only supplies an inbound endpoint when its specific plan and setup support forwarding. Changing DDNS, enabling UPnP, or removing one layer of home-router NAT does not remove the carrier's NAT.

How CGNAT translates port numbers

CGNAT does not give every subscriber the entire 65,535-port range of the shared public IPv4 address. Instead, the ISP allocates a port pool per subscriber, typically 256 to 4,096 ports out of the public-side IPv4 address. Outbound connections work because the subscriber initiates them and the ISP records the source-port mapping for the return traffic.

Inbound port forwarding fails because there is no static rule that says "port 25565 on the public IP belongs to subscriber X". Even if the ISP wanted to expose port 25565 to your line, dozens of other subscribers behind the same public IPv4 also want port 25565 for their own Minecraft servers. The conflict cannot be resolved with a single shared address, which is why CGNAT operators do not offer port-mapping on a per-subscriber basis at consumer scale.

A small minority of ISPs run "port-restricted CGNAT" deployments where each subscriber is given a fixed, advertised port range that the customer can use for inbound traffic on a specific port. This is rare and only useful for self-hosted services that can bind to a non-standard port.

Reverse tunnel comparison: Cloudflare Tunnel vs Tailscale vs WireGuard relay

The three most common ways to bypass CGNAT for self-hosting all share the same model - the internal device opens an outbound connection that the outside world rides on the way back in - but they trade off differently:

  • Cloudflare Tunnel (cloudflared): publishes a local HTTP/HTTPS service through Cloudflare's edge with a public hostname. Free for personal use. Best for web apps, dashboards, and APIs. Not designed for arbitrary TCP/UDP (game servers, RDP, SSH require additional Cloudflare Access setup).
  • Tailscale (or Tailscale Funnel): mesh VPN that lets your trusted devices reach the CGNAT-bound machine over a private overlay. Tailscale Funnel exposes a service publicly. Free for personal use up to 3 users / 100 devices. Best for SSH, file shares, RDP, and home-lab access where the user controls both endpoints.
  • WireGuard reverse tunnel via a $5 VPS: rent a cheap VPS with a public IP, install WireGuard on the VPS and the home device, and forward inbound traffic from the VPS to the home device through the tunnel. Maximum control, no third-party dependency, works for arbitrary TCP/UDP. Requires manual setup and the VPS subscription.

For most users behind CGNAT, Cloudflare Tunnel for web services and Tailscale for personal-device access cover the majority of cases. The WireGuard-on-VPS path is the right choice when you need protocol flexibility or vendor independence.

Which CGNAT fix fits what you are hosting

Each workaround above solves a different problem, and none of them solves all of them. The question that decides it is who has to connect: only you and your own devices, anyone on the web, or other players and peers who start the connection. Find the row that matches what you run, and start with the fix in the middle column.

Which CGNAT workaround to try first for each use case
What you needFix to try firstWhat to know
Reach your own NAS, SSH, RDP, or Home AssistantAn overlay network such as Tailscale or ZeroTierNo port is opened to the internet, but every device that connects needs the app
Publish a website, dashboard, or APICloudflare Tunnel or Tailscale FunnelBuilt for HTTP and HTTPS; raw TCP and UDP need extra setup or another route
Host a game server that friends join by addressA public IPv4 address from the ISP, or a VPS relayA VPN-forwarded port works only if the game server lets you set a custom port
Seed torrents or accept P2P connectionsA VPN with port forwardingThe port is usually assigned, so enter it in your client and check it again after reconnecting
Stream Plex or Jellyfin outside the houseAn overlay network for your own devices; public IPv4 or a VPS relay for anyone elseA relay carries every stream through the VPS, so check its monthly transfer allowance
View cameras or an NVR remotelyThe camera maker's app, or an overlay networkAvoid exposing camera web interfaces to the internet at all
Serve visitors who also have IPv6Publish the service over native IPv6IPv4-only visitors cannot reach it; allow the port in the router's IPv6 firewall
Fix strict NAT on a PS5 or XboxA public IPv4 address from the ISPConsoles cannot run tunnel or VPN apps; see the gaming section below
Run several of these at oncePublic or static IPv4 from the ISP, or a plan without CGNATThe only fix that restores normal port forwarding for every app; often a paid add-on

Two patterns run through the table. If only your own devices connect, you do not need an open port at all, and an overlay network is the safer choice because nothing is exposed to strangers. If other people have to reach you, as with a public game server or torrent seeding, you need an address the internet can reach: a public IPv4 address from the ISP, IPv6, a relay you rent, or a VPN that forwards a port to you.

Which VPNs support port forwarding (checked October 2026)

A VPN gets you past CGNAT for inbound traffic only if the provider opens a port on its own public IP and sends what arrives there back through your tunnel. Many of the biggest consumer VPNs do not offer that, and the ones that do attach conditions. This is what each provider's own documentation said when we checked in October 2026:

VPN port forwarding support and limits, checked October 2026
VPNPort forwardingTerms and limits
Proton VPNYes, on all paid plansP2P servers only, in the Windows and Linux apps and in early access on macOS. The server picks a random port, which usually changes when you reconnect
Private Internet AccessYes, on most locationsNot available on US server locations
WindscribeYes, on ProOne ephemeral port at a time, requested in My Account and cleared after 7 days. Permanent rules need a separately bought static IP. Not on Free or Build-a-Plan
hide.meYes, on PremiumDynamic port forwarding in the desktop apps, so there is no permanent or static port. Not on the free plan
PureVPNPaid add-onYou choose the ports in the Member Area, then connect to a server that supports port forwarding
PrivateVPNYes, on some serversOnly on selected protocols and locations; its help center lists which ones
NordVPNOnly with the Dedicated Server add-onStandard servers and Dedicated IP do not support it. You set up to 20 TCP or UDP rules yourself. Not in the Mac App Store version of the app
SurfsharkNoSurfshark leaves it out because an open port is an entry point to your device
ExpressVPNNoIts VPN servers do not support port forwarding
CyberGhostNoCyberGhost says it does not support port forwarding
MullvadNo, removed in 2023Stopped new forwarded ports on May 29, 2023 and removed the rest on July 1, 2023, citing abuse

Before you pay for one of them, check four things:

  • Who picks the port. Proton VPN, PIA, hide.me, and Windscribe assign the outside port; PureVPN's add-on and NordVPN's Dedicated Server let you set it. A torrent client accepts any port, but players joining a game server have to be told the new number.
  • Whether it survives a reconnect. Proton's port usually changes when you reconnect, and a Windscribe ephemeral port expires after 7 days, so update the port in your client when either happens.
  • Which device receives the traffic. The forwarded port reaches the device running the VPN app. Consoles cannot run one, so for a PS5 or Xbox the VPN would have to run on your router, which is an advanced setup with its own limits.
  • Whose address you publish. The port sits on the VPN's IP, not yours. Anyone who finds it can reach the service behind it, so keep that service updated and behind a password.

To confirm a forwarded port, keep the VPN connected and run the open port checker on that port. It tests the public address you browse from, which is the VPN exit while the tunnel is up, so an open result means the forward reaches your device. The checker tests TCP, so check UDP-only game ports from the game itself.

Our reviews of Proton VPN, Private Internet Access, Windscribe, hide.me, PureVPN, and PrivateVPN cover the rest of each service. If only your own devices need to connect, you may not need a paid VPN at all: an overlay network such as Tailscale reaches them without opening any port, and it is free for personal use.

Gaming behind CGNAT: strict NAT and what you can fix

CGNAT shows up as "Strict NAT" (Xbox), "Type 3" (PlayStation), or "Moderate"/"Strict" in most game-console diagnostics. The visible symptoms: cannot host games, cannot join friends who are also behind strict NAT, voice chat breaks in party calls, and matchmaking takes longer because the platform falls back to a relay server instead of a direct peer-to-peer connection.

That relay fallback is also why CGNAT often shows up as a latency problem rather than a connection problem. Instead of a direct path to the other player, your traffic detours through an intermediate server, and the extra hops cost real milliseconds. If high ping is what actually brought you here, work through our guide to diagnosing and reducing ping - it separates the delay that CGNAT causes from the delay your own WiFi, router, or ISP route is responsible for, which need completely different fixes.

UPnP and NAT-PMP cannot fix CGNAT. Those protocols only negotiate port mappings with the local router; they have no influence on the upstream ISP translation layer. Console troubleshooting guides that recommend "enable UPnP on your router" assume your router is the public edge, which is not true under CGNAT.

Realistic fixes for gamers behind CGNAT are to ask the ISP for public IPv4 (often offered as a static-IP add-on for a few dollars per month), switch to a plan that does not use CGNAT, or use a purpose-built relay or overlay network. An ordinary consumer VPN may change the outbound route or NAT behavior, but it does not restore inbound port forwarding unless the provider explicitly assigns a reachable port or public endpoint. For Xbox specifically, the Xbox Live relay (Teredo on Windows, equivalent on console) can sometimes upgrade Strict NAT to Moderate, but it is not reliable.

How to fix strict NAT type on PS5 (NAT Type 3)

First check whether your router is actually the public edge: compare its WAN IP with your public IP using the CGNAT test. If they match, enable UPnP on the router or forward the PSN ports Sony documents (TCP 3478-3480, UDP 3478-3479), and NAT Type 3 usually becomes Type 2. If the WAN IP is inside 100.64.0.0/10 or differs from your public IP, no PS5 or router setting will reach Type 2 reliably - the fix is a public IPv4 from the ISP or one of the CGNAT workarounds above.

How to fix strict NAT on Xbox

On the console, check Settings, General, Network settings, NAT Type. With a public-edge router, enabling UPnP and forwarding UDP 3074 typically moves Strict to Open. Behind CGNAT, Xbox's Teredo-based relay may upgrade you to Moderate at best; for Open NAT you need the ISP-side fix.

Port forwarding rules need the console's local IP address. Our guide to finding the IP address on PS5, Xbox, and Switch shows where each console lists it and how to reserve it so the rule keeps working.

Strict or moderate NAT on PC

PC games and voice apps hit the same wall: UPnP and manual port forwarding only work when your router owns a public IP. For co-op and virtual-LAN play behind CGNAT, an overlay network like Tailscale or ZeroTier is usually the most practical fix, because both ends dial out and no inbound port is ever required.

Common mistakes and edge cases

  • Testing from inside the same LAN. Hairpin NAT and local loopback behavior can make a failing external setup seem to work internally.
  • Using the wrong internal host IP. The device changed address after a reboot or DHCP renewal.
  • Forgetting protocol differences. A game may need UDP, but the test was done only with TCP.
  • Assuming every ISP supports public inbound IPv4 equally. Many consumer and mobile plans intentionally do not.
  • Ignoring IPv6. Some users fight broken IPv4 exposure when the cleaner solution is publishing the service over IPv6 with proper firewall rules.
  • Blaming CGNAT before checking the service listener. If nothing is listening locally, fixing upstream reachability will not help.

Useful IP Trackers tools for CGNAT diagnosis

  • CGNAT Test compares the router WAN address with the public address and separates public IP, shared space, and likely double NAT.
  • Open Port Checker verifies whether the configured TCP service is reachable from the public internet.
  • IP Address Lookup gives the public address seen by the outside world.
  • ASN Lookup identifies the network operator behind the public-facing address.
  • ISP Directory helps you compare provider context and likely access models.
  • WHOIS / RDAP Lookup adds ownership context if the visible public address is unfamiliar.
  • Reverse DNS Lookup can provide provider or infrastructure naming hints around the public-facing IP.

Frequently asked questions

Can port forwarding work behind CGNAT? Not in the usual direct way unless the ISP gives you a real public IP or provides a special forwarding feature.

How do I know if I am behind CGNAT? Compare the router's WAN IP with the public IP shown on the web, and watch for the 100.64.0.0/10 range on the WAN side.

Is double NAT the same as CGNAT? No. Double NAT is a local multi-router problem; CGNAT is an ISP-side shared translation layer.

Will bridge mode solve CGNAT? Not by itself. It can fix local double NAT, but it does not remove the ISP's upstream CGNAT.

Is IPv6 a workaround? Often yes, if your ISP and client side support native IPv6 and you configure firewall rules properly.

What if I only need remote access, not a public game server? A VPN overlay, reverse tunnel, or managed relay service is often the simplest answer.

Which VPNs support port forwarding? As of October 2026: Proton VPN on paid plans, Private Internet Access outside the US, Windscribe Pro, hide.me Premium, PureVPN as a paid add-on, PrivateVPN on some servers, and NordVPN only with its Dedicated Server add-on. Surfshark, ExpressVPN, CyberGhost, and Mullvad do not offer it. The table above lists the limits of each.

Related reading: CGNAT IP Range Guide, Public vs Private IP, Reserved IP Blocks, What Is My ISP?, and VPN Connected but IP Not Changing

Primary sources

Standards, registries, and first-party references used to verify this guide:

  1. Technical transparency table (opens in a new tab) - Starlink. Regional table lists Residential CGNAT, optional public IPv4 on Local/Global Priority and IPv6 availability. Confirm current regional entitlement with Starlink.
  2. Minecraft Java server download and setup (opens in a new tab) - Mojang / Minecraft. Java server networking guidance and port 25565; do not generalize to every edition or tunnel protocol.
  3. Troubleshooting Remote Access (opens in a new tab) - Plex. CGNAT/double-NAT limitations, internal TCP 32400 and matching a manually selected public port.
  4. RFC 6598: Shared Address Space (opens in a new tab) - IETF. Defines the shared IPv4 range commonly used by CGNAT.
  5. RFC 6888: Common Requirements for CGN (opens in a new tab) - IETF. Explains why inbound mappings depend on upstream carrier behavior.
  6. How to use port forwarding (opens in a new tab) - Proton VPN. Paid plans and P2P servers only; the server picks a random port that usually changes on reconnect.
  7. VPN servers (opens in a new tab) - Private Internet Access. States that port forwarding works on most PIA server locations.
  8. Windows 10 and 11: Installing and Using the PIA App (opens in a new tab) - Private Internet Access. Notes that port forwarding is not offered on US server locations.
  9. What is Ephemeral Port Forwarding and How to Use It (opens in a new tab) - Windscribe. Pro-only ephemeral ports last 7 days; permanent rules need a static IP.
  10. How do I activate dynamic port forwarding? (opens in a new tab) - hide.me. Setup and requirements for Premium dynamic port forwarding.
  11. What are the Add-Ons available with PureVPN? (opens in a new tab) - PureVPN. Lists port forwarding as a paid add-on.
  12. Frequently Asked Questions (opens in a new tab) - PrivateVPN. Port forwarding is allowed on selected protocols and locations.
  13. How to configure port forwarding on your NordVPN Dedicated Server (opens in a new tab) - NordVPN. Port forwarding is available only with the Dedicated Server add-on, not on standard servers or Dedicated IP.
  14. What is VPN port forwarding? (opens in a new tab) - Surfshark. States that Surfshark does not support port forwarding and why.
  15. Port Fail Security Vulnerability (opens in a new tab) - ExpressVPN. States that ExpressVPN servers do not support port forwarding.
  16. What Is Port Forwarding? (opens in a new tab) - CyberGhost. States that CyberGhost VPN does not support port forwarding.
  17. Removing the support for forwarded ports (opens in a new tab) - Mullvad. Announced May 29, 2023; existing forwarded ports were removed on July 1, 2023.

Did this article help?

IP Trackers is free with no sign-up. A small contribution helps keep the guides current and the tools running.

Keep exploring

DNS Lookup ToolProxy/VPN DetectionReverse DNS (PTR) Lookup
PreviousVPN Connected but IP Not Changing? How to Fix ItNextWhat Is My ISP? How to Check Your Internet Provider and ASN

Related reading

CGNAT IP Range: 100.64.0.0/10 Explained (RFC 6598)13 min read - January 17, 2026How to Find the IP Address on PS5, Xbox and Nintendo Switch10 min read - October 2, 2026How to Find the IP Address of a Smart TV, Roku or Fire TV10 min read - October 2, 2026How to Find Your Printer's IP Address (HP, Canon, Epson, Brother)10 min read - October 2, 2026Why Does My IP Address Keep Changing? How to Stop It12 min read - October 2, 2026Your IP Has Been Temporarily Blocked or Banned: How to Fix12 min read - October 2, 2026