Internet Breakout
This page describes how internet breakout behaves on the 1NCE Platform 2.0 compared with the 1NCE Platform 1.0.
Routing mode
On the 1NCE Platform 2.0 core network, your organization is locked to the breakout region of the 1NCE entity you are contracted with. For example, a customer of 1NCE Inc. uses the US breakout. This applies to new SIM cards provisioned on the 1NCE Platform 2.0 core network.
Existing SIM cards keep their current breakout behavior unchanged — including automatic mode. They remain on the 1NCE Platform 1.0 core network.
Available breakout regions in v2:
- Frankfurt
- US
- APAC
If you currently use manual mode in v1, your configuration will be migrated to v2. Customers can contact support to change the breakout region configuration.
An automatic routing mode for the 1NCE Platform 2.0 core network is planned for a future release. Until then, new SIM cards use your entity's breakout region.
Public IP ranges
Public breakout IPs will change on the 1NCE Platform 2.0. Review the exact IP ranges in the v2 documentation.
NAT gateway
The 1NCE Platform 2.0 uses AWS-managed NAT gateways. Connections may be disconnected sooner during idle periods. See session timeouts below.
| Protocol | 1NCE Platform 1.0 | 1NCE Platform 2.0 | Change |
|---|---|---|---|
| TCP idle timeout | 600s | 350s | Reduced |
| UDP idle timeout | 120s | 120s | No change |
When the TCP idle timeout is exceeded, the AWS NAT gateway sends a TCP RST and the connection is dropped. For UDP, an ICMP "destination unreachable" is returned after the idle window.
What to do
- Existing SIM cards: no action — their breakout behavior does not change.
- New SIM cards: the breakout region of your 1NCE entity applies; contact support if you need a different region.
- Review the public breakout IPs in v2 documentation.
- If you run long-lived TCP sessions, add TCP keepalives to avoid disconnection at the 350-second idle timeout.
- Check NAT gateway timeout behavior for your application needs.