Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

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.
I was looking for a similar question, and already shared the answer I found on another thread where you asked the same question. <br> <br>Private IPs are next on the list, according to Rayiu on this thread (https://www.digitalocean.com/community/questions/additional-ip-addresses-internal-network-ip-addresses). <br> <br>But I believe it will not be possible to use the private IPs on inter-datacenters communication, only inside the same data center. So, to communicate form NYC to AMS you will have to use public IPs, wich will count in your data transfer cap.
We will be deploying private IPs in the future which will allow droplets in the same DC to talk to each other without any charges. <br> <br>Currently using the public IPv4 address you will still be traversing the local network in terms of performance and latency. <br> <br>We have not yet made a determination if we will be providing inter DC connectivity free of charge the simplest way to do so would be to merge the private networks across the locations however creating such a large pool can cause other networking issues so it’s very possible that for communication between DCs you would be charged for data transfer.