Set up a mirror domain for Russian traffic access to the Hub, Web Shop, and Newsfeed

Last updated: June 29, 2026

If some players in Russia cannot access the Hub, Web Shop, or Newsfeed, Aghanim can route Russian traffic through a mirror domain.

How the routing works

  1. Players continue opening the main Hub domain as usual.
  2. Russian traffic is detected at the Cloudflare level by IP and is automatically routed to the mirror domain.
  3. The redirect is seamless for players.
  4. Players in Russia who use a VPN are not redirected, because routing is based on IP geolocation.
  5. The routing scheme can be reconfigured or disabled quickly if needed.

What is required from the game team

If your traffic comes from multiple regions and the main domain must stay unchanged, set up a separate domain for Russian traffic.

  • Create a dedicated subdomain or domain for Russian traffic.
  • Add an A record pointing that domain to 103.151.135.62.

If creating a separate domain on your side is inconvenient, Aghanim can provide a default domain and handle the setup without requiring changes from your team.

After DNS is updated

After the DNS change is made, allow a short setup window for the mirror to pick up the domain and issue an SSL certificate. After that, proceed with testing before switching traffic.

API requests from Russia

The same mirror routing also applies to Aghanim platform domains used for API traffic.

  • Aghanim stated that mirrors exist for all platform domains, regardless of whether requests come from a client or a server.
  • For Russian traffic, requests sent to a platform domain such as api.aghanim.com may be redirected to the mirror domain api.aghanim.store.
  • Aghanim indicated that this is a single redirect.

Implementation note for clients and servers

Clients or backend services that call Aghanim domains directly should allow HTTP redirects when operating from Russia or when serving Russian traffic. If redirect handling is disabled, requests may fail even though the mirror routing is working as intended.

Notes

  • This approach is intended to restore access for affected Russian traffic while keeping the main domain unchanged.
  • The setup described here was communicated for Hub access, including Web Shop and Newsfeed availability.
  • If you test from Russia while connected through a VPN, you may not be redirected to the mirror because routing is based on the source IP.