Question
Unable to reach DigitalOcean server from Russia
- Posted on April 11, 2019
- Networking
Asked by jarland
I am unable to reach DigitalOcean droplet IP addresses from any local ISP in Russia. How do I fix this?
(This question is part of a series in which we ask questions using language that is similar to common support tickets, to improve our publicly searchable support database)
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hollie's Hub for Good
Working on improving health and education, reducing inequality, and spurring economic growth? We’d like to help.
Greetings!
I’m sorry to hear about the trouble this is causing for you. While we have heard several cases of ISPs in Russia blocking access to DigitalOcean IP addresses, it is not necessarily a universal truth that customers from Russia cannot reach our servers. For that reason, we prefer not to make assumptions too quickly. The first thing you need to do is run an MTR to our network. You can use your droplet IPs, as well as the hostnames found for all of the speed tests here:
http://speedtest-sfo1.digitalocean.com/
If you have never run an MTR before, this guide should help:
https://www.digitalocean.com/community/tutorials/how-to-use-traceroute-and-mtr-to-diagnose-network-issues
If the MTR consistently halts before reaching our network, your ISP is likely the first call that you need to make. Please do feel free to drop us a line as well, we like to see information that helps us identify connectivity issues for our customers. You can include the result of an MTR in an email to us here:
https://www.digitalocean.com/company/contact
Jarland
Dear Digital ocean,
Users from Russia are complaining our website freedombarometer.org is not accessible in the last 3/4 days, as “the server does not respond”. Can you please explain whether just temporarily there was a problem; when the problem will be resolved if it has not been already; what kind of measures can we take to prevent this from happening again? Looking forward to hearing from you.
I suppose the only option now is to reserve non-blocked “floating ip”(https://www.digitalocean.com/docs/networking/floating-ips/) and assign it to newly created droplet.