0

Moscow (Anexia) server node is down/inactive for Russian users

Hello NextDNS Team,

I am writing to report that the Moscow server node (provided by Anexia), which previously handled traffic for users in Russia, appears to be completely down or excluded from the Anycast routing.

Currently, all traffic from Russia is being rerouted to distant European nodes (like Stockholm, Frankfurt, or Vienna). This causes a massive spike in latency (ping is over 80–120ms instead of the usual 5–15ms) and severely degrades the user experience.

I have already contacted Anexia support regarding this matter. They informed me that the infrastructure status and routing decisions within the Anycast network are entirely managed on your side, and they advised me to reach out to NextDNS directly to check the contract/routing status for the Moscow location.

Could you please check if the Moscow (Anexia) node is temporarily disabled due to a technical glitch, or if it has been permanently decommissioned? If it's a technical issue, please restart or re-announce the prefix for this region.

Thank you for your time and assistance.

Best regards,

1 reply

null
    • NextDNs
    • 6 hrs ago
    • Reported - view

    Anexia closed their russian PoP. It is becoming more and more difficult to maintain Russian anycast presence. You can use ultralow by switching to DoH or DoT.

Content aside

  • 6 hrs agoLast active
  • 1Replies
  • 16Views
  • 2 Following