7 IoT Myths That Just Won’t Die (and What’s Actually True)

Some ideas refuse to stay buried.

The IoT industry has changed dramatically over the last decade. Networks have evolved. SIM technology has changed. Satellite connectivity is becoming part of the mix. Devices are being deployed farther from where anyone can reach them, and are expected to stay in the field for years.

Yet some of the same assumptions keep showing up in planning meetings, RFPs, and product roadmaps.

As if they were written in 2012 and never revisited.

This Halloween, we’re putting seven of them to rest.

Myth 1: “One carrier is enough.”

Why it won’t die: It’s simple. One contract, one relationship, one bill. And in the pilot, everything worked.

What’s actually true: Pilots happen in controlled environments. Deployments happen everywhere.

Relying on a single network means relying on one coverage footprint and one network dependency. When that network has a gap, an outage, or a change in strategy, your devices may be along for the ride.

That’s a problem when your fleet operates across regions, countries, or environments where coverage isn’t consistent.

Connectivity should be able to adapt across networks as your deployment changes.

And multi-network doesn’t have to mean multi-contract. One SIM and one provider relationship can still give your fleet access to hundreds of networks.

One network might be enough for a pilot. It shouldn’t have to define the life of your fleet.

Myth 2: “Connectivity is a commodity.”

Why it won’t die: From the outside, every SIM looks roughly the same. It’s a chip that moves data. So the buying decision becomes price per megabyte.

What’s actually true: Connectivity touches every device you own, every time it’s online.

That makes the connectivity layer more than a pipe for data.

It’s where you can understand what’s happening across your fleet. Where you can enforce policies. Where you can control access. And where you can respond when something changes.

Connectivity isn’t just what gets your device online. It’s what lets you manage what happens next.

Treat connectivity as a commodity, and you’re underusing some of your most useful infrastructure.

Myth 3: “The cheapest SIM is the cheapest option.”

Why it won’t die: The data rate is the line item procurement sees.

Everything else tends to show up later, in someone else’s budget.

What’s actually true: The real cost of IoT connectivity isn’t just the data.

• It’s the truck roll when a device needs attention.
• The downtime when a device can’t connect.
• The engineering hours spent troubleshooting without enough visibility.
• The unused SIMs nobody remembered to cancel.
• And, in some cases, the cost of replacing hardware because the connectivity strategy couldn’t adapt.

A cheaper data rate can easily become the more expensive decision over the life of a device.

Don’t price connectivity by the first invoice. Price it over the life of the fleet.

Myth 4: “Once it’s deployed, it’s done.”

Why it won’t die: Deployment feels like the finish line.

The devices are shipped. They’re installed. They’re reporting.

Project closed.

What’s actually true: Deployment is day one of a lifecycle that can run for ten years or more.

During that time, networks change. 2G and 3G shutdowns have already left some devices unable to connect. Servers move. Markets open. Security requirements evolve. Business priorities shift.

A fleet that can’t adapt after deployment has a shelf life, even if the hardware doesn’t.

That’s why over-the-air (OTA) connectivity management matters.

Depending on the device and its capabilities, remote management can support connectivity changes, eSIM profile updates, and other controls without physically accessing every device.

The goal is to keep a fleet reachable and manageable as its environment changes, without sending someone into the field every time connectivity needs attention.

Your device may stay in the field for ten years. Your connectivity strategy shouldn’t be frozen on day one.

Myth 5: “A global roaming SIM works everywhere, forever.”

Why it won’t die: “Global SIM” sounds like it solves everything.

Put one in every device. Ship worldwide. Done.

What’s actually true: Global roaming can be powerful, but “global” doesn’t mean permanent.

Markets have different requirements. Roaming agreements and operator policies can change, and some countries restrict permanent roaming. Coverage changes. Operators retire technologies. A device expected to stay deployed for years can’t assume today’s connectivity environment will still exist tomorrow.

The answer isn’t simply “roaming” or “no roaming.”

It’s flexibility.

A global deployment needs a connectivity strategy that accounts for local requirements and can adapt to different networks and conditions as those requirements change.

Global shouldn’t mean “works today.” It should mean “built to adapt.”

Myth 6: “Satellite IoT is a someday technology.”

Why it won’t die: For years, satellite connectivity meant specialized hardware, large antennas, and large bills.

That reputation stuck.

What’s actually true: Satellite IoT is evolving, and it’s already a viable option for some deployments.

3GPP-standardized non-terrestrial network (NTN) technologies are enabling cellular IoT connectivity via satellite, extending coverage to places traditional cellular networks can’t reach, including remote infrastructure, oceans, and areas beyond the last cell tower.

That doesn’t mean every cellular IoT device can connect directly to a satellite. Support depends on the device, modem, satellite service, coverage, and use case.

But for the right deployment, satellite isn’t just a future backup plan.

It’s another connectivity option to plan for now.

As devices operate across cellular and satellite coverage, the bigger question becomes how easily those connectivity options can work together.

Myth 7: “IoT security is the device maker’s job.”

Why it won’t die: The device is the thing that gets hacked, so the device must be where security lives.

What’s actually true: Devices matter. But they can’t do it alone.

Especially when you’re dealing with devices that were deployed years ago, can’t easily be updated, or are sitting in places nobody can physically reach.

The connectivity layer has a role to play too.

It can help establish device identity, control where devices connect, enforce network access policies, provide visibility into fleet behavior, and give teams a way to respond when something goes wrong.

That doesn’t replace device or application security. It adds another layer of protection around the connected system.

Security isn’t one product or one layer.

And connectivity shouldn’t be the layer everyone forgets.

The Monogoto POV: Retire the myths, not the devices

Every one of these myths comes from the same outdated idea:

Connectivity is something you buy once and stop thinking about.

But devices don’t work that way.

They live for years. They cross borders. Networks change around them. Business requirements change. Security threats evolve. New connectivity options appear.

So why should connectivity be treated like a static decision made before a device ever leaves the warehouse?

At Monogoto, we believe connectivity should be software-defined: adaptable, visible, and controllable throughout the life of your fleet.

That means giving organizations the ability to:

• Adapt: Connect across networks and connectivity types as deployment needs change. Monogoto connects devices across 550+ networks in 200+ countries, with cellular and satellite connectivity options.
• See: Understand what’s happening across the fleet, not just whether a device says “online.”
• Control: Manage connectivity and respond remotely throughout the device lifecycle, using supported over-the-air capabilities to reduce unnecessary truck rolls.
• Scale: Expand into new markets and environments without rebuilding the connectivity strategy from scratch.

The devices you deploy today will outlive many of the assumptions behind them.

Networks will change. Markets will shift. Security requirements will evolve. Your connectivity needs to keep up.

Frequently Asked Questions

What are the most common IoT connectivity myths?

Common IoT connectivity myths include the idea that one carrier is always enough, connectivity is a commodity, the cheapest SIM is always the cheapest option, that deployment is the finish line, a global roaming SIM will work everywhere indefinitely, satellite IoT isn’t ready yet, and security is only the device maker’s job.

Is one carrier enough for IoT?

One carrier can work for some deployments, but relying on a single network creates a single connectivity dependency. Multi-network connectivity can give IoT deployments more flexibility as coverage, markets, and network conditions change.

Is IoT connectivity a commodity?

No. Connectivity can provide more than data transport. It can also support device identity, visibility, policy enforcement, and remote control. For large or long-lived fleets, those capabilities can have significant operational value.

Why does OTA matter for IoT?

IoT devices can remain deployed for many years while networks, infrastructure, and business requirements change. Over-the-air management, including remote eSIM (eUICC) profile changes, can allow organizations to adapt connectivity and configuration remotely without physically accessing every device.

Can satellite connectivity be used for IoT today?

Yes. Satellite IoT and non-terrestrial networks can extend connectivity to locations where traditional cellular coverage is unavailable. The right approach depends on the device, use case, hardware, network, and coverage requirements.

Is IoT security only the device manufacturer’s responsibility?

No. Device security is important, but IoT security also involves identity, connectivity, network access, visibility, and the ability to respond when something changes. A defense-in-depth approach addresses multiple layers of the connected system.