Source: README.md

COD DMZ Vultr Datacenter Guide

Public guide for building a Vultr-based COD/DMZ VPS that is mapped to a corresponding COD hub family.

Purpose

The goal is to place the player behind a VPS in a chosen region and keep the matching COD hub family open while blocking competing hub families.

In practice, this is used to:

steer matchmaking toward the hub family that best matches the chosen Vultr datacenter
keep the client inside the expected network environment for that region
improve session continuity when lobbies become unstable, routes change, or mitigation systems alter external reachability

This repository is about traffic shaping and region targeting. It is not a guarantee of a specific server, match, or datacenter.

Start Here

Read howto.md for the beginner workflow.
Use this file for the profile map and project overview.
Use profiles/ to choose the matching datacenter profile.
Use data/ if you want to inspect the source data and evidence.

Concept

Choose the Vultr datacenter you want to deploy in.
Use the profile that matches that datacenter.
The profile keeps the matching COD hub family open.
All other supported regions are blocked.
Relay and control-plane networks stay open.

This does not guarantee that the game lands in the exact same physical datacenter. It is a traffic-shaping model: place the client in the right location, then block competing hubs until the matching hub family is the most likely remaining path.

Structure

howto.md: beginner workflow, client side, and VPS side
data/: COD source data, Vultr geofeed, and normalized CSV
profiles/: Vultr-datacenter profiles

Sources

COD source tags and ranges: data/cod_block_external.txt
Normalized COD source table: data/cod_block_full_by_origin.csv
Vultr regions reference: api.vultr.com/v2/regions
Vultr geofeed reference: geofeed.constant.com/?yaml
Local geofeed snapshot and summary: data/vultr_geofeed.yaml, data/vultr_geofeed.csv, data/vultr_geofeed_summary.md

The Vultr regions endpoint tells you which datacenters exist. The geofeed adds prefix-to-city evidence. The COD source data tells you which hub families the blocklists refer to. Profiles are built where those three sources line up cleanly enough to be useful.

Supported Vultr Datacenters

Only datacenters with a clear COD-hub match are included.

Vultr	Code	Profile	COD hub mapping	Match type	Evidence
Paris	`cdg`	`profiles/cdg-paris/`	`FR`	metro match	strong
Frankfurt	`fra`	`profiles/fra-frankfurt/`	`DE + HE Frankfurt`	exact city and regional family	strong
Amsterdam	`ams`	`profiles/ams-amsterdam/`	`NL`	exact city / regional hub	strong
London	`lhr`	`profiles/lhr-london/`	`UK`	exact city and regional family	strong
Manchester	`man`	`profiles/man-manchester/`	`UK`	regional match	medium
Warsaw	`waw`	`profiles/waw-warsaw/`	`PL`	exact city / regional hub	strong
Madrid	`mad`	`profiles/mad-madrid/`	`ES`	exact city / regional hub	strong
Tokyo	`nrt`	`profiles/nrt-tokyo/`	`Asia / Japan`	metro / regional match	medium
Osaka	`itm`	`profiles/itm-osaka/`	`Asia / Japan`	regional match	medium
Singapore	`sgp`	`profiles/sgp-singapore/`	`Asia / Singapore`	city / regional match	medium
Sydney	`syd`	`profiles/syd-sydney/`	`OCE`	regional match	medium
Melbourne	`mel`	`profiles/mel-melbourne/`	`OCE`	regional match	weak
Tel Aviv	`tlv`	`profiles/tlv-tel-aviv/`	`Middle East`	regional match	weak
Johannesburg	`jnb`	`profiles/jnb-johannesburg/`	`South Africa`	regional match	weak
New Jersey	`ewr`	`profiles/ewr-new-jersey/`	`US East - NY`	metro match	strong
Chicago	`ord`	`profiles/ord-chicago/`	`US East - Chicago`	metro match	strong
Atlanta	`atl`	`profiles/atl-atlanta/`	`US East - Atlanta`	exact city	strong
Miami	`mia`	`profiles/mia-miami/`	`US East - Miami`	exact city	strong
Dallas	`dfw`	`profiles/dfw-dallas/`	`US Cent - Texas`	exact regional match	strong
Seattle	`sea`	`profiles/sea-seattle/`	`US West - Washington`	metro / regional match	medium
Los Angeles	`lax`	`profiles/lax-los-angeles/`	`US West - California`	regional match	medium
Silicon Valley	`sjc`	`profiles/sjc-silicon-valley/`	`US West - California`	regional match	medium

Current Vultr regions were verified from the official Vultr regions endpoint on April 8, 2026. The Vultr geofeed was also reviewed on April 8, 2026 as supporting location evidence for several profiles, especially Paris, Frankfurt, Amsterdam, London, New Jersey, Chicago, Atlanta, Miami, and Singapore.

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

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

Important

Standard profiles leave WZ - EU Relay whitelist and 185.34.104.0/22 open.
The Google rule is not included in the standard profiles.