Plus
$2/mo
- 1 dedicated IP address
- 10 devices
- 5 open ports
- 100 GBbandwidth
- 20 Mbpsspeed
T-Mobile Home Internet cannot forward ports: homes share a public IPv4 through CGNAT, and static IPs come only with Business plans. GetAStatic gives you your own static IPv4 over WireGuard, with the ports you choose open. The gateway stays as it is.
Not affiliated with T-Mobile. Prices as listed on their sites, checked 2026-10-06.
Updated
| Port forwarding on Home Internet | None |
|---|---|
| Public IPv4 | Shared through CGNAT (464XLAT) |
| Static IP | Business plans only, as an add-on: ~$15/mo (third-party reports) |
| IPv6 | Yes |
| GetAStatic | Your own static IPv4 and the ports you open, from $2/mo |
Checked .
T-Mobile Home Internet gives your home IPv6, but no public IPv4 of its own. IPv4 traffic goes through 464XLAT, as T-Mobile users report: the gateway translates it, and T-Mobile's carrier-grade NAT (CGNAT) shares one public IPv4 among many customers. The address a what-is-my-IP site shows belongs to T-Mobile, not to you, and it can change.
So nobody on the internet can start an IPv4 connection to your home. The gateway and its app have no port-forwarding setting. A third-party router behind the gateway has a port-forwarding page, but its rules only reach as far as the gateway. The connection still stops at T-Mobile's NAT.
T-Mobile sells a static IP only with T-Mobile Business Internet, as a paid add-on: ~$15/mo (third-party reports). Home plans have no static IP option.
Your own static IP over WireGuard. No VPS.
Dedicated IPv4 from $2/mo →This takes one minute. The full port-forwarding check works for every ISP.
If the addresses do not match, a port forward cannot work. You need a public IPv4 from somewhere else.
GetAStatic gives you a dedicated static IPv4 in Kansas City, Missouri or San Jose, California. Your server, or your own router behind the gateway, connects out to our node over WireGuard. T-Mobile allows outgoing connections, so CGNAT does not block the tunnel.
When someone connects to your IP on a port you opened, the traffic comes down the tunnel to your device. The device also sends its outgoing traffic from the same IP. Plex, game servers and allowlists all see one fixed address.
It is a VPN with your own address, not a shared exit. No other customer uses your IP.
Run WireGuard on the machine that hosts your service. Or run it on your own router behind the gateway, and every device behind that router uses the IP.
| Port | Protocol | Used for |
|---|---|---|
| 32400 | TCP | Plex Media Server |
| 25565 | TCP | Minecraft Java server |
| 19132 | UDP | Minecraft Bedrock server |
| 443 | TCP | Website or reverse proxy (HTTPS) |
Plus includes 5 open ports; Pro and Ultra have unlimited open ports. A port range counts as its size.
Plus for light use, Pro for most people, Ultra for full gigabit.
5× speed · 10× bandwidth · 2 IPs — only $2/mo more
No. T-Mobile sells a static IP only with T-Mobile Business Internet, as a paid add-on: ~$15/mo (third-party reports). Home plans share a public IPv4 through CGNAT. GetAStatic gives you a static IPv4 on any T-Mobile plan, from $2/mo.
No. Users report that the T-Mobile gateway has no true bridge mode. You can turn off its Wi-Fi and plug in your own router, but that router still sits behind T-Mobile's CGNAT. Run WireGuard on that router instead, and every device behind it uses your GetAStatic IP.
Only for visitors who also have IPv6. A visitor on a network without IPv6 cannot reach an IPv6 address, and many Plex and Minecraft clients still connect over IPv4. A public IPv4 works for everyone.
Yes. Run WireGuard on the Plex machine, open port 32400 TCP in the dashboard, and set "Manually specify public port" to 32400. Remote viewers then connect directly, not through the slow Plex Relay. Details: Plex behind CGNAT.
Yes. Open 25565 TCP for Java or 19132 UDP for Bedrock, and run WireGuard on the server. Players join with your IP. Other games: game servers behind CGNAT.
Have more questions? See the full FAQ →