A fixed-IP SIM card is a cellular SIM provisioned by the carrier to always receive the same, directly addressable IP address, so a field device using it can be reached from the outside rather than only reaching out. It is the specific product operators buy when they need to connect inbound to an RTU or gateway over cellular, instead of forever waiting for the device to call home. This guide explains what a fixed-IP SIM actually provides at the hardware and carrier level, the use cases that call for it, and how it sidesteps the carrier-grade NAT that hides ordinary SIMs.
Fixed-IP SIM in one line: A fixed-IP SIM card, sometimes called a static-IP or addressable SIM, is an M2M SIM that a mobile carrier configures to always assign the same IP address to the device, and to place that device on a network path where the address is reachable for inbound connections rather than hidden behind carrier-grade NAT. This lets an engineer or SCADA master initiate a connection to the remote device at a known address, which an ordinary consumer SIM - with a rotating, non-routable address behind NAT - does not allow.
A fixed-IP SIM delivers two things that a standard SIM does not: a persistent address and inbound reachability. Persistence means the device answers to the same IP every time it connects, so anything that wants to talk to it - a polling master, an engineer's laptop, a diagnostic tool - can be pointed at a fixed target rather than chasing an address that changes with each attach. Reachability means that address is on a routable path where connections initiated from outside can actually arrive at the device, instead of being dropped by the carrier's network.
This is provisioned at the carrier and SIM level, not on the device. The carrier assigns the SIM to a special APN and address pool configured for static, routable addressing, often tied into a private network or VPN back to the customer so the traffic never traverses the open internet in the clear. From the device's point of view very little changes - it still attaches to the cellular network normally - but from the network's point of view it now has a stable identity that other systems can find and connect to.
It is worth being precise about the distinction from the general idea of a static IP. The conceptual difference between static and dynamic addressing is about whether an address changes; a fixed-IP SIM is the concrete carrier product that implements a static, addressable identity over cellular, including the inbound routing that makes the address useful. You can have a stable-looking address that is still unreachable from outside because it sits behind NAT - a fixed-IP SIM is specifically the offering that solves both the stability and the reachability at once.
Ordinary cellular SIMs almost always sit behind carrier-grade NAT, or CGNAT, where many devices share a pool of public addresses and each device is given a private, non-routable address internally. CGNAT works fine for a phone browsing the web, because the phone always initiates the connection outward and the carrier maps the return traffic back. But it makes the device impossible to reach from outside: there is no stable, public address that points to it, and any inbound connection attempt has nowhere to land. A fixed-IP SIM avoids CGNAT by placing the device on a routable address the carrier maintains for it.
The classic use case is a legacy RTU or gateway that only supports inbound polling - a master that connects to the device on a schedule to read registers. Such a device cannot phone home, so it must be directly addressable, and a fixed-IP SIM makes that possible over cellular where a static public address would otherwise be unavailable. Remote engineering access is another driver: being able to reach a specific field device at a known address to reconfigure it, pull logs, or update firmware without a site visit is far simpler when the device answers at a fixed target.
Fixed-IP SIMs also simplify security by giving the traffic a predictable shape. Because the device lives at a known address on a private carrier network, firewall rules and access controls can be written against that address, and the whole path can be locked down to a VPN back to the customer's systems. This makes cellular remote access auditable in a way that a rotating, NAT-hidden consumer SIM cannot match - though it also means the fixed-IP path itself must be secured properly, since an addressable device is one that others can attempt to reach.
In classic remote monitoring, a fixed-IP SIM was often the default answer to 'how do I reach the RTU,' and for inbound-poll-only equipment it remains a legitimate and sometimes necessary tool. On oil and gas sites running older gateways that cannot initiate their own connections, provisioning fixed-IP SIMs is a practical way to keep those devices addressable over cellular without deploying private circuits to every pad.
That said, modern cloud SCADA architectures increasingly avoid needing a fixed-IP SIM at all by having the field device initiate the connection outbound to a cloud broker. When the device phones home over an ordinary SIM, it does not matter that its address is dynamic and hidden behind CGNAT, because the connection is established from the inside out and stays open for two-way traffic. A platform such as Merobix built around this outbound model lets a fleet run on standard SIMs and still be monitored and, where the device supports it, reconfigured remotely.
The practical trade-off is cost, reach, and legacy support. Fixed-IP SIMs typically carry a premium and require carrier provisioning, and they are essential when the field equipment genuinely can only be polled inbound. The outbound-connection model removes that requirement for capable devices and simplifies the SIM logistics across a large fleet. Many real operations run a mix: fixed-IP SIMs where legacy hardware demands direct addressing, and standard SIMs with phone-home connectivity everywhere the newer model works, choosing per site rather than standardizing on one for its own sake.
Ordinary SIMs sit behind carrier-grade NAT, which gives each device a private, non-routable address and rotates it, so there is no stable public target an outside connection can reach. That works for a phone that always connects outward, but it means nothing on the internet can initiate a connection into the device. A fixed-IP SIM avoids this by putting the device on a persistent, routable address the carrier maintains for inbound reachability.
You need one mainly when the field equipment can only be polled inbound - a legacy RTU or gateway that cannot initiate its own connection and must be reached at a known address. Remote engineering access to a specific device over cellular is another common driver. If the device can instead phone home to a cloud broker over a standard SIM, you usually do not need a fixed-IP SIM at all, because the outbound connection sidesteps the CGNAT problem.
A fixed-IP SIM is the concrete carrier product that gives a cellular device a static, addressable IP, including the inbound routing that makes the address actually reachable. A static IP in the general sense just means an address that does not change, which by itself can still be unreachable if it sits behind NAT. The fixed-IP SIM solves both the stability and the reachability at the SIM and carrier level.
Merobix reads your field devices into a cloud SCADA - the real thing behind these terms, live in days from any browser.