Yandex Cloud
Search
Contact UsGet started
  • Blog
  • Pricing
  • Documentation
  • All Services
  • System Status
    • Featured
    • Infrastructure & Network
    • Data Platform
    • Containers
    • Developer tools
    • Serverless
    • Security
    • Monitoring & Resources
    • ML & AI
    • Business tools
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Customer Stories
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Education and Science
    • Yandex Cloud Partner program
  • Blog
  • Pricing
  • Documentation
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for VPC
    • Fixing errors at cloud network deletion
    • Errors in geographic attribution of Yandex Cloud resource IP addresses
    • Resolving issues with network connection speed when accessing cloud resources
    • Resolving errors when setting up TLS connections on VMs
    • Could not delete a security group
    • Resolving issues with sending emails via SMTP from external IP addresses
    • How to disable DDoS protection
    • Moving an external static IP address to another cloud
    • Monitoring incoming or outgoing VM traffic
    • How to determine the speed of communication channels
    • Checking for restrictions on traffic, connection speed, and bandwidth
    • How to change the network or subnet for an MDB cluster
    • How to read the "Connections quota utilization" chart
    • How to assign a fixed IP address to a NAT gateway
    • How to enable Egress NAT
    • How to route traffic between two cloud networks
    • Enabling advanced DDoS protection

In this article:

  • Issue description
  • Solution
  1. VPC
  2. Errors in geographic attribution of Yandex Cloud resource IP addresses

Errors in geographic attribution of Yandex Cloud resource IP addresses

Written by
Yandex Cloud
Updated at September 12, 2023
  • Issue description
  • Solution

Issue descriptionIssue description

  • Governmental sites are blocking connections originating from the VM, considering that the originating IP address is outside Russia.
  • Based on the information from third-party online resources, the external IP address belongs to another country.

SolutionSolution

All external IP ranges in Yandex Cloud are located in Russia.
However, the information on IP ranges is distributed over the internet, and some companies may sometimes fail to timely update their IP attribution data.

If needed, you can get another public IP for your VM. For this, stop the VM in the Yandex Cloud console, and then restart it. If the VM parameters use a dynamic public IP, when you stop and then start such a VM, it gets a new IP. You can make this IP static if needed. A static IP address will not change when you stop your VM.

Note

Public IP ranges for Yandex Cloud are listed here. To check the country of your IP, use the whois command or the RIPE public resource.

You can also try moving your VM to a different availability zone. For this, follow this guide.

To make a VM's public IP address static, do the following:

  1. When your VM is running, in the cloud console, click "Virtual Private Cloud".
  2. Go to "IP addresses".
  3. Find the IP address in the list.
  4. On the right of the IP line, click "...".
  5. In the menu that opens, select Make static.

For more information, see the documentation section.

Was the article helpful?

Previous
Fixing errors at cloud network deletion
Next
Resolving issues with network connection speed when accessing cloud resources
© 2025 Direct Cursus Technology L.L.C.