Bandwidth Billing

Details on bandwidth billing for DigitalOcean products are included on the respective products’ overview pages. This page summarizes the same information for all products that charge for bandwidth.

Bandwidth billing is automated and you can view your charges on your invoice. There are no regional variations on bandwidth pricing.


Droplets include free outbound data transfer, starting at 1000 GB/month for the smallest plan. Excess data transfer is billed at $.01/GB. For example, the cost of 1000 GB of overage is $10. Inbound bandwidth to Droplets is always free.

Any data transfer sent by a Droplet using a public network interface will count against the transfer pool for that Droplet’s account. Data transfer between Droplets over the private network uses a private network interface.

Transfer allowance is pooled cumulatively at the account level, not individually at the Droplet level. For example, if you run two Droplets for a full month, each with 1000 GB/month allowance, you accrue a 2000 GB allowance. Let’s say you transfer 1500 GB of data with the first Droplet, which is over its individual limit, and 100 GB of data with the second Droplet, you would still be under the total limit of 2000 GB by 400 GB and would not be charged any overage fees.

Accrued transfer does not roll over between months and cannot be transferred between accounts or teams.

Monthly Allowance

Your monthly transfer allowance depends on your monthly Droplet usage; for every hour Droplet exists, it accrues transfer allowance.

Droplets are billed per hour up to a maximum of 672 hours per month (28 days multiplied by 24 hours). For every hour the Droplet exists during the month, whether it’s powered on or not, it will earn 1672 of its total allocation up to that limit. Once it’s been active for 672 hours, it has reached its full bandwidth allowance.

For example, if a Droplet’s maximum monthly data transfer allowance is 1000 GB, it will accrue 1000 GB / 672 hours = 1.5 GB per hour that the Droplet exists. Fractional usage is rounded to increments of 1 GB: 1.49 GB of use will be rounded down to 1 GB and 1.5 GB will be rounded up to 2 GB.

Estimated Droplet Transfer Pool

We collect usage data and display projections about your transfer pool, which you can view on your account’s Billing page.

Estimates are based on the assumption that the same daily averages for both the number of active Droplets and bandwidth usage will be maintained through the end of the month. Outbound data transfer and projected transfer allowance are updated once daily.

Billing alerts are triggered on the basis of actual usage, so projections of transfer in excess of the transfer pool will not trigger a billing alert until they are applied to the invoice.


Spaces subscriptions include 1TB of outbound data transfer (from Spaces to the internet), which is shared between all Spaces. Additional outbound transfer is $0.01/GB. Outbound data transfer is free in the following cases:

  • From Spaces in NYC3 to Droplets in NYC1, NYC2, and NYC3
  • From Spaces in SGP1 to Droplets in SGP1
  • From Spaces in SFO2 to Droplets in SFO1 and SFO2
  • From Spaces in AMS3 to Droplets in AMS2, AMS3, LON1, and FRA1
  • From Spaces in FRA1 to Droplets in AMS2, AMS3, LON1, and FRA1

Inbound bandwidth to Spaces never counts against your Spaces transfer allowance.

Droplets have their own transfer allowance, independent of Spaces. Traffic from Droplets to Spaces does not count against your Spaces transfer allowance (because inbound bandwidth to Spaces is free), but does currently count against your Droplets’ outbound transfer allowance. We’re working on changing this behavior.


Inbound data transfer is included in the price of the cluster. Outbound data transfer billing is waived until January 1, 2020, at which time it will be billed at $0.01/GB.

Load Balancers

There are no bandwidth charges for DigitalOcean Load Balancers because they are bandwidth neutral. In other words, load balancers themselves don’t change the amount of data transferred by Droplets. Bandwidth costs are based on the data transfer of the Droplets included in the load balancer’s backend, taking into consideration their own transfer limits.