Local data routing
emnify was the first to move beyond traditional home-routed network models with a patented, globally distributed operational core. Its cloud-native platform combines a mobile core network with a dedicated communications platform purpose-built for IoT. Deployed across seven AWS regions with 2-3 availability zones per region, this distributed architecture ensures high availability and continuous data flow across the emnify network - even if an individual cloud data center becomes unavailable.
Regional data breakouts
In a traditional roaming scenario, data is routed to the core network, which resides in the country of the operator that has issued the SIM card. This home routing makes the deployment of a distributed IoT solution impossible.
With emnify’s globally distributed IoT SuperNetwork, you can define flexible data routing to the closest AWS region. Data can either be automatically routed to the region closest to where the SIM is located or, in the case of a single-region application deployment, routed to the region where the application server resides.
The emnify IoT SuperNetwork is deployed in seven AWS regions:
- eu-west-1 (Ireland)
- eu-central-1 (Frankfurt, Germany)
- eu-central-2 (Zurich, Switzerland)
- us-east-1 (Virginia, United States)
- ca-central-1 (Canada)
- ap-southeast-1 (Singapore)
- sa-east-1 (São Paulo, Brazil)
Each AWS region is deployed across 2-3 availability zones to ensure high availability. Even in the event of a single data center failure, device data is continuously routed within the emnify network. emnify also establishes direct peering with local operators in each region, ensuring low-latency connectivity and reducing reliance on intermediary transit routes.
Additional breakouts in AWS regions are launched based on market growth demands.
You can either select a specific breakout region or the network automatically selects the breakout region closest to the device. Service policies specify how the network selects breakout regions for your devices. You can create and configure service policies in the emnify Portal or using the emnify REST API.
Complying with local regulations
Several countries require cellular networks to follow local regulations, or network operators impose restrictions on roaming.
Local IP assignment
emnify enables access to localized content using the emnify distributed breakouts. Devices utilizing the public internet use carrier-grade NAT with local IP addresses for that region. Consequently, content filters enforced in that region are also applied. Additionally, emnify utilizes a DNS filter for Brazil based on special legal requirements in the market.
Permanent roaming
Several operators are banning devices from roaming on their networks for extended periods. The emnify IoT SuperNetwork includes direct agreements with over 400 network operators in more than 100 countries, allowing permanent roaming for IoT and M2M use cases.
Unlike other forms of network access, like those provided through intermediaries or resellers, these direct roaming agreements differ primarily in the level of control and visibility they offer:
- Control and stability: emnify can manage its networking connectivity, ensuring stability and consistency in connectivity and features. Without direct access agreements, a provider’s networking connectivity and management could be out of emnify’s control.
- Visibility: Direct access agreements provide visibility into granular, network event-level data, helping to alert, troubleshoot, and resolve network issues quickly.
- Regulatory protection: Direct agreements help protect you against regulatory changes, network changes, and unexpected roaming costs.
