Region Codes
Geographic region codes used in AS203314 BGP communities for area-based routing policies across Asia-Pacific, Europe, North America, and Oceania regions.
Region communities use a two-digit geographic code. 203314:130:XX identifies a learning region; 203314:201:XX requests that a region be excluded from export.
Usage: These codes identify geographic regions in internal communities (130:XX, 135:XX) and control communities (201:XX).
Region Code Reference
| Region Name | Area | Code | Notes |
|---|---|---|---|
| Asia | West | 100 | Hong Kong, Taiwan |
| Asia | East | 150 | Japan, Singapore |
| Europe | West | 200 | UK, Ireland, France |
| Europe | East | 250 | Germany, Netherlands, Russia |
| Americas | North | 300 | USA, Canada |
| Americas | South | 350 | Brazil, Argentina |
| Australia | West | 400 | Perth |
| Australia | East | 450 | Melbourne, Sydney |
| Antarctica | - | 500 | Research networks |
Regional Groupings
Asia (100, 150)
Asia West (100): Hong Kong, Taiwan, mainland China
Asia East (150): Japan, Korea, Singapore, Southeast Asia
Europe (200, 250)
Europe West (200): UK, Ireland, France, Benelux, Iberia
Europe East (250): Germany, DACH, Netherlands, Nordics, Eastern Europe
Americas (300, 350)
North America (300): United States, Canada, Mexico
South America (350): Brazil, Argentina, Chile, Colombia
Oceania (400, 450)
Australia West (400): Western Australia
Australia East (450): Eastern states (NSW, VIC, QLD)
Using Region Codes
In Internal Communities
Identify where a route was learned:
# Learned-in tags (set by AS203314 on routes you receive):
# (203314, 130, 100) -> Asia West
# (203314, 130, 150) -> Asia East
# (203314, 130, 300) -> North America
filter prefer_asia_west_routes_v4 {
if (203314, 130, 100) ~ bgp_large_community then bgp_local_pref = 200;
accept;
}In Control Communities
Control geographic propagation:
bgp_large_community.add((203314, 2, 1)); # Disable cross-region
bgp_large_community.add((203314, 201, 300)); # Exclude North America
bgp_large_community.add((203314, 201, 200)); # Exclude EuropeConfiguration Snippets (JunOS / BIRD2)
The examples below match a learning-region tag or attach an export exclusion. Replace the example prefixes with your authorized announcements.
Exclude North America (203314:201:300)
set policy-options community HATS-NO-NA members large:203314:201:300
set policy-options policy-statement EXPORT-TO-HATS term NO-NA from route-filter 203.0.113.0/24 exact
set policy-options policy-statement EXPORT-TO-HATS term NO-NA then community add HATS-NO-NA
set policy-options policy-statement EXPORT-TO-HATS term NO-NA then accept
set policy-options policy-statement EXPORT-TO-HATS term REJECT-ALL then rejectPrefer routes learned in Asia West (203314:130:100)
set policy-options community HATS-ASIA-W members large:203314:130:100
set policy-options policy-statement IMPORT-FROM-HATS term ASIA-W from community HATS-ASIA-W
set policy-options policy-statement IMPORT-FROM-HATS term ASIA-W then local-preference 200
set policy-options policy-statement IMPORT-FROM-HATS term ASIA-W then acceptRegional Filtering Examples
Accept only Asian routes:
# Allow only Asia West and Asia East
if (community matches 203314:130:1*) then accept
else rejectPrefer local region:
# Higher local preference for Asia West
if (community matches 203314:130:100) then localpref 200
if (community matches 203314:130:150) then localpref 150
if (community matches 203314:130:300) then localpref 100Related Information
- PoP Codes - Specific location codes within regions
- Internal Communities - Using region codes in location-based communities
- Control Communities - Using region codes in traffic engineering
Tip: Region codes are ideal for high-level geographic traffic engineering when you don't need PoP-level granularity.
PoP Codes
Point of Presence (PoP) codes used in AS203314 BGP communities for location-based routing across 16+ PoPs in Hong Kong, Tokyo, Singapore, Amsterdam, Frankfurt, London, Los Angeles, New York, and more.
Hats Network Services
Dedicated access, managed private networks and routing profiles from Hats Network. Compare handoffs, commitments and deployment requirements.