What is a global data pool in IoT connectivity?

A global data pool is a shared allocation of mobile data that every SIM in a fleet draws from, instead of each SIM being capped at its own fixed limit. High-use devices pull from the headroom left by low-use devices, the pool works across borders, and the total is sized to the fleet's average usage rather than to any single device's worst case.

That is the short answer. The rest of this page covers how pooling actually works, where it saves money, where it does not, and how to size one for your own fleet.

11.03.2025 (updated 12.08.2026)

How a data pool works

Picture your SIM subscription as one shared account rather than a hundred separate ones. If each SIM in a fleet of 100 is allocated 5MB, a per-SIM plan gives you exactly that: 100 buckets of 5MB, no more. A pooled plan takes the same 500MB total and lets any SIM draw from it. A tracker that reports every five minutes uses more, a sensor that reports once a day uses less, and the fleet as a whole still lands inside the 500MB ceiling.

The pool is not unlimited. It is sized at setup, based on realistic average usage per SIM multiplied by the number of active SIMs, and it can be adjusted upward as the fleet grows. Usage against the pool, by individual SIM and in total, is visible in real time through IXT's Connectivity Management Platform, with threshold alerts before the pool runs low.

Why pool data instead of buying per-SIM plans

Per-SIM plans create a predictable failure mode at scale: some devices exceed their allocation and trigger overage charges, while others use a fraction of theirs and the difference is wasted. Neither problem shows up until the invoice arrives.

Pooling addresses both sides of that at once.

• Fewer overage charges. A device that has a heavier month draws from the shared pool instead of triggering a per-SIM overage fee, for most fleets with mixed or seasonal usage patterns.
• Less wasted allocation. Idle or low-traffic SIMs no longer sit on unused data that the fleet as a whole could have used.
• One line of visibility, not one hundred. Instead of monitoring individual SIM limits, a connectivity manager watches one pool level and gets alerted before it runs low.
• Works the same across borders. An IXT global data pool functions identically whether the SIMs using it are in Norway, Germany, or Singapore, across 600+ mobile networks in 190+ countries, so a fleet expanding into a new country does not need a new plan negotiated for it.

Data pool vs per-SIM data plans

Uniform, low-variance usage across a small fleet is the one case where a per-SIM plan can be just as simple to run. Once usage varies by device type, or the fleet spans more than one country, pooling is the more efficient allocation for most deployments.

What a data pool does not do

A data pool solves data allocation, not connectivity security or network performance. It is worth being precise about the boundary:

• If the pool is exhausted, every SIM drawing from it is affected until it is topped up. IXT does not automatically resize a pool mid-contract without a customer request, so realistic sizing at setup matters.
• Pooling does not change coverage. It does not add private networking, and it does not add the traffic visibility or anomaly detection that come with IXT SecureNet or IXT Zero Trust.
• An under-sized pool affects the whole fleet at once, which is a different failure mode to a single SIM running over its limit. Size the pool from real usage data, not a guess.

A real deployment

Pascal Technologies, a Norwegian maritime software company, runs a 5GB shared data pool across its AirHull vessel fleet. The pool covers OTA software updates and performance monitoring across vessels operating in different countries, on one predictable cost rather than a separate plan per vessel or per country. "The simplicity lets us focus on building better boats, not managing telecom contracts," says Jesper Hosen, Head of Software at Pascal Technologies.

How to size a data pool

1. Pull actual usage per device type from your current connectivity data, not the manufacturer's estimate. Real usage is almost always different from the spec sheet.
2. Multiply average usage per SIM by the number of active SIMs to get a starting pool size.
3. Add headroom for seasonal or event-driven spikes if your fleet has them, for example firmware update windows or usage tied to weather or demand.
4. Set threshold alerts well before the pool is exhausted, so there is time to act rather than react.
5. Review pool size at each significant point of fleet growth. A pool sized for 1,000 devices does not automatically scale itself to 5,000.

Frequently asked questions

What is a data pool in IoT connectivity?

A data pool is a shared allocation of mobile data that a group of SIM cards can all draw from, rather than each SIM being limited to its own fixed allowance. The pool total is the sum of the fleet's allocation, and usage moves flexibly between devices within that total.

How is a global data pool different from a shared data plan?

The terms are often used interchangeably. "Global" specifically means the pool works the same way regardless of which country the SIM is operating in, which matters for fleets deployed across more than one market.

Does pooling work across different countries?

Yes, for most global SIM providers, including IXT. The pool is not tied to a specific country's network; SIMs draw from the same pool wherever they are connected, across the provider's supported network footprint.

What happens if the pool runs out of data?

Every SIM drawing from that pool is affected until it is topped up. This is why realistic sizing at setup, and threshold alerts before the pool runs low, matter more with pooled data than with individual SIM plans.

Can I resize a data pool after it is set up?

Yes, pool size can be adjusted as a fleet grows, but this is typically a customer-initiated change rather than automatic. Build in a review point at each stage of fleet growth.

Is a data pool worth it for a small SIM fleet?

If usage is uniform and the fleet is small and single-country, a per-SIM plan can be simpler to run. Pooling starts to pay off once usage varies across devices or the fleet spans more than one country.

Does a data pool include security or private networking?

No. A data pool manages data allocation only. Keeping IoT traffic off the public internet requires a private networking layer such as IXT SecureNet, and traffic visibility or anomaly detection requires IXT Zero Trust.

Thinking about a data pool for your fleet?

If you are running multiple SIM cards and want a flexible way to manage data across them, get in touch. We can help you work out whether pooling fits your usage pattern and how to size one correctly from the start.

We're here to help you stay connected.