A Static IP provides a dedicated public IPv4 address for your Neptune Internet service. This article explains what a Static IP is, how Neptune implements it, and when it may be the right choice for your connection.
If you need reliable inbound access over IPv4 or prefer full control over your network edge, a Static IP may be a better fit than CGNAT.
What is a Static IP?
A Static IP is a dedicated public IPv4 address that is assigned exclusively to your service and does not change over time.
From a customer perspective, this means:
Your service is directly reachable from the public internet over IPv4
Inbound connections are supported
You can host services, forward ports, and run servers reliably
A Static IP provides maximum compatibility with IPv4-based applications and services.
How Neptune implements Static IPs
Neptune assigns each Static IP service a dedicated /32 IPv4 address.
Key details:
The address is exclusive to your service
It is delivered over a dedicated interface
The address is assigned automatically via DHCP, but customers may choose to configure a static route on their own equipment instead.
From a customer point of view, this means you get the benefits of a Static IP without needing to manually configure addressing during setup.
Benefits of a Static IP
Reliable inbound connectivity
A Static IP allows inbound connections over IPv4, making it suitable for:
Hosting services or servers from home
Remote access to your network
Port forwarding and NAT rules
Development, testing, or lab environments
This is particularly useful where IPv6 support is limited or unavailable.
Maximum compatibility
Many applications, guides, and services still assume IPv4 connectivity.
A Static IP avoids edge cases where:
Software does not support IPv6
Peer-to-peer applications require direct IPv4 access
External systems expect a fixed IPv4 endpoint
Full control over firewall and routing behaviour
With a Static IP, you control how inbound and outbound traffic is handled at your router:
Custom firewall rules
Port forwarding
VPN endpoints
Service exposure policies
However, this flexibility comes with responsibility, as you are managing your own security posture.
Considerations when using a Static IP
Increased responsibility for security
Because your service is directly reachable from the public internet, you are responsible for securing any exposed services.
This may include:
Firewall configuration
Patch management
Restricting inbound access where appropriate
For technically confident users, this is expected and manageable.
Less privacy by default
A Static IP is persistent and uniquely associated with your service.
This means:
Your connection is more consistently identifiable by IPv4 address
IP-based tracking is more effective compared to CGNAT
This doesn’t imply misuse, but it’s an important consideration for privacy-conscious users.
Static IP vs CGNAT
Feature | Static IP | CGNAT |
Public IPv4 address | Dedicated | Shared |
Inbound IPv4 connections | Fully supported | Not supported |
IPv6 connectivity | Supported | Supported |
Port forwarding | IPv6 & IPv4 | IPv6 only |
Hosting services | IPv6 & IPv4 | IPv6 only |
Security exposure | User-managed | Lower by default |
If you require inbound access over IPv4, a Static IP is the correct choice.
Who should consider a Static IP?
A Static IP may be suitable if you:
Host services or servers from home
Need reliable inbound access over IPv4
Require port forwarding for work or testing
Use software that does not support IPv6
Prefer full control over firewall and routing behaviour
Can I switch later?
Yes. You can switch between Static IP and CGNAT at any time if your needs change.
Summary
A Static IP provides a dedicated, publicly reachable IPv4 address with full inbound connectivity and maximum compatibility.
For most home users, CGNAT is sufficient and simpler. For advanced networking needs or IPv4-specific use-cases, a Static IP is the better choice.
If you’re unsure which option fits your needs, starting with CGNAT and switching later is a sensible approach.