Choosing a region

Infinity-Filter runs edge PoPs in Canada, Germany, France, and Poland. The CNAME suffix on your domain decides which PoP receives player traffic for that domain. Choose deliberately.

Why manual selection is intentional

Manual selection gives you a stable, predictable path. The trade-off: you have to pick. The Latency Test makes it easy.

What the region affects

What	Affected by the CNAME region?
Player → edge latency	✅ Yes — pick the PoP closest to your players
Edge → backend latency	✅ Yes — pick the PoP closest to your backend
Mitigation capacity	❌ No — all PoPs share the same upstream capacity
Country flag in the launcher	✅ Yes — the launcher derives it from the CNAME region
Dedicated IP location (Bedrock / voice)	❌ No — the dedicated IP has its own region (see Dedicated IP)

The picking rule

For each domain in your network:

1. 1

   Find your player base

   If your audience is mostly EU, you’ll usually want DE, FR, or PL. North-American players are best served by CA.

2. 2

   Find your backend

   The PoP also needs to be close to your backend, because every player request adds one edge-to-backend hop on top. Use the Latency Test — it pings your backend from every PoP and gives you the RTT.

3. 3

   Pick the PoP that minimizes both hops

   The best PoP is the one with the lowest RTT to your backend, in the geographic region of your players.

   Adjacent EU PoPs (DE / PL / FR) often differ by only a couple of milliseconds. If your players are in Western Europe and DE and FR give 4 ms vs. 6 ms to your backend, pick DE — it’s marginally cheaper but the user-facing difference is negligible.

Switching region

Switching CNAME region is non-disruptive:

• Existing connections keep their backend — they don’t drop.
• New connections use the new region once DNS propagates.

Before flipping, allowlist the new PoP’s IP ranges at your backend firewall — see Firewall IP ranges.

Per-domain vs. per-network

The region is set per domain on the Domains page — not at the network level. Two domains in the same network can use two different regions. That’s useful if you serve geographically split audiences (eu.example.com on DE, na.example.com on CA) but want them all to land on the same backend pool.

The selected region is remembered in the panel (localStorage) so it’s the default the next time you open the page.

Latency you should expect

Going through Infinity-Filter adds the edge-to-backend hop on top of the player-to-edge RTT. The added cost is typically 3–6 ms. Higher ping vs. a direct connection is normal — that’s the price of inspecting traffic at the edge.

For Bedrock and voice modules, latency depends on the dedicated IP’s PoP, not the Java edge’s. The dedicated IP may sit in a different PoP than the Java edge, which adds another ~10–15 ms compared to the closest Java region.

What’s next