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.
You can calculate bandwidth costs using our Bandwidth Calculator.
Droplets include free outbound data transfer, starting at 1,000 GiB/month for the smallest plan. Excess data transfer is billed at $0.01/GiB. For example, the cost of 1,000 GiB 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. All IPv6 traffic uses the public interface. Data transfer between Droplets over the VPC 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 1,000 GiB/month allowance, you accrue a 2,000 GiB allowance. Let’s say you transfer 1,500 GiB of data with the first Droplet, which is over its individual limit, and 100 GiB of data with the second Droplet, you would still be under the total limit of 2000 GiB by 400 GiB and would not be charged any overage fees.
Accrued transfer does not roll over between months and cannot be transferred between accounts or teams.
Your monthly transfer allowance depends on your monthly Droplet usage; for every hour a 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 1/672 of its total allowance 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 1,000 GiB, it will accrue 1,000 GiB / 672 hours ≈ 1.5 GiB per hour that the Droplet exists. Droplet usage is rounded to the nearest hour.
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.
Kubernetes worker nodes are billed per hour up to a maximum of 744 hours per month (31 days multiplied by 24 hours). As a result, they can accrue extra bandwidth allowance beyond the advertised monthly allowance for the corresponding Droplet plan.
App Platform bundles a certain amount of bandwidth per component for the Starter, Basic, and Professional tiers.
|Outbound transfer||1 GiB||40 GiB||100 GiB|
If an App Platform component uses more bandwidth than this, it will be billed at a rate of $0.10 per GiB.
Spaces subscriptions include 1,024 GiB of outbound data transfer (from Spaces to the internet), which is shared between all Spaces. Additional outbound transfer is $0.01 per GiB. Outbound data transfer is free in the following cases:
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 and outbound data transfer is included in the price of the cluster.
DigitalOcean Load Balancers by themselves don’t generate bandwidth charges, they are bandwidth neutral.
However, the public outbound traffic that originates from your resources and passes through the load balancer counts towards your bandwidth limit. In this scenario, the aggregated bandwidth is reported as part of the load balancer and not attributed to the individual resources behind it.