Skip to main content

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 select 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.

Single-Port Architectures​

Single-Port BGP – Provider-assigned IP​

For this configuration, Equinix assigns Private Autonomous System Number (ASN) for your LAN, and a default WAN IP subnet /30 (for IPv4) and /64 (for IPv6). You must provide a BGP-capable Layer 3 device.

note

You must purchase additional LAN IP subnets from Equinix.

  • The IPv4 choices are: /30, /29, /28, /27, /26, /25, /24
  • The IPv6 choices are: /64, /48

BGP policy is used to select:

  • Default Routes
  • Full Routes
  • Default + Full Routes

Single-Port BGP – Provider-independent IP​

You can use either your own Public ASN or a Private ASN assigned by Equinix. Your IP addresses must be a minimum of IPv4 /24 or IPv6 /48. Equinix assigns a default /30 (IPv4) and /64 (IPv6) for your WAN IP subnet. You must provide a BGP-capable Layer 3 device for this configuration. If you use Equinix assigned Private ASN, they are replaced by Equinix Public ASN when announced to the Internet.

BGP policy is used to select:

  • Default Routes
  • Full Routes
  • Default + Full Routes

Dual-Port Architectures​

Dual-Port BGP – Provider-assigned IP​

By default, Equinix assigns two /30 (IPv4) and two /64 (IPv6) for the WAN IP subnet. You must provide a pair of Layer 3 devices for the dual-homed setup.

BGP Policy is used to select:

  • Default routes
  • Full routes
  • Default + full routes
note

You must purchase additional LAN IP addresses for this configuration.

  • The IPv4 choices are: /30, /29, /28, /27, /26, /25, /24
  • The IPv6 choices are: /64, /48

Dual-Port BGP – Provider-independent IP​

For this configuration, you can either use your own Public ASN, or use a Private ASN assigned by Equinix. Your IP addresses must be a minimum of IPv4 /24 or IPv6 /48. By default, Equinix assigns two /30 (IPv4) and two /64 (IPv6) for your WAN IP subnet. If you use Equinix-assigned Private ASN, it is replaced by Equinix Public ASN when advertised to the internet. You are required to provide a pair of Layer 3 devices for the dual-port setup.

BGP Policy is used to select:

  • Default routes
  • Full routes
  • Default + full routes

Traffic Engineering - BGP Communities​

The following communities are available to all BGP users:

  • Lower local preference

    • 65502:80 Set local preference to a lower value than standard customer (above peers, multi homed customer scenario)

  • Remotely Triggered Black Hole

    • 65535:666 Blackhole a single host within customer’s ranges

If you are using BGP and bringing your own IP addresses (PI), 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 (PI customers only)

    • 65501:nnnn Prepend 1x AS15830 towards a provider or IXs in a metro
    • 65502:nnnn Prepend 2x AS15830 towards a provider or IXs in a metro
    • 65503:nnnn Prepend 3x AS15830 towards a provider or IXs in a metro
    • 65505:nnnn (to be deprecated) Prepend 5x AS15830 towards a provider or IXs in a metro

  • Do not announce (PI customers only)

    • 65509:nnnn Don’t Announce the prefix towards a provider or IXs in a metro
    • 65509:300 Don’t Announce to any peer globally
    • 65509:400 Don’t 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) metro
  • 3302 - Peers in Atlanta (AT) metro
  • 3305 - Peers in Chicago (CH) metro
  • 3307 - Peers in Dallas (DA) metro
  • 3308 - Peers in Washington (DC) metro
  • 3312 - Peers in Los Angeles (LA) metro
  • 3315 - Peers in New York (NY) metro
  • 3319 - Peers in Seattle (SE) metro
  • 3322 - Peers in Silicon Valley (SV) metro
  • 3323 - Peers in Miami (MI) metro
  • 3324 - Peers in Rio de Janeiro (RJ) metro
  • 3325 - Peers in São Paulo (SP) metro
  • 3328 - Peers in Bogota (BG) metro
  • 3330 - Peers in Mexico City (MX) metro
  • 3331 - Peers in Vancouver (VA) metro
  • 3332 - Peers in Kamloops (KA) metro
  • 3333 - Peers in Winnipeg (WI) metro
  • 3334 - Peers in Calgary (CL) metro
  • 3335 - Peers in Montreal (MT) metro
  • 3338 - Peers in Monterrey (MO) metro
  • 3339 - Peers in Lima (LM) metro
  • 3340 - Peers in Santiago (ST) metro

APAC

  • 6301 - Peers in Hong Kong (HK) metro
  • 6304 - Peers in Osaka (OS) metro
  • 6305 - Peers in Tokyo (TY) metro
  • 6306 - Peers in Singapore (SG) metro
  • 6307 - Peers in Melbourne (ME) metro
  • 6308 - Peers in Sydney (SY) metro
  • 6309 - Peers in Perth (PE) metro
  • 6310 - Peers in Seoul (SL) metro
  • 6314 - Peers in Mumbai (MB) metro
  • 6316 - Peers in Jakarta (JK) metro
  • 6317 - Peers in Kuala Lumpur (KL) metro
  • 6318 - Peers in Johor (JH) metro

EMEA

  • 301 - Peers in London (LD) metro
  • 302 - Peers in Manchester (MA) metro
  • 303 - Peers in Dublin (DB) metro
  • 304 - Peers in Frankfurt (FR) metro
  • 305 - Peers in Amsterdam (AM) metro
  • 306 - Peers in Paris (PA) metro
  • 307 - Peers in Milan (ML) metro
  • 308 - Peers in Stockholm (SK) metro
  • 309 - Peers in Helsinki (HE) metro
  • 310 - Peers in Istanbul (IL) metro
  • 312 - Peers in Sofia (SO) metro
  • 313 - Peers in Warsaw (WA) metro
  • 317 - Peers in Munich (MU) metro
  • 319 - Peers in Geneva (GV) metro
  • 320 - Peers in Zurich (ZH) metro
  • 321 - Peers in Madrid (MD) metro
  • 322 - Peers in Lisbon (LS) metro
  • 323 - Peers in Barcelona (BA) metro
  • 324 - Peers in Hamburg (HH) metro
  • 331 - Peers in Johannesburg (JN) metro

Examples:

  • 65501:1299 Prepend 1x AS15830 towards Arelion AS1299
  • 65503:3325 Prepend 3x AS15830 towards any peer in São Paulo
  • 65509:301 Do not announce to any IX peer in London
  • 65502:80 Set 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 customers
  • 15830:3201 - Customers in Toronto (TR) metro
  • 15830:3202 - Customers in Atlanta (AT) metro
  • 15830:3204 - Customers in Culpeper (CU) metro
  • 15830:3205 - Customers in Chicago (CH) metro
  • 15830:3207 - Customers in Dallas (DA) metro
  • 15830:3208 - Customers in Washington (DC) metro
  • 15830:3212 - Customers in Los Angeles (LA) metro
  • 15830:3213 - Customers in Houston (HO) metro
  • 15830:3215 - Customers in New York (NY) metro
  • 15830:3216 - Customers in Philadelphia (PH) metro
  • 15830:3219 - Customers in Seattle (SE) metro
  • 15830:3222 - Customers in Silicon Valley (SV) metro
  • 15830:3223 - Customers in Miami (MI) metro
  • 15830:3224 - Customers in Rio de Janeiro (RJ) metro
  • 15830:3225 - Customers in São Paulo (SP) metro
  • 15830:3226 - Customers in Denver (DE) metro
  • 15830:3227 - Customers in Boston (BO) metro
  • 15830:3228 - Customers in Bogota (BG) metro
  • 15830:3230 - Customers in Mexico City (MX) metro
  • 15830:3231 - Customers in Vancouver (VA) metro
  • 15830:3232 - Customers in Kamloops (KA) metro
  • 15830:3233 - Customers in Winnipeg (WI) metro
  • 15830:3234 - Customers in Calgary (CL) metro
  • 15830:3235 - Customers in Montreal (MT) metro
  • 15830:3238 - Customers in Monterrey (MO) metro
  • 15830:3239 - Customers in Lima (LM) metro
  • 15830:3240 - Customers in Santiago (ST) metro

APAC

  • 15830:200 - All AS15830 customers
  • 15830:6201 - Customers in Hong Kong (HK) metro
  • 15830:6204 - Customers in Osaka (OS) metro
  • 15830:6205 - Customers in Tokyo (TY) metro
  • 15830:6206 - Customers in Singapore (SG) metro
  • 15830:6207 - Customers in Melbourne (ME) metro
  • 15830:6208 - Customers in Sydney (SY) metro
  • 15830:6209 - Customers in Perth (PE) metro
  • 15830:6210 - Customers in Seoul (SL) metro
  • 15830:6214 - Customers in Mumbai (MB) metro
  • 15830:6215 - Customers in Chennai (CN) metro
  • 15830:6216 - Customers in Jakarta (JK) metro
  • 15830:6217 - Customers in Kuala Lumpur (KL) metro
  • 15830:6218 - Customers in Johor (JH) metro

EMEA

  • 15830:200 - All AS15830 customers
  • 15830:201 - Customers in London (LD) metro
  • 15830:202 - Customers in Manchester (MA) metro
  • 15830:203 - Customers in Dublin (DB) metro
  • 15830:204 - Customers in Frankfurt (FR) metro
  • 15830:205 - Customers in Amsterdam (AM) metro
  • 15830:206 - Customers in Paris (PA) metro
  • 15830:207 - Customers in Milan (ML) metro
  • 15830:208 - Customers in Stockholm (SK) metro
  • 15830:209 - Customers in Helsinki (HE) metro
  • 15830:210 - Customers in Istanbul (IL) metro
  • 15830:212 - Customers in Sofia (SO) metro
  • 15830:213 - Customers in Warsaw (WA) metro
  • 15830:215 - Customers in Zwolle (ZW) metro
  • 15830:216 - Customers in Enschede (EN) metro
  • 15830:217 - Customers in Munich (MU) metro
  • 15830:218 - Customers in Dusseldorf (DU) metro
  • 15830:219 - Customers in Geneva (GV) metro
  • 15830:220 - Customers in Zurich (ZH) metro
  • 15830:221 - Customers in Madrid (MD) metro
  • 15830:222 - Customers in Lisbon (LS) metro
  • 15830:223 - Customers in Barcelona (BA) metro
  • 15830:224 - Customers in Hamburg (HH) metro
  • 15830:225 - Customers in Brussels (BL) metro
  • 15830:227 - Customers in Bordeaux (BX) metro
  • 15830:231 - Customers in Johannesburg (JN) metro