Official side event of

Sponsored by

Held · September 2026

The first impartial end-to-end interoperability test on a live network.

The plugfest has taken place. Over two days in Amsterdam, independent eIMs, eUICCs and IPA implementations met on a live network — not in a lab — to measure what actually works across vendors.

Amsterdam · two days · side event of The Things Conference

The purpose

Why it was run

Every vendor can claim SGP.32 compliance. That does not show whether their products work together.

SGP.32 is sold as the standard that ends lock-in and makes IoT connectivity portable. A self-declared compliance badge tells a buyer nothing about whether one vendor's eIM can manage another vendor's eUICC in the field.

Until this plugfest, nobody had measured that independently. The test is done. The full dataset — passes named, failures aggregated, methodology published — comes out in November.

Compliance vs. interoperability

Self-declared compliance. A vendor tests its own stack and marks the box.
Bilateral demos. Two partners who already work together show it works.
Impartial cross-vendor testing. A neutral coordinator measured every combination. The report names the passes and aggregates the failures.

What was done

Twenty-two cells, and nobody played at home.

Four eIMs, four eUICCs and two module-side IPA platforms. Every cell crossed a company line and was set to run the same profile lifecycle, on both direct and indirect download paths.

  1. 01

    Bootstrap and first network attach

    Each device came on-network, and the baseline attach path was confirmed before any profile operation.

  2. 02

    Profile download — direct (HTTPS) and indirect (CoAP)

    Both download paths were exercised across vendor boundaries, and the result was recorded for each transport.

  3. 03

    Profile enable and multi-operator switch

    Downloaded profiles were enabled and switched between operators — the operations an enterprise fleet depends on.

  4. 04

    Rollback on failure

    Recovery was checked when a download or switch failed, with the result recorded for every cell.

  5. Block A

    IPAe cross-vendor

    Each independent eIM drove a profile into an eUICC it didn't make — the primary cross-vendor profile-management path.

  6. Block B

    IPAd implementations

    External eIMs drove the modem-side IPA path, including constrained-device behaviour and a direct-versus-indirect comparison.

The output

The first independently measured SGP.32 interoperability report.

The full matrix publishes in November 2026. The findings above are already public.

What comes next

  • 01

    The patterns, already shared

    Where the pairings stalled, and what a buyer should ask before a pilot. Linked from the notes above.

  • 02

    The independent dataset

    The cross-vendor result matrix: passes named, failures aggregated and never named, with the methodology published in full.

Notify me

Get the report when it publishes

One email when the independent interoperability report lands. No spam.

No spam. One email when the report publishes.

The position

SymbIoT convened the plugfest as the neutral coordinator — an impartial player that recorded every result and will publish the cross-vendor dataset so the market can trust what was measured.

Host The Things ConferenceConvened by SymbIoTSponsor IoT Stars

Frequently Asked Questions

What was the SGP.32 Interoperability Plugfest 2026?

It was the first impartial end-to-end SGP.32 interoperability test on a live network, not in a lab. Independent eIMs, eUICCs and IPA implementations were tested across vendor boundaries to measure what actually works. SymbIoT convened it as a side event of The Things Conference.

When and where was the Plugfest held?

Over two days in Amsterdam in September 2026, on a live network. It has already taken place. This page records what was tested and what was learned; a later stats page will publish sourced figures without vendor names or identifiers.

What was tested at the Plugfest?

Bootstrap and first network attach, remote SIM provisioning flows, and interoperability between independent eIMs, eUICCs and IPA implementations. The aim was to see which combinations work on a live network, not only in a vendor’s own lab.

Are vendor names published from the Plugfest?

Public figures use vendor types and neutral labels, not company or product names, module or eUICC identifiers, or other vendor identifiers. The tracker remains the place for public certification announcements; the Plugfest page explains the event and the method.

In Partnership With
Need Help?