With Pureport's Multicloud Fabric, you can easily connect your cloud environments, data center locations, and main/remote branches, forming a fully meshed, private, any-to-any network... without needing a dedicated BGP routing specialist!

Our self-service console and robust API allows your IT generalist, DevOps team, or network specialists to quickly build (and maintain) private connectivity. There are no long-term contracts and you don't have to order physical circuits or cross-connects.

Pureport locations and backbone

Pureport maintains points of presence in several key locations, world-wide. With Multicloud Fabric, our software-defined networking platform, you can connect each location to cloud services (such as AWS, Google, Azure, and others) or your own, local site (such as a data center or branch office). 

Additionally, you can leverage our redundant, high-speed backbone to enable low-latency communication among connections in different Pureport regions.


The basic construct in the Pureport model is the Network, which is the control plane. After creating a network, you can add Connections to your cloud environments and physical locations. You can build a single network to connect all of your environments, or segment into separate networks for different applications, workloads, organizational units, or user groups.

All Connections added to a Network are fully meshed at Layer 3 via the BGP routing protocol. As a result, when you deploy Connections in different locations (or even in the same location), the connected environments can communicate directly with one another. Essentially, the Network itself doesn't have a "location." All Connections added to a Network can communicate directly with one another in an any-to-any fashion, avoiding the "hub and spoke" choke points often associated with deploying individual point-to-point connections.

For example, if you add an AWS VPC, an Azure Vnet, and a physical location via IPSEC, each is able to send and receive traffic directly to any of the others. As shown in the following illustration, connections attached to all three Locations (Seattle, San Jose, and Ashburn) can communicate directly with each other:

By default, the Pureport Network allows all traffic. Use the security settings within your cloud environments and on-premises firewalls to allow the traffic or control specific traffic types.

Customer connections

After creating a Network, you will add Connections for each environment to be able to communicate with each other. Pureport supports the following Connection types:

  • IPSEC tunnels for remote sites, using existing Internet connectivity
  • Physical ports to connect data center locations that are on-net with Pureport
  • AWS Direct Connect
  • Azure ExpressRoute
  • Google Cloud Interconnect

High availability

All Connections are Highly Available (HA) by default unless you select a Non-HA option (only available for select connection types and speeds). They include redundant network paths through redundant equipment. For each new HA Connection added to your Network, two routing gateways are deployed across separate, redundant nodes on our platform and connected via redundant, high-capacity switches.

For workloads or applications that do not require High Availability, Pureport offers a limited selection of connection types and speeds without HA at a reduced cost. You may consider these for workloads where up-time is not essential, such as a development projects. For most connections however, HA is mandatory and cannot be disabled in the console or via the API.

Regardless of your specific connections, the Network itself and Pureport's platform in general are always HA to ensure maximum up-time. Pureport maintains redundant Internet connections, redundant backbone connections, and redundant private connections to the cloud providers (such as AWS Direct Connect) as well as high-capacity routing and switching engines in each of its core locations. This enables you to build connectivity between sites and clouds and be assured of uptime and availability.