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.txt is the recommended profile.
• WZ - EU Relay whitelist and 185.34.104.0/22 are 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 city
• medium: useful overlap, but broader, mixed, or regional rather than city-clean
• weak: still a practical profile, but geofeed support is limited

Supported Profiles

• cdg-paris - CDG / Paris -> FR - metro match - strong - 360 networks
• fra-frankfurt - FRA / Frankfurt -> DE + HE Frankfurt - exact city and regional family - strong - 350 networks
• ams-amsterdam - AMS / Amsterdam -> NL - exact city / regional hub - strong - 342 networks
• lhr-london - LHR / London -> UK - exact city and regional family - strong - 341 networks
• man-manchester - MAN / Manchester -> UK - regional match - medium - 341 networks
• waw-warsaw - WAW / Warsaw -> PL - exact city / regional hub - strong - 403 networks
• mad-madrid - MAD / Madrid -> ES - exact city / regional hub - strong - 412 networks
• nrt-tokyo - NRT / Tokyo -> Asia / Japan - metro / regional match - medium - 407 networks
• itm-osaka - ITM / Osaka -> Asia / Japan - regional match - medium - 407 networks
• sgp-singapore - SGP / Singapore -> Asia / Singapore - city / regional match - medium - 402 networks
• syd-sydney - SYD / Sydney -> OCE - regional match - medium - 415 networks
• mel-melbourne - MEL / Melbourne -> OCE - regional match - weak - 415 networks
• tlv-tel-aviv - TLV / Tel Aviv -> Middle East - regional match - weak - 412 networks
• jnb-johannesburg - JNB / Johannesburg -> South Africa - regional match - weak - 413 networks
• ewr-new-jersey - EWR / New Jersey -> US East - NY - metro match - strong - 403 networks
• ord-chicago - ORD / Chicago -> US East - Chicago - metro match - strong - 407 networks
• atl-atlanta - ATL / Atlanta -> US East - Atlanta - exact city - strong - 405 networks
• mia-miami - MIA / Miami -> US East - Miami - exact city - strong - 402 networks
• dfw-dallas - DFW / Dallas -> US Cent - Texas - exact regional match - strong - 400 networks
• sea-seattle - SEA / Seattle -> US West - Washington - metro / regional match - medium - 412 networks
• lax-los-angeles - LAX / Los Angeles -> US West - California - regional match - medium - 404 networks
• sjc-silicon-valley - SJC / Silicon Valley -> US West - California - regional match - medium - 404 networks

Not Included

These Vultr datacenters currently have no clear COD-hub counterpart in the source data:

• blr / Bangalore
• bom / Mumbai
• del / Delhi NCR
• hnl / Honolulu
• icn / Seoul
• mex / Mexico City
• sao / Sao Paulo
• scl / Santiago
• sto / Stockholm
• yto / Toronto