You can now change the default VPC network for a region. When you change the default VPC network for a region, the new default network will be automatically selected during applicable resource set ups unless otherwise specified.
All Droplets created after 1 October 2020 are placed into a VPC network by default. You can no longer manually enable VPC networking on existing Droplets. You can migrate existing Droplets into VPC networks using Snapshots.
The SFO3 datacenter region is now available.
The DigitalOcean Virtual Private Cloud (VPC) service is now available for all customers. VPC replaces the private networking service. Existing private networks will continue to function as normal but with the enhanced security and features of the VPC service. See the description of VPC features for more information.
v1.16.0 of the DigitalOcean Terraform Provider is now available. This release includes VPC support and expanded Spaces support.
We began the incremental release of the DigitalOcean Virtual Private Cloud (VPC) service. It will be available for all customers soon. VPC replaces the private networking service.
DigitalOcean Managed Databases now support private networking. New database clusters will provision with private networking enabled. Existing clusters will require an update to connect over the private network.
With the release of private networking isolation in NYC3, private networks are restricted to each user account in all regions.
Private networking isolation was released in the NYC2 datacenter.
Private networking isolation was released in the NYC1 datacenter.
Private networking isolation was released in the SFO1 and SGP1 datacenters.
Private networking isolation continued with releases in the LON1, AMS3, FRA1, and SFO2 datacenters.
Private networking isolation was released in the AMS2, BLR1, and TOR1 datacenters. Communication over the private network in those datacenters is now restricted to other resources within an account or team.