Routing Policy

General

Routes must have valid ROA to be accepted.
Routes with unusually large path lengths (> 8) are rejected as they usually signal ghost routes.
AS4242421080 uses cold potato routing. This is done by calculating MED values on import - routes that have the same origin BGP community as the receiving PoP will be assigned a lower MED.

North America - Central (42) and North America - East (43) are considered one region.
Asia Pacific (51, 52, 53) is considered one region.

To prevent abuse, outbound dn42 traffic is rate limited to 15Mbps per interface.

AS4242421080 supports the standard dn42 BGP communities for bandwidth, encryption, and route origin region.
The latency metric is NOT supported (and should not be used for choosing routes anyways, as it does not account for intra-AS latency).

AS4242421080 exports the following informational large communities:

(AS4242421080, 100, X) - Route learned by server ID X:
- (AS4242421080, 100, 35) - Route learned in 🇺🇸 Seattle, WA, US
- (AS4242421080, 100, 34) - Route learned in 🇺🇸 San Jose, CA, US
- (AS4242421080, 100, 113) - Route learned in 🇺🇸 Chicago, IL, US
- (AS4242421080, 100, 115) - Route learned in 🇨🇦 Toronto, ON, CA
- (AS4242421080, 100, 123) - Route learned in 🇨🇦 Montreal, QC, CA
- (AS4242421080, 100, 33) - Route learned in 🇺🇸 Dallas, TX, US
- (AS4242421080, 100, 112) - Route learned in 🇺🇸 Ashburn, VA, US
- (AS4242421080, 100, 116) - Route learned in 🇬🇧 London, UK
- (AS4242421080, 100, 118) - Route learned in 🇳🇱 Amsterdam, NL
- (AS4242421080, 100, 117) - Route learned in 🇩🇪 Frankfurt, DE
- (AS4242421080, 100, 121) - Route learned in 🇸🇪 Stockholm, SE
- (AS4242421080, 100, 124) - Route learned in 🇯🇵 Tokyo, JP
- (AS4242421080, 100, 38) - Route learned in 🇭🇰 Hong Kong, HK
- (AS4242421080, 100, 39) - Route learned in 🇸🇬 Singapore, SG
- (AS4242421080, 100, 125) - Route learned in 🇦🇺 Sydney, AU
- (AS4242421080, 100, 120) - Route learned in 🇮🇳 Mumbai, IN
(AS4242421080, 101, 41...70) - Route learned in this dn42 region