Equinix Sets Late-2026 Fabric One Beta for AI and Multicloud Links
The planned service would put a managed orchestration layer over connections among enterprise systems, clouds and AI environments. The key test is whether it can turn broad customer requirements into dependable routing, security and recovery controls.
Listen to this story
The audio brief
Story brief
3 key pointsEquinix’s Fabric One roadmap would make cross-environment connectivity an outcome-based managed service: customers specify what must connect and the constraints, while Equinix assembles routing, cloud links, encryption, resiliency and failover. The service is not available yet; beta is targeted for late 2026, with North American general availability in 2027. Its use of OpenAPI 3.0 Interconnect could ease...
- 01
Fabric One is planned for late-2026 beta and 2027 general availability, initially limited to North America.
- 02
Requests could arrive through a portal, API, automation workflow, agent, or natural-language prompt.
- 03
Equinix says its exchange reaches 10,500-plus businesses and roughly 3,000 cloud and IT providers.
Equinix is planning to make a hard-to-assemble layer of AI infrastructure a managed service. Its Fabric One product is designed to connect enterprise, cloud, network and AI environments after a customer states the required outcome, rather than requiring teams to configure each connection themselves.
Equinix introduced Fabric One on September 2 at its Horizon customer and partner event. The company expects a beta later in 2026 and plans general availability in 2027, initially in North America. It is a roadmap for a future service, not an automation product customers can use today.
The proposed control layer
Fabric One’s model is to accept a connectivity request through a portal, API, automation workflow, agent-based request or natural-language prompt. Equinix intends the service to translate those requirements into a single managed configuration, orchestrating routing, cloud connectivity, encryption, resiliency and failover.
That separates the request from the underlying network work. Customers would describe what needs to connect and the conditions for doing so; Equinix would be responsible for selecting and managing the connections required to meet those conditions across distributed environments.
A standard with cloud adoption
Fabric One will use the open-source OpenAPI 3.0 Interconnect specification, developed with collaboration from AWS and Google Cloud. That gives Equinix a common interface for its planned managed layer rather than a proprietary connection format.
The specification is already appearing in cloud connectivity products. AWS said Oracle Cloud Infrastructure adopted the specification in public preview in May, before AWS made its OCI multicloud Interconnect generally available on July 29. AWS said customers can create that service through its console, command-line interface or API, and expected Microsoft Azure support later in 2026.
Scale is the starting point, not the proof
Equinix says its exchange connects more than 10,500 businesses and about 3,000 cloud and IT providers. It also says eight of the top 10 AI model providers and nine of the top 10 neoclouds have active deployments there, giving the proposed service a large existing pool of potential endpoints.
The execution question comes when Fabric One reaches beta: whether Equinix can reliably deliver its intended encryption, resiliency and failover controls alongside cloud and network connections across those distributed environments.
Sources
- prnewswire.comEquinix Unveils Equinix Fabric One, Redefining How Enterprises Connect Across AI, Cloud and Networking Infrastructure
- newsroom.equinix.comEquinix Unveils Equinix Fabric One, Redefining How Enterprises Connect Across AI, Cloud and Networking Infrastructure
- aws.amazon.comAWS announces AWS Interconnect - multicloud connectivity with Oracle Cloud Infrastructure in GA - AWS