Private Connectivity
Connect to the cloud reliably and privately. Private Connectivity uses a carrier circuit to create a private connection between the cloud and your infrastructure on premises or in a colocation environment.
Extend your on-premises networks to the cloud
Make your cloud connections reliable and secure
Connections don't route through the public internet. Traffic between your on-premises network and your cloud virtual networks passes through your own cloud gateway.
Use a private path for backup and recovery traffic
Set up a fixed, off-internet path between your own datacentre and the cloud, a good option for scenarios such as database replication and backup traffic.
Extend and connect your datacentres
Multi-branch organisations with an existing MPLS network connect the cloud as one more end of that network.
Build hybrid applications
Where policy says application traffic must not cross the internet, run applications that span on-premises infrastructure and the cloud over the private connection.
Example scenarios
A multi-branch organisation adding the cloud to its MPLS
The existing MPLS network connects the cloud as one more end. The circuit is terminated in the data center network and plugged straight into the organisation’s cloud gateway.
A bank team keeping backup traffic off the internet
Database replication and backup traffic reach the cloud on a fixed path that never touches the internet. Company policy routes application traffic the same way.
A network team announcing its own routes over BGP
BGP neighbours and IP prefix lists are set on the provider gateway dedicated to the organisation. Site-to-Site VPN waits on the same gateway as an extra path.
Securely connect to the cloud, without using the public internet
Private cloud connections
Connect your on-premises network to the cloud, ensuring a private and secure pathway for your data. The circuit is terminated in the data centre network by the team that runs the cloud and connected straight to your cloud gateway.
Increased reliability
The cloud gateway runs active/standby, so a gateway node failure does not cut the circuit. An organisation can have more than one private circuit.
Static or dynamic routing
By default your remote networks are defined as static routes on the cloud gateway. With a dedicated provider gateway you can use BGP neighbours, IP prefix lists and route advertisement.
Work alongside Site-to-Site VPN
Site-to-Site VPN runs on the same gateway as the private connection and can serve as an additional path.
Bring every connection to one place
SD-WAN and remote-access VPN connections attach to the same gateway, so your branches, users and private circuit meet at one point in the cloud.
Embedded security
A VLAN of your own
The circuit is handed over in the data centre network on a VLAN assigned to your organisation.
Only your own gateway
Each organisation's circuit connects only to that organisation's cloud gateway.
Firewall control
Traffic from the circuit passes through the cloud gateway's firewall rules, with your remote networks defined as sources.
Learn more to get started
Software-Defined Networking
See how the cloud network is built and protected.
Enterprise IT
Solutions for IT teams that run on-premises networks together with the cloud.
Cloud Migration
See the steps for moving workloads from on premises to the cloud.
Infrastructure
Learn about the data centres and network where the circuit is handed over.