By robertvazan
It looks like there’s a bug in routing floating IPs. When connecting from another droplet within the same datacenter through floating IP, the connection sometimes works and sometimes doesn’t. Using droplet’s own IP address immediately resolves the problem at the cost of losing floating IP functionality.
That means floating IPs are presently useless for backend servers. It also means it is impossible to publish application APIs through floating IP address, because there is always some non-trivial probability that some API client happens to be in the same datacenter.
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!
I just got bit by this with crazy timeouts when trying to access my own droplet by its DNS name which is tied to the floating IP.
What is going on with this? Any plans to fix it?
I’m also experiencing this issue. Very annoying that you have to ping to fix it. Spent 2 days trying to troubleshoot this and finally found this post. Please fix @BrookDO
This comment has been deleted
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.