Permanent roaming in IoT occurs when a device uses a SIM card registered to a foreign network operator for its entire operational life, without ever returning to the SIM's home network. This is the default state for most globally deployed IoT devices. A smart meter installed in Germany with a SIM from a Netherlands-based operator will roam on German networks indefinitely. It will never "go home." That is permanent roaming.
Roaming agreements between operators were designed for traveling humans, not stationary devices. Regulatory frameworks in a growing number of countries reflect that mismatch, and the consequences for organizations deploying IoT at scale are increasingly serious.
Most cellular IoT devices share two characteristics that distinguish them from mobile phones: they stay in one place, and they stay connected for years. A utility meter, a charging station, an industrial sensor, a surveillance system. None of them roam the way a business traveler does. All of them spend their entire operational life connecting to a network the SIM was never designed to call home.
This creates three distinct problems.
Regulatory exposure: A growing number of countries prohibit permanent roaming outright or make it practically unworkable through supporting regulation. Deploying devices with permanently roaming SIMs in these markets is a compliance failure, and it carries the risk of sudden disconnection.
Network performance degradation: Operators prioritize local subscribers. Roaming devices receive secondary treatment: reduced bandwidth, increased latency, and throttling under congestion. For IoT applications that depend on reliable data transmission, this is an operational problem.
Data sovereignty risk: When a SIM is registered in one country and the device operates in another, traffic routing follows the SIM's home network. Data generated inside one country travels abroad before reaching its destination. In markets with strict data localization requirements, that is a compliance problem on top of a performance one.
Regulation varies significantly by country, and the list of markets with active restrictions is growing.
Brazil, Turkey, and Nigeria have instituted explicit bans on permanent roaming. In Brazil, the regulator Anatel reinforced its long-standing prohibition with additional enforcement steps in 2025. Turkey is particularly strict: in 2025, the country required all eSIM provisioning to be handled through Turkish operators, which resulted in dozens of international eSIM providers being blocked.
Permanent roaming is effectively prohibited in China, India, Egypt, Saudi Arabia, Singapore, and the United Arab Emirates, though not always through explicit legislation. In China and India, companies providing communication services require local licenses. In Saudi Arabia and the UAE, services must be delivered by a locally registered operator.
The Americas present a mixed picture. A February 2026 report from Cullen International found that permanent roaming remains legally permissible in most of the eleven Americas markets surveyed, with Brazil as a clear outlier and several other jurisdictions classifying IoT connectivity as a regulated telecommunications service when it includes public internet access.
For organizations with devices deployed across multiple countries, the practical reality is this: the markets most likely to be on your deployment roadmap include at least some where permanent roaming is a legal or operational risk.
The failure mode is abrupt and disruptive. An operator detects a SIM roaming beyond the permitted period, typically 90 to 120 days, though this varies by market and operator, and terminates the connection. The device goes offline. For many IoT applications, there is no fallback.
In practice, this means a fleet of asset trackers stops reporting location data. A grid of charging stations goes dark. A set of industrial monitoring sensors stops transmitting. A building security system loses its connection to the management platform.
Recovery requires physical intervention or remote reprovisioning. In the case of physically inaccessible devices, MFF2 solderable SIMs, or large fleets across multiple markets, recovery is slow and expensive.
The operational risk is significant. The regulatory risk is separate. They arrive together.
When a device roams, traffic takes a longer path. Data generated on the device travels back to the SIM's home network first, then routes to its destination. This is called home-routed roaming. The additional hops add latency, typically 150 to 300 milliseconds, and increase data transit costs. In applications where timing matters, industrial automation, grid management, real-time monitoring, that latency is not a minor inconvenience.
When a device connects to a local network with a locally provisioned profile, traffic routes directly from the device to its destination. No international detour. Lower latency, lower cost, and no dependency on two operators keeping their agreement intact.
The performance difference is measurable. The compliance difference is binary.
Organizations managing global IoT deployments have historically handled the permanent roaming problem in one of three ways, each with trade-offs.
Multiple SIM SKUs. Deploying different SIM cards for different markets solves the roaming problem at the cost of operational complexity. Multiple procurement relationships, multiple contracts, multiple data pools, and multiple management platforms. Inventory management for large fleets becomes a logistics problem.
Single-carrier roaming agreements. Using a single global operator that has negotiated roaming agreements across target markets reduces operational complexity. It does not solve the regulatory exposure in markets that prohibit foreign SIMs, and it does not solve the performance degradation from home-routed traffic.
Manual reprovisioning. Swapping SIM cards when restrictions kick in works for small deployments or lab environments. For tens of thousands of devices in the field, it is not viable.
None of these approaches addresses the regulatory map as it currently exists. And that map is expanding.
The technical answer to permanent roaming is the ability to change operator profiles remotely, without physical access to the device.
Multi-IMSI technology allows a single SIM to carry multiple network identities. The SIM connects to whichever network provides the strongest signal in the device's current location, without any of those connections being classified as roaming. The SIM presents a local identity to the local network.
eUICC, embedded Universal Integrated Circuit Card, takes this further. An eUICC-enabled SIM stores multiple operator profiles and switches between them remotely, over the air. In markets where a locally registered operator profile is required, the device presents one. When it moves to a different market with different requirements, the profile changes.
This matters for compliance. It also matters for performance: locally routed traffic means lower latency and more predictable data costs.
GSMA SGP.32, the remote SIM provisioning standard published in 2023 and updated to version 1.2 in late 2024, was designed specifically for headless IoT devices. It enables bulk, server-orchestrated profile management across large fleets, without user interfaces or physical intervention. Certified products began appearing in 2025, with broader commercial deployment expected through H2 2026 and into 2027. SGP.32 is a significant step forward for the industry, though it is worth being precise about what it solves: it provides the technical mechanism for remote profile switching. Whether a given profile meets local regulatory requirements depends on which operator provides it and whether the provisioning infrastructure satisfies local rules. Technology and compliance need to be managed together.
IXT is a full MVNO with its own core network. This is not a reseller arrangement. IXT owns and operates its own greenfield IoT core, which gives it direct control over routing, policies, and network behavior without dependence on third-party carriers.
The IXT Global SIM uses multi-IMSI technology to connect to 600-plus mobile networks across 190-plus countries. It supports 2G, 3G, 4G, 5G, NB-IoT, LTE-M, and NTN. It auto-connects to the strongest available signal in each market. The SIM activates on first use, giving organizations a grace period before consumption begins, and it arrives pre-activated and ready to connect.
For markets where local provisioning is required or preferred, the IXT Global SIM is available with eUICC, enabling remote profile switching. For permanently deployed devices in MFF2 form factor, including solderable chips for devices where SIM replacement is physically impossible, eUICC and remote profile switching are the right architecture to build toward as local provisioning requirements in key markets continue to develop.
All SIMs can share a single Global Data Pool. Traffic data from devices across every country draws from one shared allocation. No individual caps per SIM. No stranded data on underused devices. No surprise overage fees when a high-traffic device exceeds an individual plan.
The IXT CMP provides real-time visibility into connectivity status, location, and data usage across the entire fleet. Most connectivity management platforms show data that is 24 to 48 hours old. IXT shows current status. When a device goes offline or behaves unexpectedly, the diagnostic information is available immediately, not the next day.
Connectivity and compliance are not the same thing
Solving the permanent roaming problem means getting devices connected in a compliant way. It does not, by itself, make those devices secure.
An IoT device connected to a local network through a compliant profile is still transmitting data across the public internet unless something at the network level keeps that traffic private. Most IoT deployments lack that protection. Traditional VPN approaches require client software on the device, and most IoT devices do not run software agents. They are headless, constrained, and not designed to handle the overhead of a VPN client.
IXT's standard security offering is Zero Trust, built into the connectivity layer at the SIM level. This is not an optional feature. It is how IXT approaches security by default, built specifically for the constraints of IoT.
Zero Trust Connectivity, powered by Zscaler ZTNA, eliminates the attack surface. All traffic is device-initiated. No ports are exposed. No VPN clients are required on devices. Security policies are enforced at the network edge. This works on headless devices, constrained devices, and industrial devices that were never designed to run security software.
For organizations operating in regulated industries or across markets with data sovereignty requirements, this layer of visibility and control is not optional. NIS2, the EU directive on network and information security, requires risk management, supply chain security, and incident containment. Zero Trust, built into the SIM and the network, is the architecture built to meet that requirement.
If your deployment touches multiple countries today, or will in the next two years, here are the questions that separate providers who solve the permanent roaming problem from those who work around it.
Multi-IMSI means the SIM presents a local identity in each market. Single-network SIMs roam.
Remote profile switching without physical access is the operational requirement for deployed fleets. Ask specifically whether this works on constrained devices without user interfaces.
Coverage claims, 600 networks, 190 countries, tell you where the SIM connects. They do not tell you where local provisioning is available. Ask specifically about Brazil, Turkey, China, India, and any other market on your deployment roadmap.
Is data pooled globally, or does each SIM have individual caps? Individual caps create stranded data on low-usage devices and overage charges on high-usage ones. A global pool eliminates both.
24 to 48-hour delays in usage and connectivity data are the norm for most providers. Real-time visibility changes what is possible for troubleshooting and fleet management.
VPN requires software on the device. Most IoT devices do not run software agents. If the security answer is "VPN," ask how that works on a device with no operating system and no user interface.
Permanent roaming in IoT refers to a device using a SIM card registered to a foreign network operator for its entire operational life, without returning to the SIM's home network. This is the default state for most stationary IoT devices using a SIM from a different country.
Brazil, Turkey, and Nigeria have explicit bans. Permanent roaming is effectively prohibited in China, India, Egypt, Saudi Arabia, Singapore, and the UAE through licensing requirements or mandatory local operator involvement. Regulations in each country are subject to change.
eUICC with remote profile switching addresses the technical side of the problem by allowing a device to present a locally provisioned operator profile. Whether that profile satisfies local regulations depends on which operator provides it and whether the provisioning infrastructure meets local requirements.
SGP.32 is the GSMA's remote SIM provisioning standard for IoT, published in 2023 and updated to version 1.2 in late 2024. It enables bulk, server-orchestrated profile management for headless IoT devices without physical intervention. Commercial deployment is expected to accelerate through H2 2026 and into 2027.
Multi-IMSI is a technology allowing a single SIM card to carry multiple network identities. The SIM presents a local identity to whichever network it connects to, avoiding the classification of the connection as roaming.
Home-routed roaming traffic travels back to the SIM's home network before reaching its destination. This adds latency, typically 150 to 300 milliseconds, and increases data transit costs. In applications that depend on real-time data, this is an operational and commercial problem.
Zero Trust is a security architecture that removes the assumption of trust from network connections. Every device, every session is treated as untrusted until verified. For IoT, where devices are headless and cannot run VPN clients or security software, Zero Trust must be enforced at the network level rather than on the device. IXT delivers this built into the SIM and the network, without requiring any client software on the device.
Permanent roaming was never designed for IoT. It is a byproduct of deploying devices globally using SIM technology built for traveling consumers. As the regulatory map tightens and the technical tools for solving the problem mature, the organizations best positioned are those that treat connectivity, compliance, and security as a single architecture decision rather than three separate ones.
If your IoT deployment spans multiple countries today, or if it will, the question is not whether permanent roaming is a risk. The question is how you address it.
IXT is built for this. One SIM, global coverage, a global data pool, real-time visibility through the CMP, and Zero Trust security built into the connectivity layer. No VPN clients on devices. No exposed ports. No 24-hour delay before you know something went wrong.
To test the IXT Global SIM in your environment or talk through your deployment requirements, get in touch.
This article was written by the IXT team. IXT is a full MVNO built specifically for IoT, operating its own core network across 600+ mobile networks in 190+ countries. IXT helps organizations deploy, manage, and secure connected devices at scale, from single-country pilots to global fleets.