International IoT Day: From Idea Exchange to Critical Infrastructure

Each year in April, International IoT Day offers a moment to reflect on how the Internet of Things is evolving. It is not only about new ideas, but about what has proven to work in real deployments.

What began in 2010 as an initiative by the IoT Council to encourage discussion around emerging technologies has grown into a global movement. Today, it is recognised across hundreds of locations worldwide, from universities and meetups to industry events and online communities. More importantly, it has become a point of reference for the industry to assess progress in practical terms.

In 2026, one theme is clear. Connectivity has moved to the centre of the IoT value chain.

IoT has matured and connectivity is no longer a commodity

In the early stages of IoT, the focus was straightforward. Connect devices, collect data and demonstrate value. Connectivity played a key role, but it was often treated as a background function.

That is no longer the case.

Deployments today operate at a very different scale. Organisations are managing thousands and often millions of devices across multiple countries, networks and regulatory environments. In this context, connectivity has a direct impact on performance, data integrity and operational continuity.

There is little tolerance for disruption. Even minor connectivity issues can lead to service interruptions, financial consequences or operational risk.

The conversation has shifted. It is no longer about simply connecting devices. It is about ensuring they remain connected, securely and reliably, over time.

Connectivity must now provide:

• Resilience across networks and regions
• Consistent performance under changing conditions
• Security aligned with operational requirements
• Control across the full device lifecycle

IoT connectivity is no longer a supporting layer. It is part of the infrastructure on which operations depend.

IoT eSIM and SGP.22: enabling scalable deployments today

One of the technologies supporting this shift is IoT eSIM, based on the GSMA SGP.22 specification.

SGP.22 introduced remote SIM provisioning, allowing operator profiles to be delivered and managed over the air. This removes the need to physically access devices to change connectivity, which has traditionally been a limitation in large deployments.

In practical terms, this changes how IoT is deployed.

Devices can be manufactured and shipped globally with a single SIM. Connectivity can then be configured remotely based on location, commercial requirements or operational needs. This reduces complexity and allows deployments to scale more efficiently.

This approach enables:

• Zero-touch provisioning at scale
• Lower operational costs linked to SIM logistics
• Faster rollout across multiple regions
• The ability to optimise connectivity over time

SGP.22 is now widely used across sectors where reliability and scale are essential, including EV charging, smart metering, industrial automation and logistics. It provides a stable and proven framework for managing connectivity in live environments.

For a deeper technical perspective on how IoT eSIM is shaping connectivity models, this International IoT Day 2026 analysis provides additional context.

SGP.32: moving towards more automated connectivity management

While SGP.22 supports today’s deployments, the next phase of IoT evolution is already emerging.

SGP.32 has been designed for environments where devices operate independently and often without user interaction. These deployments typically involve remote locations, constrained devices and long operational lifecycles.

The focus shifts towards automation.

SGP.32 introduces:

• A more centralised approach to provisioning
• Greater automation across the connectivity lifecycle
• Reduced reliance on device-side processes
• More efficient management of large device fleets

This is particularly relevant where manual intervention is not practical.

SGP.32 does not replace SGP.22. The two standards are complementary. SGP.22 continues to support current deployment models, while SGP.32 introduces capabilities that will become increasingly important as IoT scales further.

Together, they provide a clear path towards more efficient and adaptable connectivity management.

Why the connectivity model now defines success

As IoT becomes embedded in critical operations, the way connectivity is delivered is under closer scrutiny.

Organisations are no longer selecting providers based only on coverage or pricing. They are looking for consistency across regions, greater visibility and stronger control over how devices connect and behave.

This has brought attention to the underlying connectivity model.

Providers with direct access to mobile network infrastructure are generally better positioned to deliver consistent performance. They can offer greater control over routing, faster response when issues arise and improved long-term reliability.

By contrast, models that rely entirely on third-party agreements can introduce variability, particularly at scale. As deployments grow, these differences become more visible and more important.

International IoT Day as a measure of industry progress

International IoT Day has evolved alongside the industry it represents.

What began as a platform for discussion has become a reflection of execution.

In 2026, IoT is no longer defined by how many devices are connected, but by how well those devices remain connected over time.

IoT eSIM, through SGP.22 today and SGP.32 in the near future, plays a central role in this transition. It enables more flexible and scalable connectivity models that can adapt as deployments evolve.

A clear direction for the future of IoT

The next phase of IoT will not be defined by the availability of connectivity, but by how well that connectivity performs in real-world conditions.

As deployments expand across regions, networks and use cases, the focus is shifting towards consistency, control and long-term adaptability. Connectivity must work reliably across different environments, remain secure throughout the device lifecycle and adapt as requirements change.

In this context, success will depend on execution rather than access. Ultimately, the defining factor will be whether connectivity works as expected, consistently, securely and globally, without compromise.