What to Ask About Global IoT Coverage by Market

Every global IoT provider will tell you they have "worldwide coverage." Most brochures show a world map with connectivity lit up in nearly every country, often citing 180 or more markets. But when your devices ship to sites in Chile, Vietnam, and rural Norway on the same rollout, that map is not the answer you need.

Cellular IoT Connectivity / Cellular Networks / Low Power Wide Area Networks (LPWAN) |
Nine Com4-branded IoT icons in a 3×3 grid — router, gauge, robotic arm, smart home, globe, satellite, smart lock, connected vessel, and SIM card — set in Com4 green and white on a Nordic Blue background.
There are roughly 4 billion cellular IoT connections in service globally as of 2025, running across more than 800 mobile network operators. No single provider owns a direct relationship with all of them. The real question is what happens in each market, one at a time. A provider might have strong direct presence across Western Europe and North America, and lean on a single roaming partner for all of Southeast Asia. Technically "covered," but with very different performance, cost, and support behind the scenes.

For enterprise IoT teams evaluating multinational service providers, the useful comparison is not who has more countries on the map, but who can prove what they deliver in the markets you actually operate in.

Here are eight questions worth asking before you sign anything.

1. Which markets do you own the relationship in, and which do you resell?

A global network coverage claim usually rests on a mix of directly negotiated operator agreements and reseller layers. The two are not equivalent. Where a provider owns the operator relationship, they can influence pricing, escalate faults inside minutes, and adjust commercial terms. Where they resell through a partner, the response chain has two or three extra links, and the commercial flexibility is thinner.

Ask for the list of markets where the provider holds direct agreements, and the ones where the service passes through an intermediary. 

2. What is the local network profile in each market I care about?

International service availability is not one number. In each country, ask about the operators the SIM steers to, the technologies supported (2G, 4G, LTE-M, NB-IoT, 5G), and the sunset dates for older technologies. In the United States all three major carriers completed their 2G and 3G shutdowns by December 2022. In Europe, most operators have set 2G sunset dates between 2025 and 2033, and 3G is largely gone. LTE-M and NB-IoT are available in roughly 130 countries, but with major gaps across Africa and South America.

If your devices depend on 2G, that timeline is the difference between a five-year deployment and a two-year one. A serious provider will send you a per-market data sheet without hesitation. If they hedge, that is the answer.

3. Are the SIMs local, roaming, or eSIM with local profiles?

Coverage in a market can be delivered several ways, and the model has real consequences. Permanent roaming is convenient but restricted or outright banned in at least a dozen countries, including Brazil (Anatel enforces a 90-day cap), Turkey, the UAE, Saudi Arabia, India, Argentina, and Vietnam. A local SIM or an eSIM with a local profile solves that, but only if the provider actually has a local footprint or a partner that does.

Ask how coverage is delivered in each of your markets, and what happens if the regulation changes mid-contract.

In practice: MedThings. Com4 provides eSIM connectivity for MedThings' smart medication dispensers. eSIM with the right local profile means the same device can ship into different markets without swapping hardware, and stays compliant as regulation around permanent roaming shifts.

 

4. What are the throughput, latency, and reliability commitments per market?

Worldwide provider coverage is a floor, not a promise. What you want is a commitment tied to your use case. LTE-M gives you around 300 kbps at typical latencies of 100 to 500 ms. NB-IoT is designed for a few kilobits per second and can be more than a second away from the network on wake. 4G LTE delivers tens of megabits per second. 5G stand-alone slicing brings latency to single-digit milliseconds where it is available. Uptime targets should be written per region, not as one blanket global figure.

A logistics tracker sending 200 bytes a day tolerates a lot. A connected medical device or a construction site's safety system does not. Push for numbers that reflect the market and the workload, not a general "carrier-grade" line.

In practice: ZetaDisplay. ZetaDisplay runs digital signage across more than 120,000 installations in 50+ countries, including the 128 m² display at Oslo Central Station, the largest in Europe. A frozen screen is an immediate, visible failure. Com4's cellular connectivity keeps those displays online in real time, with instant SIM activation and remote diagnostics. Blanket "global SLA" language would not have been enough.

5. How is billing handled across markets, and what does a per-country cost look like?

Global contracts often obscure the fact that costs vary widely by country. Data in one market can be five to ten times the price of a neighbouring one. If you are budgeting for a multi-country rollout of 5,000 or 50,000 SIMs, you need visibility per market: pooled or unpooled data, overage rates, and any local surcharges.

Ask for a sample invoice covering the countries in your plan. If the answer is a flat rate that sounds too clean, ask what that rate includes when a device roams into an adjacent market.

6. Where do your support and NOC teams sit, and in what languages?

When a fleet of devices in Germany goes silent at 3 a.m., the support experience is decided by where the team is, what hours they cover, and whether they can talk to the local operator directly. Multinational service providers vary widely on this. Some centralize everything in one region. Others run follow-the-sun operations across three or four regional NOCs. A P1 incident response commonly runs 15 to 30 minutes on the best contracts, and can stretch to several hours on the worst.

Ask about hours, languages, and the escalation path into each market's operators. A partner who has been through a real incident in your target country is worth more than one who has only read the routing tables.

In practice: Gomero. Gomero uses Com4 connectivity to collect grid and infrastructure data across more than 100 companies in 9 countries. Coordinating that many endpoints across that many markets is not a coverage-map exercise. It depends on a support team that can reach the right operator in the right country, quickly.

7. How do you handle regulatory and compliance requirements per country?

Data residency rules, lawful interception requirements, permanent-roaming restrictions, and eSIM regulation all differ by country, and they change often. GSMA counts at least 14 countries with active permanent-roaming restrictions, and the list is growing. GDPR and its equivalents in the UK, Switzerland, and Brazil (LGPD) shape where data can flow. A market coverage comparison that ignores compliance is incomplete. In some countries the provider must maintain a local entity or hold specific licenses. In others, encryption or data-export rules will shape your architecture.

Ask which countries in your rollout carry regulatory constraints, how the provider stays on top of changes, and who is on the hook if a rule shifts mid-deployment.

8. Can you show a customer running the same profile I need, in these markets?

Reference cases speak louder than coverage maps. If a provider claims strong service in a market, ask to speak with a customer of similar scale, doing similar work, in that same country. Not a brochure quote. A real conversation.

A partner confident in their global service provider coverage will connect you. If the references only exist for one or two headline countries, that is what the coverage really looks like.

The point behind all this

Global IoT rollouts tend to fail quietly. A device fleet works everywhere until it does not, and the gap between "covered on the map" and "supported in practice" is where the surprises live. Industry surveys have consistently placed IoT project failure rates at 30 percent or higher, with connectivity issues among the top three causes. Asking these questions early moves the conversation from marketing language to something you can hold a provider to.

At Com4 we build our answers to these questions into the way we work. Direct operator relationships across Europe and beyond, access to more than 750 mobile networks across 165 countries through the Wireless Logic group, 25 million connected devices under management, local SIM and eSIM options where regulation demands them, and Nordic support teams who know the operators personally. If you're evaluating international service availability for a multi-country deployment, we're happy to walk through your specific markets and share what we see.

Northern-light-sky
START YOUR JOURNEY TODAY

Stay up to date with the latest news and developments in Com4 and IoT industry