BGP Communities

Everything you need to know about the i3D.net informational communities on your prefix advertisement to AS49544.

BGP Informational Communities

i3D.net strips all external BGP communities on the AS49544 border routers. If a customer unilaterally attempts to set i3D.net informational communities on their prefix advertisement to AS49544, these will be stripped as well before the rest of the AS49544 import policy is processed. Informational communities that provide knowledge about where (and how) that route was learned are then added to each prefix. There are always two informational tags on a prefix in the AS49544 backbone, one with full location details and one for the generic continental area. These codes are always in the 49544:CTLLL format:

49544: Standard preamble.
C Continent where the route was learned.
T Type of relationship with BGP neighbor.
LLL Location where the route was learned.

Continental codes:

North America
Europe
Asia-Pacific
Oceania
South America
Africa

Relationship codes:

Internal route originated by AS49544
IP transit customer route
Private peering route
Public peering route
Upstream partial IP transit route
Upstream full IP transit route

Location codes:

Generic continental region:
- - When the three location digits are 000 it concerns all routes of this type learned on the continent.
North America:
- First location digit indicates federal nation:
  - 1 United States of America
  - 2 Canada
- For USA, the second and third location digits indicate State ANSI FIPS code:https://www.census.gov/library/reference/code-lists/ansi/ansi-codes-for-states.html
- For Canada, the second and third location digits indicate Canada’s SGC Provinces and Territories code: http://en.wikipedia.org/wiki/Standard_Geographical_Classification_code_(Canada)#Provinces_and_Territories
Rest of the world:
- The three location digits are the ITU-T E.164 telephone country code: http://en.wikipedia.org/wiki/List_of_country_calling_codes#Alphabetical_listing_by_country_or_region

Examples:

49544:16106 = route learned from full transit in North America, USA, California.
49544:24031 = route learned from public peering in Europe, The Netherlands.
49544:23000 = route learned from private peering in Europe.
49544:35852 = route learned from partial transit in Asia-Pacific, Hong Kong.
49544:22031 = route learned from IP transit customer in Europe, The Netherlands.
49544:14235 = route learned from public peering in North America, Canada, Ontario.

BGP Well-known Communities

i3D.net is aware of well-known BGP communities as defined by the IETF and has currently implemented the following standardized well-known BGP communities:

RFC1997 = 65535:65281 = NO_EXPORT
RFC3765 = 65535:65284 = NO_PEER

Please note that 65535:65284 has the same effect as 65500:65000 per the BGP Action Community documentation described later in the document.

BGP Blackhole Communities

i3D.net currently provides a blackhole community that takes global effect. You can trigger a blackhole for IPv4 and IPV6 prefixes that you’re already permitted to advertise by tagging the route with 49544:666. This works for the whole prefix, all the way down to /32 and /128 size: so please take great care when using this functionality.

BGP LocalPref Communities

By default, i3D.net customers are imported to BGP with LocalPref 5000. However, i3D.net provides a LocalPref manipulation community that will allow you to control the link over which traffic comes in for active-passive backup purposes. You can set the LocalPref to 4000 by tagging the route with 49544:4000, which is still higher than non-customer routes.

BGP Action Communities

i3D.net provides a set of BGP action communities allowing customers to manipulate routing policy for their prefixes within the backbone. This functionality only works for AS49544 peering and transit BGP neighbors, our transit customers always receive every prefix without 49544 prepends. Please note we already take great care when announcing our prefixes outside the originating continent to prevent hairpinning. BGP action communities are always in the action: target format, using the following syntax:

Action:

65501 = Prepend the AS-path once using AS49544, results in _TARGET_49544_49544_CUSTOMER$
65502 = Prepend the AS-path twice using AS49544, results in _TARGET_49544_49544_49544_CUSTOMER$
65503 = Prepend the AS-path thrice using AS49544, results in _TARGET_49544_49544_49544_49544_CUSTOMER$
65500 = Do not advertise route to target (AKA no-export).

Target:

IP transit providers:
- 174 = Cogent Communications
- 1299 = Telia Carrier
- 2914 = NTT Communications
- 3356 = Lumen (formerly known as CenturyLink, Level(3) Communications)
- 65535 = All transit providers
Regional peering codes:
- 65000 = All worldwide peering
- 65001 = All North American peering
- 65002 = All European peering
- 65003 = All Asian-Pacific peering
- 65004 = All Oceanian peering
- 65005 = All South American peering
- 65006 = All African peering
Internet Exchange codes:
- 65010 = All peering in the Netherlands
  - 65011 = AMS-IX, Amsterdam
  - 65012 = NL-ix, Rotterdam
  - 65013 = R_iX, Rotterdam
  - 65014 = Asteroid, Amsterdam
  - 65015 = Frys-IX, Amsterdam
  - 65016 = BBIX, Rotterdam
- 65020 = All peering in Germany
  - 65021 = DE-CIX, Frankfurt
  - 65022 = ECIX, Frankfurt
  - 65023 = Peering.cz, Frankfurt
  - 65024 = NL-ix, Frankfurt
  - 65025 = City-IX, Frankfurt
- 65030 = All peering in the United Kingdom
  - 65031 = LINX LON1, London
  - 65032 = LONAP, London
  - 65033 = LINX LON2, London
- 65040 = All peering in Poland
  - 65041 = PLIX, Warsaw
  - 65042 = TPIX, Warsaw
  - 65043 = EPIX.Katowice, Warsaw
  - 65044 = EPIX.Warszawa-KIX, Warsaw
- 65050 = All peering in Virginia, USA
  - 65051 = Equinix Ashburn IX, Ashburn VA
  - 65052 = LINX NoVA, Ashburn VA
  - 65053 = MegaIX Ashburn, Ashburn VA
- 65060 = All peering in California, USA
  - 65061 = Any2 California, Los Angeles CA
  - 65062 = Equinix Los Angeles IX, Los Angeles CA
  - 65063 = Equinix San Jose IX, Santa Clara CA
  - 65064 = Equinix Palo Alto IX, Santa Clara CA
  - 65065 = SFMIX, Santa Clara CA
  - 65066 = BBIX US-West, Los Angeles CA
- 65070 = All peering in Australia
  - 65071 = IX Australia NSW, Sydney
  - 65073 = Equinix Sydney IX, Sydney
  - 65074 = MegaIX Sydney, Sydney
  - 65075 = EdgeIX, Sydney
- 65080 = All peering in Japan
  - 65081 = BBIX Tokyo, Tokyo
  - 65082 = Equinix Tokyo IX, Tokyo
  - 65083 = JPIX Tokyo, Tokyo
- 65090 = All peering in Brazil
  - 65091 = IX.br São Paulo, Brazil
  - 65092 = Equinix São Paulo, Brazil
- 65100 = All peering in Texas, USA
  - 65101 = Equinix Dallas IX, Dallas TX
  - 65102 = DE-CIX Dallas, Dallas TX
  - 65103 = MegaIX Dallas, Dallas TX
- 65110 = All peering in South Africa
  - 65111 = NAPAfrica IX Johannesburg, Johannesburg
  - 65112 = angonix, Johannesburg
  - 65113 = JINX, Johannesburg
- 65120 = All peering in Hong Kong
  - 65121 = HKIX, Hong Kong
  - 65122 = Equinix Hong Kong IX, Hong Kong
  - 65123 = BBIX Hong Kong, Hong Kong
  - 65124 = AMS-IX Hong Kong, Hong Kong
- 65130 = All peering in the United Arab Emirates
  - 65131 = UAE-IX, Dubai
  - 65132 = SH-IX, Fujairah
- 65140 = All peering in New Jersey, USA
  - 65141 = DE-CIX New York, Newark NJ
  - 65142 = NYIIX, Newark NJ
  - 65143 = Equinix New York IX, Newark NJ
- 65150 = All peering in Illinois, USA
  - 65151 = Equinix Chicago IX, Chicago IL
  - 65152 = DE-CIX Chicago, Chicago IL
- 65170 = All peering in Singapore
  - 65171 = Equinix Singapore IX, Singapore
  - 65172 = SGIX, Singapore
  - 65173 = BBIX Singapore, Singapore
  - 65174 = MegaIX Singapore, Singapore
- 65180 = All peering in France
  - 65181 = Equinix Paris IX, Paris
  - 65182 = France-IX Paris, Paris
- 65190 = All peering in Québec, Canada
  - 65191 = QIX, Montreal
- 65200 = All peering in Ukraine
  - 65201 = DTEL-IX, Kyiv
  - 65202 = UA-IX, Kyiv
- 65210 = All peering in Washington, USA
  - 65211 = SIX Seattle, Seattle WA
  - 65212 = Equinix Seattle IX, Seattle WA
  - 65213 = MegaIX Seattle, Seattle WA
- 65220 = All peering in Spain
  - 65221 = DE-CIX Madrid, Madrid
  - 65222 = Equinix Madrid IX, Madrid
  - 65223 = ESPANIX Madrid Lower-LAN, Madrid
  - 65224 = ESPANIX Madrid Upper-LAN, Madrid
- 65230 = All peering in Ontario, Canada
  - 65231 = TorIX, Toronto
  - 65232 = Equinix Toronto IX, Toronto
  - 65233 = MegaIX, Toronto
- 65240 = All peering in Denmark
  - 65241 = DIX, Copenhagen
  - 65242 = Netnod Copenhagen Blue, Copenhagen
  - 65243 = Netnod Copenhagen Green, Copenhagen
  - 65244 = STHIX, Copenhagen
- 65250 = All peering in India
  - 65251 = DE-CIX Mumbai, Mumbai
  - 65252 = AMS-IX Mumbai, Mumbai
  - 65253 = Extreme-IX Mumbai, Mumbai
  - 65254 = NIXI Mumbai, Mumbai
- 65260 = All peering in Georgia, USA
  - 65261 = Equinix IX, Atlanta
  - 65262 = Digital Realty IX, Atlanta
  - 65263 = Community IX, Atlanta
- 65270 = All peering in Chile
  - 65271 = PIT Santiago, Chile
- 65280 = All peering in Sweden
  - 65281 = Netnod Stockholm Blue, Stockholm
  - 65282 = Netnod Stockholm Green, Stockholm
  - 65283 = Equinix Stockholm IX, Stockholm
  - 65284 = STHIX, Stockholm
- 65290 = All peering in Argentina
- 65300 = All peering in Italy
  - 65301 = MIX-IT, Milan
  - 65302 = Equinix Milano IX, Milan
- 65310 = All peering in Romania
  - 65311 = InterLAN, Bucharest
  - 65312 = Balcan-IX, Bucharest
  - 65313 = RoNIX, Bucharest
- 65320 = All peering in Switzerland
  - 65321 = SwissIX, Zurich
  - 65322 = Equinix Zurich IX, Zurich
- 65330 = All peering in Norway
  - 65331 = NIX1, Oslo
- 65340 = All peering in Austria
  - 65341 = VIX, Vienna
  - 65342 = NIX. CZ, Vienna
  - 65343 = NIX. SK, Vienna
- 65350 = All peering in Hungary
  - 65351 = BiX, Budapest

Examples:

65501:3356 = prepend the AS-path for this prefix once towards transit Level(3) Communications.
65500:174 = do not advertise this prefix towards transit Cogent Communications.
65502:65041 = prepend the AS-path for this prefix twice with AS49544 towards peers on PLIX, Warsaw.
65503:65072 = prepend the AS-path for this prefix thrice with AS49544 towards peers on PipeIX NSW, Sydney.

Compute

Cloud

Related Pages

Game Online Services

Related Pages

Connectivity

Related Pages

CDN

Related Pages

Colocation

Related Pages

By Application

Compute

Low Latency Connectivity

Content Delivery

DDoS Mitigation

BGP Communities

Everything you need to know about the i3D.net informational communities on your prefix advertisement to AS49544.

BGP Informational Communities

Continental codes:

Relationship codes:

Location codes:

Examples:

BGP Well-known Communities

BGP Blackhole Communities

BGP LocalPref Communities

BGP Action Communities

Action:

Target:

Examples:

Need help from our Customer Support Team?

Sales

Features

Solutions

Products

Company