Profiles
One directory per supported Vultr datacenter profile.
Only Vultr datacenters with a clear COD-hub counterpart are included.
Profiles are built from three inputs:
- Vultr datacenter availability
- COD source tags and ranges
- Vultr geofeed location evidence from geofeed.constant.com/?yaml
Rules
blocklist.txtis the recommended profile.WZ - EU Relay whitelistand185.34.104.0/22are kept open.- XML ranges are translated to CIDR.
- The Google rule is not included.
- Some Vultr datacenters share the same COD-hub mapping.
- Geofeed evidence is used as support, not as proof of exact in-game server selection.
- Source tag labels in the docs may be normalized slightly for readability.
Evidence levels:
strong: clean or dominant geofeed overlap with the mapped metro or citymedium: useful overlap, but broader, mixed, or regional rather than city-cleanweak: still a practical profile, but geofeed support is limited
Supported Profiles
cdg-paris-CDG / Paris->FR-metro match-strong-360networksfra-frankfurt-FRA / Frankfurt->DE + HE Frankfurt-exact city and regional family-strong-350networksams-amsterdam-AMS / Amsterdam->NL-exact city / regional hub-strong-342networkslhr-london-LHR / London->UK-exact city and regional family-strong-341networksman-manchester-MAN / Manchester->UK-regional match-medium-341networkswaw-warsaw-WAW / Warsaw->PL-exact city / regional hub-strong-403networksmad-madrid-MAD / Madrid->ES-exact city / regional hub-strong-412networksnrt-tokyo-NRT / Tokyo->Asia / Japan-metro / regional match-medium-407networksitm-osaka-ITM / Osaka->Asia / Japan-regional match-medium-407networkssgp-singapore-SGP / Singapore->Asia / Singapore-city / regional match-medium-402networkssyd-sydney-SYD / Sydney->OCE-regional match-medium-415networksmel-melbourne-MEL / Melbourne->OCE-regional match-weak-415networkstlv-tel-aviv-TLV / Tel Aviv->Middle East-regional match-weak-412networksjnb-johannesburg-JNB / Johannesburg->South Africa-regional match-weak-413networksewr-new-jersey-EWR / New Jersey->US East - NY-metro match-strong-403networksord-chicago-ORD / Chicago->US East - Chicago-metro match-strong-407networksatl-atlanta-ATL / Atlanta->US East - Atlanta-exact city-strong-405networksmia-miami-MIA / Miami->US East - Miami-exact city-strong-402networksdfw-dallas-DFW / Dallas->US Cent - Texas-exact regional match-strong-400networkssea-seattle-SEA / Seattle->US West - Washington-metro / regional match-medium-412networkslax-los-angeles-LAX / Los Angeles->US West - California-regional match-medium-404networkssjc-silicon-valley-SJC / Silicon Valley->US West - California-regional match-medium-404networks
Not Included
These Vultr datacenters currently have no clear COD-hub counterpart in the source data:
blr/ Bangalorebom/ Mumbaidel/ Delhi NCRhnl/ Honoluluicn/ Seoulmex/ Mexico Citysao/ Sao Pauloscl/ Santiagosto/ Stockholmyto/ Toronto