BGP Routing
Border Gateway Protocol (BGP) Routing determines the best network routes for data transmission on the internet. The internet consists of thousands of private, public, corporate, and government networks linked together through standardized protocols, devices, and communication technologies. When you browse the internet, data travels across multiple networks before reaching its destination. BGP looks at all the available paths that data could travel and selects the best route. For instance, when a user in the United States loads an application with origin servers in Europe, BGP makes that communication quick and efficient.
Equinix assigns a private Autonomous System Number (ASN) for your LAN. BGP policy is used to select:
- Default Routes
- Full Routes
- Default + Full Routes
IP Subnet Sourcing
The available options for the LAN IP subnets used by EIA services are described here:
Up to 100 subnets can be configured per EIA service. Subnets may include a mix of Equinix-assigned and Customer-assigned IP addresses. Mixing Equinix-assigned and Customer-assigned addresses on the same EIA service is permitted only when the announcing ASN is provided by Equinix. Equinix-assigned addresses cannot be announced using a customer ASN.
Equinix-assigned IP Addresses
Provided by Equinix, you must purchase additional LAN IP subnets from Equinix for this option.
Customer-assigned IP Addresses
Provided by the customer, IP addresses must be at least IPv4 /24 or IPv6 /48. For customer-assigned IPs, customers can use either their own public ASN (only for EIA over Dedicated variant) or a private ASN assigned by Equinix.
Single-Port Architectures
For Single-Port BGP, Equinix assigns a private Autonomous System Number (ASN) for the LAN, and a default WAN IP subnet of /30 for IPv4 addresses and /64 for IPv6 addresses. A BGP-capable Layer 3 device is required.


Dual-Port Architectures
By default, Equinix assigns a private Autonomous System Number (ASN) for the LAN, and two /30 IPv4 WAN subnets and two /64 IPv6 WAN subnets. A pair of Layer 3 devices for the dual-homed setup is required.


Traffic Engineering - BGP Communities
The following communities are available to all BGP users:
-
Lower local preference
65502:80Set local preference to a lower value than standard customer (above peers, multi homed customer scenario)
-
Remotely Triggered Black Hole
65535:666Blackhole a single host within customer’s ranges
If you are using BGP and bringing your own IP addresses, you can control how your routes are announced out of AS15830, and how traffic should flow into your network. Equinix offers the following communities for you to tag onto your prefixes.
-
Prepend (Customer-assigned IP addresses only)
65501:nnnnPrepend 1x AS15830 towards a provider or IXs in a metro65502:nnnnPrepend 2x AS15830 towards a provider or IXs in a metro65503:nnnnPrepend 3x AS15830 towards a provider or IXs in a metro65505:nnnn(to be deprecated) Prepend 5x AS15830 towards a provider or IXs in a metro
-
Do not announce (Customer-assigned IP addresses only)
65509:nnnnDo not announce the prefix towards a provider or IXs in a metro65509:300Do not announce to any peer globally65509:400Do not announce to any ISP provider globally
The suffix ‘nnnn’ can be either the provider ASN or one of the following:
AMER
3301- Peers in Toronto (TR) metro3302- Peers in Atlanta (AT) metro3305- Peers in Chicago (CH) metro3307- Peers in Dallas (DA) metro3308- Peers in Washington (DC) metro3312- Peers in Los Angeles (LA) metro3315- Peers in New York (NY) metro3319- Peers in Seattle (SE) metro3322- Peers in Silicon Valley (SV) metro3323- Peers in Miami (MI) metro3324- Peers in Rio de Janeiro (RJ) metro3325- Peers in São Paulo (SP) metro3328- Peers in Bogota (BG) metro3330- Peers in Mexico City (MX) metro3331- Peers in Vancouver (VA) metro3332- Peers in Kamloops (KA) metro3333- Peers in Winnipeg (WI) metro3334- Peers in Calgary (CL) metro3335- Peers in Montreal (MT) metro3338- Peers in Monterrey (MO) metro3339- Peers in Lima (LM) metro3340- Peers in Santiago (ST) metro
APAC
6301- Peers in Hong Kong (HK) metro6304- Peers in Osaka (OS) metro6305- Peers in Tokyo (TY) metro6306- Peers in Singapore (SG) metro6307- Peers in Melbourne (ME) metro6308- Peers in Sydney (SY) metro6309- Peers in Perth (PE) metro6310- Peers in Seoul (SL) metro6314- Peers in Mumbai (MB) metro6316- Peers in Jakarta (JK) metro6317- Peers in Kuala Lumpur (KL) metro6318- Peers in Johor (JH) metro
EMEA
301- Peers in London (LD) metro302- Peers in Manchester (MA) metro303- Peers in Dublin (DB) metro304- Peers in Frankfurt (FR) metro305- Peers in Amsterdam (AM) metro306- Peers in Paris (PA) metro307- Peers in Milan (ML) metro308- Peers in Stockholm (SK) metro309- Peers in Helsinki (HE) metro310- Peers in Istanbul (IL) metro312- Peers in Sofia (SO) metro313- Peers in Warsaw (WA) metro317- Peers in Munich (MU) metro319- Peers in Geneva (GV) metro320- Peers in Zurich (ZH) metro321- Peers in Madrid (MD) metro322- Peers in Lisbon (LS) metro323- Peers in Barcelona (BA) metro324- Peers in Hamburg (HH) metro331- Peers in Johannesburg (JN) metro
Examples:
65501:1299Prepend 1x AS15830 towards Arelion AS129965503:3325Prepend 3x AS15830 towards any peer in São Paulo65509:301Do not announce to any IX peer in London65502:80Set local preference below standard customers but above peers (backup)
Origin Communities
Your traffic is marked as follows in different metros:
AMER
15830:200- All AS15830 customers15830:3201- Customers in Toronto (TR) metro15830:3202- Customers in Atlanta (AT) metro15830:3204- Customers in Culpeper (CU) metro15830:3205- Customers in Chicago (CH) metro15830:3207- Customers in Dallas (DA) metro15830:3208- Customers in Washington (DC) metro15830:3212- Customers in Los Angeles (LA) metro15830:3213- Customers in Houston (HO) metro15830:3215- Customers in New York (NY) metro15830:3216- Customers in Philadelphia (PH) metro15830:3219- Customers in Seattle (SE) metro15830:3222- Customers in Silicon Valley (SV) metro15830:3223- Customers in Miami (MI) metro15830:3224- Customers in Rio de Janeiro (RJ) metro15830:3225- Customers in São Paulo (SP) metro15830:3226- Customers in Denver (DE) metro15830:3227- Customers in Boston (BO) metro15830:3228- Customers in Bogota (BG) metro15830:3230- Customers in Mexico City (MX) metro15830:3231- Customers in Vancouver (VA) metro15830:3232- Customers in Kamloops (KA) metro15830:3233- Customers in Winnipeg (WI) metro15830:3234- Customers in Calgary (CL) metro15830:3235- Customers in Montreal (MT) metro15830:3238- Customers in Monterrey (MO) metro15830:3239- Customers in Lima (LM) metro15830:3240- Customers in Santiago (ST) metro
APAC
15830:200- All AS15830 customers15830:6201- Customers in Hong Kong (HK) metro15830:6204- Customers in Osaka (OS) metro15830:6205- Customers in Tokyo (TY) metro15830:6206- Customers in Singapore (SG) metro15830:6207- Customers in Melbourne (ME) metro15830:6208- Customers in Sydney (SY) metro15830:6209- Customers in Perth (PE) metro15830:6210- Customers in Seoul (SL) metro15830:6214- Customers in Mumbai (MB) metro15830:6215- Customers in Chennai (CN) metro15830:6216- Customers in Jakarta (JK) metro15830:6217- Customers in Kuala Lumpur (KL) metro15830:6218- Customers in Johor (JH) metro
EMEA
15830:200- All AS15830 customers15830:201- Customers in London (LD) metro15830:202- Customers in Manchester (MA) metro15830:203- Customers in Dublin (DB) metro15830:204- Customers in Frankfurt (FR) metro15830:205- Customers in Amsterdam (AM) metro15830:206- Customers in Paris (PA) metro15830:207- Customers in Milan (ML) metro15830:208- Customers in Stockholm (SK) metro15830:209- Customers in Helsinki (HE) metro15830:210- Customers in Istanbul (IL) metro15830:212- Customers in Sofia (SO) metro15830:213- Customers in Warsaw (WA) metro15830:215- Customers in Zwolle (ZW) metro15830:216- Customers in Enschede (EN) metro15830:217- Customers in Munich (MU) metro15830:218- Customers in Dusseldorf (DU) metro15830:219- Customers in Geneva (GV) metro15830:220- Customers in Zurich (ZH) metro15830:221- Customers in Madrid (MD) metro15830:222- Customers in Lisbon (LS) metro15830:223- Customers in Barcelona (BA) metro15830:224- Customers in Hamburg (HH) metro15830:225- Customers in Brussels (BL) metro15830:227- Customers in Bordeaux (BX) metro15830:231- Customers in Johannesburg (JN) metro