Referencing https://www.digitalocean.com/docs/networking/vpc … it read that a given customer can only have one VPC using, say, 10.10.0.0/16:

VPC network ranges cannot overlap with the ranges of other networks in the same account.

Why would this limit be in place, if multiple customers can have otherwise-overlapping private IP space?

Does assigning a VPC to a different Project still suffer from the same cannot-overlap-IP-space constraint?

When the docs say “VPC network ranges cannot overlap with the ranges of other networks in the same account”, is that across all datacenters & regions? Or is it intra-DC/-region only? Ie, could I deploy 10.10.0.0/16 to both FRA1 and NYC3? The statement

We do not support VPC networks between resources in different datacenter regions

would seem to indicate overlapping private IP space could be handed-out to the same account, so long as it’s not in the same place. Is that the case?

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.

×
Submit an Answer
1 answer

Hi there,

Yes, your VPC IP ranges are isolated from other accounts so they can overlap with the VPC IP ranges of other accounts. However indeed, as you stated, the IP rages can not overlap in the same account.

This is also the case for separate projects, as the projects are still under the same account.

This is also true for different regions, for example, if you have this IP rage: 10.136.0.0/16 for NYC1, if you try to add the same range for FRA1 it will not work and you will get the following message:

This range/size overlaps with another VPC network in your account. 

Learn more about setting IP ranges

default-nyc1 10.136.0.0/16

It will also automatically provide you with an alternative range you could use.

Hope that this helps.
Regards,
Bobby