Secure and control the traffic to your applications with private networking, traffic filtering, and load balancing.

Manage DNS for Droplets, DigitalOcean Load Balancers, and non-DigitalOcean resources all in the same place.
4 articles
DigitalOcean Floating IPs are publicly-accessible static IP address that you can assign to Droplets and instantly remap to other Droplets in the same datacenter.
4 articles
Load balancers distribute traffic across pools of Droplets for high availability setups.
4 articles
Restrict traffic with network-based, stateful firewalls for Droplets.
4 articles
IPv6 is intended to replace IPv4 and provide a larger address space, increased security, and other benefits. DigitalOcean currently only supports IPv6 for Droplets. You can enable IPv6 on a Droplet to gain access to its 16 configurable IPv6 addresses.
4 articles
A Virtual Private Cloud (VPC) is a private network interface for collections of DigitalOcean resources. VPC networks provide a more secure connection between resources because the network is inaccessible from the public internet and other VPC networks. Traffic within a VPC network doesn’t count against bandwidth usage.
4 articles

Latest Updates

19 January 2022

  • Managed Let’s Encrypt certificates will begin using Elliptic Curve Digital Signature Algorithm (ECDSA) instead of RSA. ECDSA is equally secure and more computationally efficient than RSA. ECDSA certificates follow the shorter root chain and aren’t rooted using the DST Root CA X3 cross-sign which expired on 30 September 2021.

    As we roll out this change, new Let’s Encrypt certificates provisioned for DigitalOcean Load Balancers and Spaces will increasingly use ECDSA and existing certificiates secured with RSA will be secured with ECDSA upon auto-renewal. This change doesn’t require any action from DigitalOcean customers.

10 January 2022

  • You can now resize load balancers once per minute, instead of once per hour. The cost is prorated based on how long the load balancer operates at each size, with a minimum charge of $0.01.

9 November 2021

  • You can now scale load balancers with more granularity by adding or removing nodes. The number of nodes a load balancer contains determines how many simultaneous connections and requests per second it can manage.

    Each additional node increases the load balancer’s maximum:

    • Requests per second by 10,000
    • Simultaneous connections by 10,000
    • New SSL connections per second by 250

    You can add up to 100 nodes to a load balancer.

    The scaling feature is not available in the following regions at this time: AMS2, NYC2, SFO1. In these regions, you can only create load balancers with one node, which equates to a small size load balancer under the legacy scaling system.

    The load balancer’s cost per month is based on the number of nodes it contains.

For more information, see the full release notes.