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.
• As such, MED values from other ASNs will be ignored at import.
• For cold potato routing:
• North America - Central (42) and North America - East (43) are considered one region.
• Asia Pacific (51, 52, 53) is considered one region.

Rate Limits

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

BGP Communities

• 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).

Large communities

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, 123) - Route learned in 🇨🇦 Toronto, ON, CA
  • (AS4242421080, 100, 116) - Route learned in 🇬🇧 London, UK
  • (AS4242421080, 100, 117) - Route learned in 🇩🇪 Frankfurt, DE
• (AS4242421080, 101, 41...70) - Route learned in this dn42 region