Hats Network | LogoHats Network
BGP Communities

PoP Codes

Point of Presence (PoP) codes used in AS203314 BGP communities for location-based routing.

Each Point of Presence (PoP) has a unique 3-digit code used in community strings like 203314:120:XXX and 203314:202:XXX.

Usage: These codes identify specific PoP locations in internal communities (120:XXX, 125:XXX) and control communities (202:XXX).

PoP Code Reference

LocationIATAGenerationTypePoP CodeNotes
Hong KongHKG1Gen2Core101Unique
Hong KongHKG2Gen2Core102Unique
Hong KongHKG3Gen2Core103
TaiwanTPE1Gen2Core121
TaiwanTPE2Gen2Core122
TokyoTYO1Gen2Edge111
TokyoTYO2Gen2Core131Unique
SingaporeSIN1Gen2Core151Unique
SeattleSEAGen2Core301
AshburnIADGen2Core302
San JoseSJCGen2Edge303
MoscowMOWGen2Core201
FrankfurtFRAGen2Edge252
ZurichZRHGen2Edge251
AmsterdamAMSGen2Edge253
BerlinBERGen2Edge254Unique
LondonLONGen2Edge255Unique
MelbourneMELGen2Edge451

Type Definitions

  • Core PoP: Major interconnection points with multiple upstream providers
  • Edge PoP: Smaller presence focused on local connectivity

Generation Definitions

  • Gen2: Second-generation infrastructure (current deployment)

Using PoP Codes

In Internal Communities

Identify where a route was learned:

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

In Control Communities

Exclude specific PoPs from receiving announcements:

203314:202:301  → Do not announce via Seattle
203314:202:131  → Do not announce via Tokyo
203314:202:102  → Do not announce via HKG2

Tip: PoP codes are primarily used for granular traffic engineering when you need to control route propagation at the location level.

On this page