Packet Connect

What is Packet Connect? 

Packet Connect allows direct connection of Packet infrastructure with the Azure cloud environment to achieve a seamless hybrid cloud architecture. This is built from the ground up to be a cloud-native network service focused on developers and their needs.  Service is automated via native APIs to support virtual connections that are priced hourly and monthly, which simplifies the ordering process. It is also a high quality, reliable connection with available speeds from 100Mbps to 10 Gbps for virtual connections.

What facilities is Packet Connect in?

At launch, we will offer Packet Connect in our EWR1 & SJC1 facilities, with other facilities coming soon.

How to get the best latency?

For use in EWR, Azure US-East(1,2). For SJC, use Azure US-W(1,2)

Which providers does Packet Connect work with? 

Microsoft Azure, coming soon Google Cloud Platform (GCP) & AWS

How Does Packet Connect work? 

It is no secret that Packet customers have applications, microservices, deployed across both the packet Data centers and cloud providers such as Azure, GCP, and AWS. In fact, more than a third of our outbound traffic is goes to these cloud providers. 

Packet customers can create a virtual interconnect between the Packet Data center and cloud provider through the self-serving portal or via the APIs. Each virtual interconnect corresponds to a VLAN subnet the customer has created in both the Packet data center and in the cloud data centers.  Each virtual interconnect is capped at a CIR of anywhere from 100Mbps to 10Gbps. 

What is a use case for Packet Connect? 

Prior to Packet Connect, the only options for Packet customers to connect to public cloud providers--such as the Azure virtual network--was over our existing backbone network. This method was not ideal due to the possibility for higher latency--depending on how the packets get routed. Packet Connect provides an alternative by establishing a high-quality direct connection to the cloud data center without having to peer with the IXP, as shown below. This allows customers already in GCP/AWS/Azure to seamlessly access/move their workloads between the public cloud and select Packet data centers.

How does billing work for Packet Connect?

Packet Connect is billed per location, per circuit (virtual or physical) on a total port capacity,  and usage (per GB).  The pricing per VLAN, Speed, the connection is below. 

Virtual Connection:

Capacity (Port Speed) per VLAN

Hourly Rate

Outbound Rate

Ingress Rate





















*(Please contact Packet for availability and reservation)

Physical Connection:




Outbound Rate

Ingress Rate











How do you enable Packet Connect? 

Packet Connect is purely Layer 2. The first thing you must do is create a VLAN within the IPs & Network section of the project you wish to enable Packet Connect for.

With the VLAN created, you can proceed to the same IPs & Networking dropdown and, this time, select Packet Connect.

Name your connection, choose your provider:

Choose VLAN location, SJC/EWR are the available options for now.

Choose port speed:

Select your previously created VLAN:

Input your Azure ExpressRoute Key:

Confirm pricing is understood: 


Provisioning Complete:

Azure Quick Glance:

Circuit Name: Will be what you would like to call this particular circuit. In this example, we shall call it PacketConnect. 

Provider: Will be us, Packet! 

Peering Location: Will either be New York (EWR1) or Silicon Valley (SJC1)

Bandwidth: Is the specific port speed you require, it must also match what you opted for our Customer Portal. 

SKU: This is specific to Azure billing method, please review here for more info. (pending link)

Billing Model: This is also specific to the billing method, please review here for more info. (pending link)

Allow Classic Operations: This enables the workload to utilize older untraditional “classic” circuit config.

Subscription: This is determined by your particular subscription tier with Azure. 

Resource Group: This is specific to your setup on Azure, to group your particular resources. 

Location: Where this circuit will live. (e.g. US-E, US-W, etc)

While the circuit is being created, you will be able to follow along from the notifications drop down as shown above. To complete the network connection to Azure a Virtual Network & Virtual Network Gateway must be configured/setup on Azure side. When creating your virtual network, always use /30. 


Disconnect/Delete: You must first delete the circuit on Packet portal. In order to delete it via the Azure site.

Lowest Speed: Azure has 50Mbps, however, we are not offering that speed. Our lowest offering is 100Mbps. 

Azure VLAN: In the Azure portal, the VLAN will NOT match your Packet Layer 2 VLAN. In fact, in Azure you will find VLAN2, this is expected.

BGP/Layer2: Enable Layer2 on the Packet project, that will be utilized for Packet Connect. In addition, local BGP will also need to be enabled on the same project.