RackCorp BGP Communities

RackCorp is currently undergoing a transition to our BGP model globally.  If you notice a combination of communities is not working as you expect, please raise a support ticket as our team as it may be our issue

BGP Looking Glass URL
(RackCorp is currently undergoing testing on this service and it is not currently publicly available)
https://lg.rackcorp.com/

Transit Management (outbound)

(Please note while we try to pass on these communities, upstream networks may still advertise to these providers)
56038:283 Don't advertise to CoreIX (AS31708)
56038:284 Don't advertise to Hurricane Electric (AS6939)
56038:285 Don't advertise to Constant (AS20473)
56038:297 Don't advertise to NTT (AS2914)
56038:279 Don't advertise to Vocus (AS4826)
56038:286 Don't advertise to IPTransit (AS64098)
56038:287 Don't advertise to Indonet (AS9340)
56038:288 Don't advertise to Voxility (AS3223)
56038:289 Don't advertise to China Telecom (AS58453)
56038:290 Don't advertise to Aknet (AS12764)
56038:291 Don't advertise to Cogent (AS174)
56038:292 Don't advertise to Mongolia National DC (AS56301)
56038:293 Don't advertise to Gemnet (AS45204)

Peering Management (outbound)

(Please note while we try to pass on these communities, upstream networks may still advertise to peering exchanges)
56038:300 Don't advertise to WA-IX AU
56038:301 Don't advertise to NSW-IX AU
56038:302 Don't advertise to VIC-IX AU
56038:303 Don't advertise to QLD-IX AU
56038:310 Don't advertise to Megaport WA IX AU
56038:311 Don't advertise to Megaport NSW IX AU
56038:312 Don't advertise to Megaport VIC IX AU
56038:313 Don't advertise to Megaport QLD IX AU
56038:320 Don't advertise to DEC-IX DE

Global Management (outbound)

56038:666 Blackhole prefix wherever possible (only IPv4 /32 or IPv6 /128 allowed)

56038:777 Do not advertise outside of local city (Useful if deploying anycast and utilising other vendors besides RackCorp)

56038:888 Attempt to pad announcements globally with prefixes for optimal anycast traffic
56038:8880 Attempt to pad announcements globally with prefixes for optimal anycast traffic (identical to :888)
56038:8881 Attempt to pad announcements globally with prefixes for optimal anycast traffic +1
56038:8882 Attempt to pad announcements globally with prefixes for optimal anycast traffic +2
56038:8883 Attempt to pad announcements globally with prefixes for optimal anycast traffic +3
56038:8889 Do not advertise
56038:2000 Do not advertise by default (Use specific keyed communities)

Cloud Users next-hop (outbound)

You can use 110.232.119.254 as your next-hop.  Our systems will automatically assign your VM primary IP as the next hop.

Keyed Management (outbound)

(Please note while we try to pass on these communities, upstream networks may still advertise at these locations)
A: 1=Dont Advertise, 2=Advertise no padding, 3=Advertise pad x1, 4=Advertise pad x2, 5=Advertise pad x3, 6=Advertise no-export
B: 0=Transit + Peering, 1=Transit Only, 2=Peering Only
56038:1AB00 Global
56038:1AB21 AU Brisbane
56038:1AB01 AU Sydney GlobalSwitch
56038:1AB26 AU Sydney Equinix
56038:1AB02 AU Melbourne
56038:1AB03 AU Perth
56038:1AB09 DE FRA8
56038:1AB08 HK
56038:1AB14 IN
56038:1AB13 JP
56038:1AB19 MN MNDC1
56038:1AB20 MN GEMNET1
56038:1AB12 NL Amsterdam
56038:1AB11 NZ
56038:1AB17 TH BKK1
56038:1AB18 TH BKK2
56038:1AB06 UK London
56038:1AB04 US Fremont
56038:1AB05 US Chicago
56038:1AB15 US Los Angeles, CA
56038:1AB16 US Reston VA
56038:1AB07 SG
56038:1AB22 KG NSP1
56038:1AB23 PH Carmona
56038:1AB24 PH Makati
56038:1AB25 ID Jakarta

56038:5070 Force local-pref 70
56038:5080 Force local-pref 80 (Default)
56038:5090 Force local-pref 90
56038:5095 Force local-pref 95

Informational Communities (inbound)

56038:3000 Received via local
56038:3001 Received via transit
56038:3002 Received via peering
56038:3003 Received via customer

BGP Internal Distancing (inbound)

RackCorp uses a private AS65001 to represent some internal connectors in the BGP router path and is used to indicate distance between datacenters/cities. You can make use of these internally if you wish in calculating optimal routing


Revision #5
Created 1 March 2022 05:18:51 by Stephen D
Updated 1 March 2022 09:00:51 by Stephen D