Multi-Network IoT SIM Cards Are Not a Magic Bullet: Why Reliable M2M Connectivity Needs More Than Roaming

Multi-network IoT SIM cards are often sold as the answer to reliable M2M connectivity. The idea sounds simple: if one mobile network has poor coverage or goes down, the SIM can use another network.

That idea is useful. It is not wrong.

But it is incomplete.

A multi-network SIM gives an IoT device more possible networks. It does not guarantee that the SIM, modem, router or application will always choose the best network, abandon a bad network, recover from a stuck registration state, reset the cellular module properly, or explain what went wrong when the site goes offline.

In real deployments, reliability does not come from the SIM alone.

It comes from the full system:

• The SIM profile
• The roaming agreements
• The PLMN and FPLMN behaviour
• The modem firmware
• The industrial router configuration
• The antenna installation
• The APN and IP design
• The watchdog and recovery logic
• The monitoring platform
• The support process behind it

This is where many IoT projects go wrong.

The customer buys a “multi-network roaming SIM” expecting automatic resilience. Then the device still drops offline. The provider refreshes the SIM. The installer reboots the router. The customer blames the mobile network. Nobody can clearly explain whether the fault was signal, registration, APN, DNS, routing, modem state, network steering or a failed PLMN reselection.

That is not resilience. That is hope with a monthly invoice.

This article explains why multi-network IoT SIM cards are useful, why they are often oversold, how roaming and network selection really work, and what businesses should do if they want reliable IoT and M2M connectivity.

What Is a Multi-Network IoT SIM Card?

A multi-network IoT SIM card is a SIM that can connect to more than one mobile network.

In the UK, that might mean access to EE, Vodafone, O2 and Three, depending on the SIM provider and its roaming agreements. In international deployments, it may mean access to multiple operators across many countries.

These SIMs are commonly used for:

• CCTV systems
• EV chargers
• Smart meters
• Building management systems
• SCADA and telemetry
• Environmental monitoring
• Traffic management
• Digital signage
• Vending machines
• Payment terminals
• Remote gateways
• Industrial routers
• Vehicle tracking
• Asset monitoring

The commercial promise is obvious.

Instead of installing a single-network SIM and hoping that one operator works everywhere, the customer can deploy one SIM product that has access to several networks.

For many deployments, that is genuinely valuable.

If one network has poor coverage at a remote site, another may work better. If a device is moved between locations, the SIM may find a usable network without needing a physical SIM swap. If a project spans multiple countries, the organisation can avoid buying different SIMs for each region.

This is why IoT roaming SIMs, M2M SIMs and multi-network SIMs became popular.

But there is a dangerous assumption hidden inside the sales message.

Many buyers think “multi-network” means “automatic failover”.

It does not always work that way.

Why People Buy Multi-Network IoT SIM Cards

Most customers buy multi-network SIMs for one or more of the following reasons.

The buying logic is sensible.

The mistake is treating the SIM as the whole solution.

In reality, the SIM is only one part of the connectivity chain.

The “Magic Bullet” Myth

The myth usually sounds like this:

“The SIM can connect to all networks, so if one network goes down, it will just switch.”

That sounds logical.

But mobile network selection is not that simple.

A typical customer imagines this:

Network A fails
        ↓
SIM detects failure
        ↓
SIM selects Network B
        ↓
Device comes back online

A more realistic picture looks like this:

Network issue occurs
        ↓
Router detects loss of internet, or fails to detect it
        ↓
Modem may remain registered to the same PLMN
        ↓
SIM may still prefer the same network
        ↓
APN session may remain stale
        ↓
Ping reboot may restart router OS but not reset modem state
        ↓
Device reconnects to the same bad network
        ↓
Customer still offline

That is the gap between marketing and engineering.

A multi-network SIM gives access to more than one network. It does not always force the device to make the right decision at the right time.

The SIM Does Not Control Everything

One of the biggest misunderstandings is the belief that the SIM card alone decides which network to use.

It does not.

Network selection involves several layers:

This is why two routers using the same SIM can behave differently.

It is also why two SIMs in the same router can behave differently.

A good IoT connectivity design must treat the SIM, modem, router and APN as a system.

What Is a PLMN?

PLMN stands for Public Land Mobile Network.

In simple terms, it is the technical identity of a mobile network.

Every mobile network has a PLMN identity based on:

• MCC, Mobile Country Code
• MNC, Mobile Network Code

For example, a UK mobile network will have a UK MCC and its own MNC.

When an IoT router scans for networks, it is not just seeing “EE”, “Vodafone”, “O2” or “Three” as friendly brand names. It is seeing mobile network identities.

The modem then tries to register according to the SIM profile, network availability, roaming permissions and selection rules.

For a supporting explainer, internally link to:

What Is a PLMN?

Why PLMN Behaviour Matters in IoT

In consumer mobile use, PLMN selection is mostly invisible.

Your phone chooses a network, shows signal bars, and you move on.

IoT is different.

An industrial router may be installed in a cabinet, on a rooftop, in a basement plant room, on a wind farm, at a roadside cabinet, inside a payment kiosk, or in a remote pumping station.

Nobody is standing there watching the screen.

If the modem chooses a poor PLMN, gets stuck on a failing PLMN, or refuses to retry a previously failed PLMN, the device may remain offline until somebody intervenes.

That intervention may require:

• A remote modem reset
• A SIM refresh
• A router reboot
• A forced network scan
• Manual network selection
• SIM failover
• A site visit

This is why PLMN behaviour is not just a technical detail. It affects uptime, support cost and customer confidence.

What Is an FPLMN?

FPLMN stands for Forbidden Public Land Mobile Network.

The FPLMN list is a list of networks that the SIM or modem should not currently attempt to use.

This can happen when a registration attempt fails or a network rejects access.

The logic is reasonable. If a network has rejected the SIM, the modem should not waste time endlessly trying it again.

But in IoT this can cause practical problems.

A network may reject access temporarily. It may later recover. Coverage may improve. The SIM provider may update its roaming arrangements. But the device may still avoid that network because it has been added to the forbidden list.

For a supporting explainer, internally link to:

What Is an FPLMN?

Preferred PLMN Lists, Blank PLMN Lists and Operator Control

A SIM profile may contain preferred PLMN information.

This can influence which network is selected first when several are available.

Some providers load preferred network lists onto the SIM. Others may leave the SIM more open, allowing the modem and network selection process to behave with less provider preference.

This matters.

A SIM with a heavily managed preferred PLMN list may try to use Network A first, even if Network B is available and perhaps better at that specific location.

A SIM with a blank or less restrictive preferred list may allow more freedom, but this can also create unpredictability.

There is no universal “best” answer.

It depends on the deployment.

This is one reason why two “multi-network SIMs” from different providers may behave very differently in the same router.

Steered Roaming Versus Unsteered Roaming

This is one of the most important commercial and technical issues in IoT SIM connectivity.

What Is Steered Roaming?

Steered roaming means the SIM provider or home network influences which visited network the device should use.

The provider may prefer one network because:

• It has better commercial rates
• It has stronger wholesale agreements
• It performs better in general
• It supports required services
• It is part of the provider’s preferred partner network
• It aligns with the provider’s traffic management strategy

This is not automatically bad.

In many cases steering improves service quality and commercial stability.

But the customer needs to understand that “multi-network access” does not always mean the device has equal freedom to use every available network.

What Is Unsteered Roaming?

Unsteered roaming allows the device more freedom to select a network.

The modem may choose based on signal, registration success, previous behaviour and available network information.

This can be good for local resilience.

But it can also create issues if the device chooses a network that looks strong but performs poorly.

A site may have excellent RSRP but terrible SINR. Or it may register successfully but suffer from poor routing, high latency or congestion.

The modem does not always understand application performance.

It often knows that it is attached. It may not know that the customer’s CCTV stream, telemetry feed or VPN tunnel is unusable.

Why “Strongest Signal” Is Not Always the Best Network

Many customers assume the router should simply choose the strongest network.

That is a dangerous assumption.

Signal strength is only part of the story.

Important cellular metrics include:

A router may show three or four bars of signal and still deliver poor data performance.

A reliable IoT deployment should not be based on bars.

It should be based on measured signal quality, application testing and long-term monitoring.

Where Multi-Network SIMs Still Go Wrong

A multi-network SIM can still fail for many reasons.

1. The Device Stays on a Bad Network

The modem may remain attached to a network that is technically available but practically unusable.

This is common during partial outages.

The router may think it is connected because the modem is registered. The application may be offline because data is not passing correctly.

2. The SIM Is Steered Back to the Same Network

If a SIM is steered, the provider may prefer a certain network.

After a reboot, the device may reconnect to the same operator that caused the original problem.

3. The Modem Does Not Reset Properly

Some router reboot actions restart the router operating system but do not fully reset the cellular modem.

The router comes back online, but the modem returns to the same PLMN and the same failure state.

4. The APN Session Is Stale

The device may be registered to the mobile network, but the data session may be broken.

Refreshing the SIM or forcing a detach and reattach can sometimes resolve this.

5. DNS Is Broken

The router may have IP connectivity but fail DNS resolution.

If the watchdog only pings a domain name, this may trigger false failures. If it only pings an IP address, it may miss DNS failures that affect the application.

6. The Antenna Installation Is Poor

A multi-network SIM cannot fix bad RF design.

If the router is installed in a steel cabinet, basement or plant room with poor antenna placement, all networks may perform badly.

7. The Router Is Too Basic

Consumer routers often lack the recovery tools needed for unattended IoT deployments.

Industrial applications need industrial hardware.

Why Ping Reboot Is Not Enough

Ping reboot is often treated as a cure-all.

It is not.

A typical ping reboot feature works like this:

Router pings target address
        ↓
Ping fails several times
        ↓
Router reboots
        ↓
Router attempts to reconnect

That can help if the router software has frozen.

But many cellular faults are not router software faults.

The problem may be inside the modem state, SIM registration, PDP context, PLMN selection or APN session.

If the reboot does not fully reset the modem, the device may reconnect to the same bad network.

The result:

Device offline
        ↓
Ping reboot triggers
        ↓
Router restarts
        ↓
Modem remains effectively stuck
        ↓
Same PLMN selected again
        ↓
Device still offline

This is why a good recovery strategy must distinguish between different actions.

The key point is simple.

If the problem is a stuck modem or stuck PLMN, a basic ping reboot may not be enough.

Router Reboot Versus Modem Reset

This distinction deserves its own section because it is often misunderstood.

An industrial cellular router usually contains:

• Router CPU
• Router operating system
• Cellular modem module
• SIM interface
• Ethernet/Wi-Fi interfaces
• VPN services
• Firewall and routing engine

Rebooting the router does not always mean the cellular modem has been fully reset.

Depending on the hardware and firmware, the modem may retain state across a software reboot.

A proper recovery strategy should therefore include a way to restart the cellular module itself.

For Teltonika, Milesight, Robustel, InHand and other industrial routers, the exact feature names differ, but the principle is the same.

For critical IoT sites, you want controlled recovery actions that can force the cellular side to reinitialise, not just restart the router web interface.

Dual SIM Does Not Automatically Solve It Either

Dual SIM routers are useful.

But dual SIM is also often oversold.

A dual SIM router can support:

• Primary and backup SIM
• Different providers
• Different APNs
• Different IP addressing
• Different roaming agreements
• Different commercial plans

However, dual SIM only helps if failover is configured correctly.

Questions to ask:

A proper resilient design may use a multi-network SIM as primary and a different provider SIM as backup.

In higher-risk applications, this is often better than relying on one provider alone.

Manual Network Steering and Provider Portals

Many IoT SIM providers give customers access to a management portal.

These portals may include features such as:

• SIM status
• Data usage
• Network currently in use
• Session history
• Last seen timestamp
• SIM refresh
• Suspend/resume
• APN settings
• Manual network steering
• Diagnostics
• Alerts

These features matter.

A cheap SIM with no visibility may be fine for low-value applications.

It is not ideal for remote infrastructure.

What Is SIM Refresh?

A SIM refresh or network refresh is usually a provider-side action intended to clear or renew the mobile session.

It may help when:

• The session is stale
• The device is stuck
• The APN session needs refreshing
• The network has stale state
• The device needs to reattach

But it is not magic.

It will not fix poor antenna placement.

It will not fix local congestion.

It will not repair a broken router configuration.

It may not help if the router modem refuses to perform a clean reselection.

What Is Manual Network Steering?

Manual network steering allows the provider or customer to force or prefer a specific network.

This can be extremely useful after proper testing.

For example, an installer may discover that a site performs best on Vodafone, even though EE appears stronger. Manual steering can then lock or prefer Vodafone.

But it must be used carefully.

Manual steering can improve reliability at a fixed site. It can reduce flexibility for mobile or relocatable devices.

The Difference Between Coverage and Reliability

Coverage means a network is available.

Reliability means the application keeps working.

Those are not the same thing.

A site may have coverage from three networks and still suffer downtime because:

• The antenna is poorly positioned
• The modem selects the wrong PLMN
• The router watchdog is too basic
• The APN has routing issues
• The VPN does not reconnect
• The SIM provider lacks diagnostics
• The customer has no remote management
• The device is installed in a hostile RF environment

This is why the correct question is not:

“Does this SIM roam on all networks?”

The better question is:

“How will this complete system behave when something goes wrong?”

Recommended Reliability Architecture

A strong IoT connectivity design should look like this:

IoT Device / PLC / CCTV / Sensor
        ↓
Industrial Router or Gateway
        ↓
Primary SIM: multi-network IoT SIM
        ↓
Backup SIM: different provider or different profile
        ↓
Private APN or secure data breakout
        ↓
VPN / firewall / remote access layer
        ↓
Monitoring platform
        ↓
Alerting and recovery process

This design gives multiple levels of resilience.

It does not depend on one SIM doing everything.

Hardware Choice: Why Industrial Routers Matter

For serious IoT and M2M deployments, router choice matters as much as SIM choice.

A £40 consumer router may be fine for temporary internet access.

It is not ideal for unattended infrastructure.

Industrial routers usually provide:

• Better modem control
• External antenna support
• Watchdog options
• VPN support
• Remote management
• Dual SIM failover
• DIN rail mounting
• Wider temperature tolerance
• Better logging
• More stable firmware
• Digital input/output options
• Serial connectivity
• Modbus, MQTT or industrial protocol support

Common industrial router brands include:

• Teltonika
• Milesight
• Robustel
• InHand
• Digi
• Sierra Wireless
• Advantech
• INSYS icom

The right router depends on the application.

Modem Choice Matters Too

The modem inside the router affects performance and behaviour.

Important differences include:

• LTE category
• 5G NSA or SA support
• LTE-M support
• NB-IoT support
• Carrier aggregation
• Band support
• Firmware quality
• Network scan behaviour
• Recovery behaviour
• eSIM support
• Certification status

For example, a simple LTE Cat 4 router may be perfectly suitable for a low-data telemetry application.

A CCTV or temporary office application may need LTE Cat 6, Cat 12, Cat 18 or 5G.

A battery-powered sensor may be better suited to LTE-M or NB-IoT.

A future-proof IoT gateway may need eSIM/eUICC support and SGP.32 compatibility.

The point is that SIM choice and modem choice must match the application.

Antennas: The Boring Part That Often Decides Everything

A poor antenna installation can make the best SIM look bad.

A good antenna installation can make an average SIM perform well.

Things to check:

• Is the antenna inside a metal cabinet?
• Is the router installed near electrical noise?
• Is the antenna suitable for the required bands?
• Are the cables too long?
• Is the coax cable too lossy?
• Is MIMO being used correctly?
• Is the antenna mounted with clear separation?
• Has the installer tested multiple networks from the final mounting location?

Do not judge a site from a phone signal test at waist height.

Test using the actual router, actual SIM, actual antenna position and actual application.

Signal Quality Table

These values are general guidance, not absolute rules.

Application requirements matter.

A low-data sensor may tolerate weaker conditions than a CCTV system or VPN-connected industrial controller.

Permanent Roaming: The Regulatory and Commercial Problem

Permanent roaming is another issue that makes global IoT connectivity more complicated.

A roaming SIM was originally designed for a subscriber who travels temporarily onto another network.

IoT devices are different.

A smart meter, EV charger or industrial router may be deployed permanently in a country where the SIM has no home network.

That can create commercial and regulatory problems.

Some countries allow permanent roaming. Some restrict it. Some operators tolerate it commercially. Others may block, limit or renegotiate it.

The practical message is simple:

Do not assume a roaming SIM can legally and commercially remain in every country forever.

For international deployments, businesses should check:

• Country-specific permanent roaming rules
• Operator restrictions
• Data sovereignty requirements
• eSIM provisioning rules
• Local profile availability
• Contract terms
• Long-term commercial sustainability

This is one of the reasons SGP.32 is so important.

Where SGP.32 Fits In

SGP.32 is the GSMA technical specification for eSIM IoT remote SIM provisioning.

It is designed for IoT devices, including devices that may have no screen, no keyboard and no human user available to scan a QR code.

That matters because older eSIM workflows were not ideal for industrial IoT.

A phone user can scan a QR code.

A smart meter in a basement cannot.

A roadside cabinet cannot.

A remote telemetry device on a hilltop cannot.

SGP.32 is intended to make remote profile management more practical for IoT.

Internal links to include:

What Is SGP.32?

SGP.32 v1.2 Explained

What Is eUICC?

Remote SIM Provisioning Explained

Does SGP.32 Solve the Multi-Network SIM Problem?

Partly.

SGP.32 could make connectivity more flexible because it allows remote management of eSIM profiles.

Instead of being locked into one physical SIM profile for the lifetime of the device, a business may be able to change profiles remotely.

That creates major advantages:

• Change provider without visiting site
• Download a local operator profile
• Replace a poor roaming profile
• Adapt to permanent roaming restrictions
• Improve commercial control
• Support regional connectivity strategies
• Reduce physical SIM swaps
• Extend device life

But SGP.32 is not a cure-all.

It does not automatically fix:

• Poor antenna installation
• Bad router configuration
• Weak modem firmware
• Application-level failures
• Poor monitoring
• Bad VPN design
• Inadequate support processes
• Incorrect watchdog settings

SGP.32 improves profile control.

It does not remove the need for engineering.

SGP.32 Reliability Model

A future SGP.32-enabled connectivity design may look like this:

IoT Device with eUICC
        ↓
SGP.32-compatible IoT profile management
        ↓
Primary operator profile
        ↓
Alternative operator profile
        ↓
Local profile where required
        ↓
Private APN / VPN / secure breakout
        ↓
Monitoring and policy engine
        ↓
Automated or manual profile change

This is more powerful than a traditional roaming SIM.

But only if the platform gives the customer real control and visibility.

eSIM Management Platforms: The New Control Layer

The next battle in IoT connectivity may not be about who supplies the plastic SIM card.

It may be about who controls the eSIM management platform.

An eSIM IoT management platform can potentially control:

• Which profile is installed
• Which profile is enabled
• Which operator is used
• When profiles are changed
• How devices are grouped
• How policies are applied
• How connectivity is monitored
• How permanent roaming is managed

This is a major shift.

Traditional SIM resellers could often compete by offering good pricing, good support and access to strong roaming SIM products.

But if large providers control the eSIM orchestration layer, smaller resellers may lose direct influence over the most important part of the connectivity stack.

Are Big Network eSIM Platforms the Answer?

Large networks and global IoT connectivity providers are well positioned to benefit from SGP.32.

They may have:

• Direct operator relationships
• eSIM profile infrastructure
• Global roaming agreements
• Profile management platforms
• Better diagnostics
• More automation
• Stronger commercial control
• Regulatory teams
• Enterprise support

This could make them attractive to large IoT deployments.

For a multinational EV charging company, vehicle manufacturer, smart meter provider or industrial OEM, a managed eSIM platform from a major provider may be the obvious route.

But there is a catch.

Centralised control can also create lock-in.

If one provider controls the eSIM profiles, management platform, billing, support, roaming agreements and data breakout, the customer may find it difficult to move later.

The physical SIM lock-in problem could become a platform lock-in problem.

What Happens to Smaller IoT SIM Resellers?

This is the uncomfortable question.

Smaller IoT SIM resellers have historically offered value through:

• Personal support
• Flexible tariffs
• Faster response
• Vertical market knowledge
• Router configuration help
• Fixed IP and VPN services
• Practical deployment advice
• Customer-specific troubleshooting

SGP.32 does not remove the need for those skills.

But it may change where value sits.

If smaller resellers do not control eSIM profiles, profile orchestration or platform-level policy, they may become dependent on larger upstream providers.

That could reduce margin and reduce control.

However, smaller providers still have opportunities.

They can compete by offering:

• Router configuration expertise
• End-to-end deployment support
• VPN and private IP design
• Hardware selection
• Antenna design
• Monitoring services
• Troubleshooting
• Sector-specific solutions
• Managed connectivity bundles
• Independent advice across multiple platforms

In other words, smaller resellers may need to stop selling “SIM cards” and start selling “managed connectivity outcomes”.

That is the real shift.

The Future: SIM Reseller or Connectivity Integrator?

The traditional SIM reseller model is under pressure.

A customer does not really want a SIM.

They want:

• Their CCTV online
• Their EV charger connected
• Their PLC reachable
• Their meter reporting
• Their digital sign updated
• Their remote site monitored
• Their engineer able to access the router securely

The SIM is just one component.

SGP.32 may accelerate this change.

The companies that win will be those that can combine:

• eSIM profile control
• router expertise
• secure remote access
• diagnostics
• automation
• support
• application understanding

That may favour large providers.

But it also creates a strong opportunity for specialist providers who understand the real-world edge.

How to Build the Most Reliable IoT SIM Solution Today

If you are deploying IoT or M2M devices today, do not simply ask for a multi-network SIM.

Ask these questions instead.

SIM and Provider Questions

• Which networks are available?
• Is roaming steered or unsteered?
• Can I manually select or prefer a network?
• Can the provider perform SIM refresh?
• Can I see current network and PLMN?
• Can I see session history?
• Are there permanent roaming restrictions?
• Is private APN available?
• Is VPN access available?
• Is eSIM/eUICC supported?
• Is SGP.32 on the roadmap?

Router and Modem Questions

• Does the router support modem restart?
• Does it support SIM failover?
• Does it support cellular watchdogs?
• Can it force network reselection?
• Can it log PLMN changes?
• Can it report RSRP, RSRQ and SINR?
• Can it be managed remotely?
• Does it support VPN?
• Does it support external antennas?
• Is the modem suitable for the required bands and technologies?

Installation Questions

• Has the site been surveyed?
• Has each network been tested?
• Has the antenna been mounted in the best position?
• Has cable loss been considered?
• Has MIMO been installed correctly?
• Has the final application been tested?
• Has failover been tested?
• Has recovery been tested?

Monitoring Questions

• Can you see when the device last connected?
• Can you see which network it used?
• Can you see why it failed?
• Can you trigger remote recovery?
• Can you distinguish signal failure from APN failure?
• Can you alert before the customer notices?

Troubleshooting Flow: When an IoT Router Goes Offline

When a device goes offline, follow a structured process.

Device offline
        ↓
Is router reachable via management platform?
        ↓
Check cellular registration
        ↓
Check serving PLMN
        ↓
Check signal quality: RSRP, RSRQ, SINR
        ↓
Check APN/data session
        ↓
Check DNS and routing
        ↓
Check VPN tunnel
        ↓
Restart modem, not just router
        ↓
Force PLMN/network reselection
        ↓
Try manual network selection
        ↓
Fail over to backup SIM/profile
        ↓
Escalate to SIM provider with evidence

This is much better than blindly rebooting the router.

A reboot without diagnosis can hide the original fault.

Practical Recovery Table

Diagram Briefs for the Article

Diagram 1: The False Promise

Title: “The Multi-Network SIM Myth”

Visual:

Customer expectation:
Network A fails → SIM switches to Network B → Device online

Reality:
Network issue → modem stuck → PLMN not reset → same network retried → device offline

Use this as a simple comparison graphic.

Diagram 2: Full Reliability Stack

Title: “Reliable IoT Connectivity Is a Stack”

Layers:

1. Application
2. Router/gateway
3. Modem
4. SIM/eSIM profile
5. PLMN/network selection
6. APN/private IP/VPN
7. Monitoring platform
8. Support process

Diagram 3: SGP.32 Future Model

Title: “From Roaming SIM to Managed eSIM Profiles”

Flow:

IoT Device with eUICC
        ↓
SGP.32 IoT Profile Management
        ↓
Profile A / Profile B / Local Profile
        ↓
Secure APN and VPN
        ↓
Monitoring and policy control

Diagram 4: Troubleshooting Decision Tree

Title: “What To Check When an IoT SIM Goes Offline”

Flow:

Offline → Signal? → Registered? → Data session? → PLMN? → DNS? → VPN? → Modem reset? → Network reselection? → Backup SIM?

The Bottom Line

Multi-network IoT SIM cards are valuable.

They improve coverage options.

They reduce dependence on a single operator.

They can make deployments simpler.

They can improve resilience.

But they are not magic.

A multi-network SIM does not guarantee that the modem will choose the right PLMN. It does not guarantee that the router will reset the modem properly. It does not guarantee that ping reboot will recover a stuck session. It does not guarantee that a steered roaming profile will select the best network at a specific site. It does not guarantee that the customer will know what went wrong.

Reliable IoT connectivity requires a complete design.

The right SIM.

The right router.

The right modem.

The right antenna.

The right APN.

The right watchdog settings.

The right monitoring.

The right recovery process.

And increasingly, the right eSIM management platform.

Final Question: Is SGP.32 the Answer?

SGP.32 may become one of the most important developments in IoT connectivity.

It gives the industry a better way to manage eSIM profiles remotely across devices that cannot rely on consumer-style QR codes or manual setup.

It could help solve permanent roaming problems.

It could reduce physical SIM swaps.

It could allow better regional profile control.

It could give customers more flexibility across the life of a device.

But it may also shift power towards the companies that control the eSIM profile management platforms.

Large networks and global IoT connectivity providers may gain even more control over profile orchestration, operator selection, diagnostics and lifecycle management.

Smaller resellers will need to adapt.

The winning providers will not be those who simply resell data.

They will be those who understand the full connectivity stack and can deliver reliable outcomes.

Because in IoT, the customer does not really want a SIM card.

They want the device to stay online.

And when it does not, they want somebody who can actually fix it.