- April 30, 2021
- April 8, 2021
- March 25, 2021
- March 15, 2021
- February 25, 2021
- February 8, 2021
- January 28, 2021
- January 21, 2021
- January 13, 2021
- 2020 Releases
- Getting Started
- Cross Connects
- Virtual Circuits
- Cloud Connectivity Overview
- Amazon Web Services
Google Cloud Platform
- Google Cloud Interconnect Overview
- Pricing Examples
- Google Interconnect Redundancy
- Microsoft Azure
- IBM Cloud
- Oracle Cloud Infrastructure
- Cloud Router Overview
- Requirements and Feature Support
- Create and Manage Cloud Routers
- Add Connections
- Manage Connections
- BGP Sessions
- Resources and FAQ
- Marketplace & IX
- Troubleshooting & FAQ
- Technical Reference
- Reseller Admin Portal
PacketFabric Network Hierarchy
- A region doesn’t follow specific boundaries, but typically represents a general geopolitical area.
- A market is not a single city; it is a geographical metropolitan area (also referred to as a “metro”). For example, the New York City market includes POPs located in New Jersey.
- Whether a service extends outside a market affects how you are billed:
- If a virtual circuit extends between POPs within a market, data transfer is free.
- If your source port and cloud on-ramp port are in the same market, you receive Metro pricing on a cloud connection. For more information on metro pricing, see our cloud connectivity pricing calculator.
- A POP (point of presence) is one or more sites in the same cross connect domain. This means that an operator can run a cross connect to every site within the POP.
- Note the following:
- When you select a location for your service, you select it at the POP level.
- Our POP names and numbers are unique to PacketFabric and do not map to any data center names or designations.
- There can be multiple POPs in a market.
- PacketFabric equipment is installed at the site level.
- A site can be any physical location with its own shipping address. For example, a site might be a floor or suite within a building, or it might be the entire building.
- You can view the sites within a POP through our API. However, sites are not available for individual selection when provisioning ports.
Using the example below, let’s say you provision a port in the CHI2 POP. This means that the actual port itself could be in either Cyxtera Chicago ORD1 or Digital Realty CHI1. PacketFabric programatically selects the specific site on your behalf.
If you connect to a cloud on-ramp in the CHI3 POP, you receive Metro transit pricing.
If you create a virtual circuit to the CHI3 POP, you are not charged for data transfer.
If you connect to a port in any POP outside the Chicago market (e.g. the ATL1 POP), you are charged long-haul data transfer pricing.