VPC Release Notes

April 2025

1 April

• Partner Network Connect is now in general availability. Create a partner attachment to establish high-bandwidth, low-latency network connections directly between DigitalOcean VPC networks and other public cloud providers or on-premises datacenters.

March 2025

7 March

• The 10.229.0.0/16 VPC IP address range is now reserved in all regions for DigitalOcean internal use. You may not create new VPC networks with subnets that overlap this range.

December 2024

12 December

• VPC-native networking is now in general availability for all DigitalOcean Kubernetes (DOKS) customers. VPC-native networking allows customers to route traffic directly between DOKS pods, services, and other resources on VPC networks. For more information, refer to the DOKS Features page.

• DigitalOcean Virtual Private Cloud (VPC) peering is now in general availability. VPC peering allows you to join two VPC networks with a secure, private connection. Read How to Create a VPC Peering to get started.

October 2024

15 October

• VPC-native networking is now available in early availability for all DigitalOcean Managed Kubernetes (DOKS) customers. VPC-native networking allows customers to route traffic directly between DOKS pods, services, and other resources on VPC networks. For more information, see the DOKS Features page.

• DigitalOcean Virtual Private Cloud (VPC) peering is now in early availability. VPC peering allows you to join two VPC networks with a secure, private connection. See How to Create a VPC Peering to get started.

October 2020

26 October

• 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.

1 October

• 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.

April 2020

28 April

• 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.

14 April

• v1.16.0 of the DigitalOcean Terraform Provider is now available. This release includes VPC support and expanded Spaces support.

7 April

• 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.

May 2019

29 May

• 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.

July 2018

18 July

• With the release of private networking isolation in NYC3, private networks are restricted to each user account in all regions.

17 July

• We have released private networking isolation in NYC2.

16 July

• We have released private networking isolation in NYC1.

12 July

• We released private networking isolation in SFO1 and SGP1.

11 July

• Private networking isolation continued with releases in LON1, AMS3, FRA1, and SFO2.

10 July

• We have released private networking isolation in AMS2, BLR1, and TOR1. Communication over the private network in those datacenters is now restricted to other resources within an account or team.