Internal BGP Communities

Internal BGP communities for AS203314 indicating route origin types, PoP locations, and geographic regions.

Internal communities indicate where routes are learned from and whether they are uniquely announced. These communities help you identify the source and path of routes received from AS203314.

Community Format: 203314:XXX:YY where XXX is the category and YY is the specific value.

Route Origin

These communities indicate how a route was learned by Hats Network:

Community	Description	Unique
`203314:110:10`	Route learned from Upstream	Yes
`203314:110:20`	Route learned from Downstream	Yes
`203314:110:30`	Route learned from Peering	Yes
`203314:110:110`	Route originated within Hats Network	Yes

Unique means this route is only announced via this method—if you see 203314:110:30, the route is exclusively available via peering.

PoP-Based Communities

These communities identify which PoP a route was learned at or passed through:

Routes learned at a specific PoP (entry point):

Community	Description	Unique
`203314:120:XXX`	Route learned at PoP `XXX`	Yes

Example: 203314:120:101 means the route was learned at Hong Kong (HKG1).

Routes that passed through a PoP (transit):

Community	Description	Unique
`203314:125:XXX`	Route passed through PoP `XXX`	No

Example: 203314:125:101 means the route passed through Hong Kong (HKG1).

Region-Based Communities

These communities identify which region a route was learned in or passed through:

Routes learned within a specific region:

Community	Description	Unique
`203314:130:XX`	Route learned in Region `XX`	Yes

Example: 203314:130:100 means the route was learned in Asia (West).

Routes that passed through a region:

Community	Description	Unique
`203314:135:XX`	Route passed through Region `XX`	No

Example: 203314:135:100 means the route passed through Asia (West).

Usage Examples

Identify Route Source

Determine if a route comes from peering, upstream, or our customers:

# If you see:
203314:110:30  → Learned from Peering (unique)
203314:110:10  → Learned from Upstream (unique)
203314:110:20  → Learned from Downstream (customer)

Identify Entry Location

Determine where a route entered our network:

203314:120:101  → Entered at HKG1 (Hong Kong)
203314:120:131  → Entered at TYO2 (Tokyo)
203314:120:302  → Entered at IAD (Ashburn)

Filter by Region

Accept routes only from specific regions:

# Only accept routes learned in Asia West
if (community matches 203314:130:100) then accept

# Reject routes that passed through Europe
if (community matches 203314:135:2*) then reject

PoP Codes — Reference for PoP numbers (XXX)
Region Codes — Reference for region numbers (XX)
Control Communities — Traffic engineering communities

Tip: Internal communities are automatically attached to routes we announce to you. Use them to make informed routing decisions based on route origin and location.

Internal BGP Communities

On this page