July 2026 was the busiest month SGP.32 has had. For most of its life the GSMA’s IoT eSIM standard was something the industry talked about rather than shipped. That has changed, and July was the clearest sign yet: a major connectivity platform moved to full commercial availability, a group of incumbent operators proved multi-operator orchestration across a region, one of the leading eIM vendors threw its testing tools open to the market, and the specification itself quietly moved forward. Here is the month in review, and what it means if you are planning an IoT deployment.
Soracom moved SGP.32 to full commercial availability
The headline commercial event of the month was Soracom taking its SGP.32-compatible IoT eSIMs and its Connectivity Hypervisor orchestration capability from pre-order to general availability. Both are now on sale, in card and chip form factors, which marks the point where Soracom’s SGP.32 offering stopped being a roadmap item and became something you can buy.
Two details matter for anyone evaluating it. First, Soracom’s implementation is built on the standard SGP.32 building blocks – eUICC, eIM and SM-DP+ – rather than a proprietary variant, which is what you want to see for interoperability. Second, the Connectivity Hypervisor is designed to manage connectivity from multiple operators through a single control plane, though Soracom has been clear that broader multi-operator availability depends on partner operators completing their profile integrations. In other words, the mechanism is built and the platform is live, and the ecosystem around it is still filling in. That is a fair summary of SGP.32 as a whole right now.
Soracom is the first platform of its scale to reach this point since Telenor IoT began commercial SIM delivery in April. For the wider timeline of who reached commercial first, see our breakdown of who went first with SGP.32 commercial deployments.
Bridge Alliance and Thales proved multi-operator orchestration in Asia Pacific
If Soracom was the commercial milestone, the Bridge Alliance initiative was the interoperability one. Member operators AIS, Globe Telecom, Optus and Singtel completed testing of a multi-operator enterprise eSIM connectivity platform for IoT, built around SGP.32, with Thales providing the orchestration layer. The target is cross-border IoT across Asia Pacific, where a device might ship once and then need its connectivity managed for years across several markets and operators.
The significance is not that eSIM exists. It is the combination of the SGP.32 standard, several incumbent operators, and a shared orchestration layer aimed squarely at enterprise deployments that cannot be handled one country at a time. That is the model the whole standard was designed to enable. We covered this one in full when it landed: Thales, Singtel and Bridge Alliance launch multi-operator IoT eSIM.
Kigen opened up its IoT eSIM Starter Kit
The third big move was about lowering the barrier to entry. Kigen opened access to its IoT eSIM Starter Kit for businesses wanting to test SGP.32 provisioning in real conditions. The kit bundles ten certified Kigen eSIMs, access to Kigen’s eSIM IoT Manager (eIM) and its Pulse platform, device-side development tools, three months of evaluation access, and profiles from more than a dozen connectivity partners ready to activate.
Alongside it, Kigen signalled that more MNOs and MVNOs are finalising streamlined profile activation workflows on its platform, which steadily widens the pool of connectivity you can attach to a single eSIM foundation. The practical effect is a much shorter path from curiosity to pilot: an OEM or enterprise team can now evaluate what SGP.32 actually does before committing to a production design. We looked at this in detail in Kigen’s IoT eSIM Starter Kit: SGP.32 gets a proving ground.
The specification quietly moved to v1.3
Amid the commercial noise, the standard itself advanced. On 28 May 2026 the GSMA published SGP.32 v1.3, alongside a matching SGP.31 v1.3 architecture update. It has taken until now for that to filter through into market awareness, and there is an important nuance: formal certification is still issued against v1.2, so most vendor documentation and explainer pages continue to reference it. The two versions will coexist for a while.
For anyone designing hardware or evaluating vendors today, that means v1.2 remains the version to certify against and design around, which is why our guide to the current SGP.32 v1.2 specification is still the practical reference. Treat v1.3 as the direction of travel rather than the version your certification questions should be about, at least until conformance programmes catch up.
The bigger picture: momentum, but not yet a finished ecosystem
Put the month together and a pattern emerges. SGP.32 in July 2026 is genuinely commercial, genuinely multi-vendor, and no longer dependent on any single operator or platform. Soracom’s availability, the Bridge Alliance multi-operator work, and Kigen’s testing tools all point the same way: the standard has crossed from pilot into production.
The honest caveats still apply. Cross-vendor interoperability – a different eUICC operating system, an eIM from a second vendor, and an SM-DP+ from a third – is still being validated in the field rather than assumed. Not every cellular module vendor has SGP.32-native hardware certified in volume. And enterprise tooling to fold eIM management into existing device platforms is still maturing. The GSMA’s forecast of roughly 195 million SGP.32 profile downloads by 2029 remains the trajectory, but the acceleration has always been an H2 2026 and 2027 story, and nothing this month changes that timeline.
For UK teams, the relevance is direct. A multi-operator market, the ongoing 2G and 3G sunsets, and long-life infrastructure in energy, utilities and transport are exactly the conditions SGP.32 was built for. If you are weighing it up, the starting points are what SGP.32 is, how it compares to SGP.02 and SGP.22, and, when you get to procurement, how to choose a bootstrap provider. For the broader regional context, our sister site covers the UK and European SGP.32 state of play.
July 2026 SGP.32 news at a glance
| Date | Development | Why it matters |
|---|---|---|
| 8 July | Soracom SGP.32 IoT eSIMs and Connectivity Hypervisor reach general availability | First platform of its scale to full commercial sale since Telenor |
| Mid July | Bridge Alliance operators (AIS, Globe, Optus, Singtel) complete multi-operator testing with Thales orchestration | Proof of cross-border, multi-operator SGP.32 at regional scale |
| Late July | Kigen opens IoT eSIM Starter Kit; more MNOs and MVNOs finalise profile workflows | Shortens the path from evaluation to pilot for OEMs and enterprises |
| Ongoing | SGP.32 v1.3 (published 28 May) filters into awareness; certification still tracks v1.2 | Design and certify against v1.2 for now; v1.3 signals the direction |
Frequently asked questions
What is the current version of SGP.32?
The GSMA published SGP.32 v1.3 on 28 May 2026, but formal certification is still issued against v1.2. In practice v1.2 remains the version to design and certify against, while v1.3 indicates where the standard is heading.
Is SGP.32 commercially available in 2026?
Yes. Commercial SGP.32 offerings are live from providers including Telenor IoT (from April 2026) and Soracom (generally available from July 2026), with a growing ecosystem of certified eUICC, eIM and SM-DP+ components behind them.
What was the biggest SGP.32 news in July 2026?
The standout events were Soracom moving its SGP.32 IoT eSIMs and Connectivity Hypervisor to general availability, the Bridge Alliance and Thales multi-operator orchestration testing across Asia Pacific, and Kigen opening its IoT eSIM Starter Kit to the market.
Written by Peter Green. This round-up reflects the state of the SGP.32 market as of the end of July 2026 and will be updated as the ecosystem develops. Sources: IoT Business News; Morningstar / Business Wire; IoT Now; IoT For All; GSMA eSIM specification pages (SGP.32 v1.3, published 28 May 2026); company announcements from Soracom, Thales, Bridge Alliance and Kigen.