Russian mirror setup for hub domains
Last updated: May 26, 2026
Russian mirror setup for hub domains
For projects that need a Russia-specific mirror because the main hub domain may be intermittently blocked, Aghanim can configure a separate mirror domain and route Russian users to it automatically.
How the routing works
- Players initially open the original hub domain as usual.
- Cloudflare identifies users from Russia by IP and returns a
302redirect to the mirror domain for that audience. - Users outside Russia continue to use the original domain.
- If a Russian user is using a VPN and is not identified as being in Russia at the Cloudflare layer, they will not be redirected.
From the player’s perspective, the experience remains seamless: they still start from the main domain, whether they open it directly in a browser or via an in-game link.
Mirror domain options
You can use a dedicated subdomain such as ru.example.com for Russian traffic.
- If the customer manages DNS for that subdomain, they should create an A record pointing to
103.151.135.62. - If Aghanim manages the domain or subdomain on the customer’s behalf, Aghanim can configure the record directly.
After DNS is configured
Once the DNS record is in place, allow a short window for the mirror environment to recognize the domain and issue the SSL certificate. After SSL is active, the team can proceed with testing or go live.
Hosting and traffic flow
The current Russian mirroring setup uses Gcore in front of Google Cloud Platform (GCP):
- Russian mirror traffic: mirror domain -> Gcore -> GCP
- Other traffic: original domain -> Cloudflare -> GCP
Within Gcore, the setup can use CDN caching for static assets together with WAF / WAAP, anti-DDoS protections, and load balancing before proxying requests to the same GCP-hosted application and databases.
Operational notes
- The main and mirror domains are fully isolated entry points, with separate domains and certificates.
- The routing can be reconfigured or disabled if needed.
- The mirror is intended to help Russian users reach the hub even when access to the primary domain is disrupted.