VodafoneThree and Ericsson announced on September 17, 2026 that the operator's upgraded cloud-native 5G core had gone live. The operator's announcement marks an operational step in a longer integration programme. For technology suppliers tracking such changes, PipeSignals offers a way to follow concrete delivery milestones alongside the contracts that preceded them.
Activation follows earlier network sharing
The new core brings 4G and 5G core functions onto Ericsson's cloud-native platform. VodafoneThree describes it as the second major phase of its network transformation, moving beyond the infrastructure-sharing stage. The statement does not say that all customer traffic has migrated or that the wider programme is finished.
There is an important distinction from Ericsson's May 28 announcement. That earlier milestone combined core-level and radio-network sharing while maintaining separate cores. September's announcement concerns the activation of an upgraded core, rather than another announcement of the same sharing arrangement.
The project itself is older. A 2025 operator release already described installation work and a planned staged migration. The latest news therefore records progress on a previously contracted system. It should not be presented as the first decision to invest in the technology.
The incumbent supplier is already named
In separate reporting on September 17, Mobile World Live placed the activation within the operator's wider investment programme and noted Ericsson's position as sole core-network supplier. Its account corroborates the new phase but does not independently measure network performance.
That supplier position matters commercially. An activation announcement is not an invitation to bid for the core platform. Any outside provider would need to identify work genuinely separate from the established delivery contract before treating this as a potential engagement. Neither cited September report announces an open competition for additional services.
The operator links the upgraded core to services using network slicing, which separates traffic into differentiated service arrangements. However, commercial service descriptions and promised performance are not the same as independent acceptance evidence for every site, application or customer. A prospective enterprise deployment would still need its own scope and requirements.
Questions for supporting technology providers
An application integrator could examine whether a customer's planned use case depends on a particular connectivity service. A testing specialist could look for an explicitly commissioned requirement to validate application behaviour under agreed conditions. A managed-service provider would need to establish support boundaries between the customer, the operator and existing technology partners.
These are conditional avenues for assessment, not confirmed purchasing needs. The sensible starting point is a documented operational problem and a named contracting organisation. General claims about improved connectivity are not enough to justify assuming a budget, a procurement window or an unfilled supplier role.
Further migration updates and published service requirements should make the next stage easier to assess. Readers can try PipeSignals to track those changes while keeping the newly reported activation separate from both the older contract and work still ahead.
