Russian traffic access via mirror domain

If some users in Russia cannot open the Aghanim hub without a VPN, the issue may be caused by regional blocking of Cloudflare, which Aghanim uses for traffic filtering, CDN, DDoS protection, and related network functions. In this situation, part of the traffic from Russia may experience intermittent access problems.

How the mirror setup works

1. Players still open the main hub domain first.
2. Russian traffic is then automatically routed to a mirror domain.
3. Routing is determined by Cloudflare based on the user’s IP address.
4. If a player in Russia uses a VPN, they may not be recognized as Russian traffic and therefore may not be redirected to the mirror.
5. The redirect is intended to be seamless for the player and can be reconfigured or disabled if needed.

Domain setup options

To enable the mirror for Russian traffic, one of the following approaches can be used:

• Customer-managed domain: create a separate domain for Russian traffic and point it to the mirror IP provided by Aghanim. In the referenced support case, the required DNS record was an A record pointing to 103.151.135.62.
• Aghanim-managed default domain: if creating a separate domain is inconvenient, Aghanim can prepare a default domain and configure the routing on its side, with no customer-side DNS work required.

After DNS changes

After the DNS record is added or changed, allow a short setup window for the mirror to pick up the domain and issue an SSL certificate. Once that completes, testing can begin.

When to use this setup

This setup is relevant when Russian users have trouble accessing the hub without a VPN and a dedicated routing path is needed specifically for Russian traffic while keeping the main domain unchanged for other regions.