Bandwidth Billing
Last verified 17 Nov 2026
Details on bandwidth billing for DigitalOcean products are included on each product’s pricing page. The following sections summarize the same information for products that charge for bandwidth. There are no regional variations on bandwidth pricing.
Bandwidth billing is automated and you can view charges on your invoice. Now in beta, you can additionally request a CSV file that has the details of your team’s bandwidth usage across Droplets, load balancers, and Kubernetes clusters. To request this file, on the Billing page, in the Droplet Transfer (Bandwidth) Overview section, click Bandwidth Detail CSV (Beta).
Droplets
Each Droplet plan includes an amount of free outbound data transfer. Additional outbound transfer is billed at $0.01 per GiB. Inbound transfer to Droplets is free.
Transfer allowance and usage is pooled cumulatively across all Droplets at the team level, not individually per Droplet. Accrued transfer does not roll over between months and cannot be transferred between teams.
Any data transfer sent by a Droplet using a public network interface counts against the transfer pool for that Droplet’s team. All IPv6 traffic uses the public interface. Data transfer between Droplets over the VPC network uses a private network interface. We do not bill for outbound data transfer that we determine is dropped by a DigitalOcean firewall rule.
In the Droplet Transfer (Bandwidth) Overview section of the team billing page, you can view usage data and projections about your team’s transfer pool, updated daily. We base projections on the assumption that your team maintains the same daily averages for both quantity of active Droplets and bandwidth usage through the end of the billing cycle.
You can calculate bandwidth costs using our Droplet bandwidth calculator.
Details and Examples
We bill bundled-plan Droplets for each second they exist, rounded to the nearest minute, up to a maximum of 2,419,200 seconds (28 days) per monthly billing cycle. For every second a bundled-plan Droplet exists, it accrues 1/2,419,200 of its total transfer allowance towards the team’s transfer pool, up to the maximum included with its plan.
v5 Droplets also include a transfer allowance and accrue it at the same rate, 1/2,419,200 of the allowance per second. Because v5 Droplets do not have a monthly usage cap, they accrue allowance for every second they exist in the billing cycle instead of stopping at 28 days. In a month longer than 28 days, a v5 Droplet that runs the whole month accrues more than its plan’s monthly allowance. For example, a v5 Droplet with 1,000 GiB of transfer allowance that runs for all of a 31-day month (2,678,400 seconds) accrues 1,000 GiB x 2,678,400 / 2,419,200, or about 1,107 GiB.
For example, if a bundled-plan Droplet includes 1,000 GiB of transfer allowance, the Droplet accrues 1,000 GiB / 2,419,200 seconds, or about 0.0004 GiB of transfer allowance per second towards the team’s transfer pool. If the team runs two such Droplets for an entire billing cycle, those Droplets accrue 2,000 GiB of transfer allowance into the team’s transfer pool.
If the first Droplet uses 1,500 GiB of outbound data transfer (which is more than it contributed to the pool) and the second Droplet uses 100 GiB, they cumulatively used 1,600 GiB of the team’s 2,000 GiB transfer pool, so no overage fees apply.
App Platform
Each App Platform plan includes an amount of free outbound data transfer. Additional outbound transfer is billed at $0.02 per GiB. Inbound transfer to App Platform is free.
Transfer allowance and usage is pooled cumulatively across all apps at the team level, not individually per app or component. Accrued transfer does not roll over between months and cannot be transferred between teams.
You can view ingress bandwidth for individual apps, but you cannot currently view the accrued transfer allowance or cumulative usage for App Platform.
Details and Examples
We bill apps for each second they exist, up to a maximum of 2,419,200 seconds (28 days) per monthly billing cycle. For each second an app exists, it accrues 1/2,419,200 of its total transfer allowance towards the team’s transfer pool, up to the maximum included with its plan.
For example, if an app’s plan includes 500 GiB of transfer allowance, the app accrues 500 GiB / 2,419,200 seconds, or about 0.0002 GiB of transfer allowance per second towards the team’s transfer pool. If the team runs two such apps for an entire billing cycle, those apps accrue 1,000 GiB of transfer allowance into the team’s transfer pool.
If the first app uses 800 GiB of outbound data transfer (which is more than it contributed to the pool) and the second app uses 100 GiB, they cumulatively used 900 GiB of the team’s 1,000 GiB transfer pool, so no overage fees apply.
Spaces
Spaces subscriptions include 1,024 GiB of outbound data transfer (from Spaces buckets to the internet), which is shared between all buckets. Additional outbound transfer is $0.01 per GiB. 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, SFO2, and SFO3
- From Spaces in SFO3 to Droplets in SFO1, SFO2, and SFO3
- From Spaces in AMS3 to Droplets in AMS2 and AMS3
- From Spaces in FRA1 to Droplets in FRA1
- From Spaces in SYD1 to Droplets in SYD1
- From Spaces in BLR1 to Droplets in BLR1
- From Spaces in ATL1 to Droplets in ATL1
- From Spaces in LON1 to Droplets in LON1
- From Spaces in TOR1 to Droplets in TOR1
- From Spaces in RIC1 to Droplets in RIC1
- From Spaces in MKC1 to Droplets in MKC1
Private Spaces Traffic
Droplets that use the VPC-local DNS resolver can access Spaces buckets over DigitalOcean’s internal network instead of the public internet. When a Droplet resolves a Spaces URL through the VPC-local DNS resolver, the request is routed privately and does not count against your Spaces outbound transfer allowance.
Private Spaces traffic is available in all regions. In the following region groups, a Droplet can also access Spaces buckets in other datacenters within the same group over the internal network (for example, a Droplet in NYC1 accessing a bucket in NYC3):
- AMS (AMS2, AMS3)
- NYC (NYC1, NYC2, NYC3)
- SFO (SFO1, SFO2, SFO3)
Traffic between regions in different groups (for example, from a Droplet in NYC to a Spaces bucket in SFO) uses the public endpoint and is billed at the standard rate.
To use the private network route, your Droplet must be configured to use the VPC-local DNS resolver. Droplets that use external DNS resolvers (such as Google or Cloudflare) resolve Spaces URLs to the public endpoint, and standard bandwidth billing applies.
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.
Invoices include a breakdown of bandwidth usage and cost per Spaces bucket. If you have 100 or more Spaces buckets, you can only view this breakdown in the CSV version of the invoice. To view or download invoices, see our Invoices billing page.
Kubernetes Worker Nodes
Each worker node includes the free outbound data transfer allowance of its Droplet plan, prorated by how long the node runs. For example, a worker node whose plan includes 5,000 GiB of transfer per month accrues 5,000 GiB / (24 * 28) = 7.44 GiB of allowance for each hour it runs. Bundled-plan worker nodes stop accruing after 28 days (672 hours) in a month. v5 worker nodes accrue at the same hourly rate for every hour they run, so a v5 node that runs for all of a 31-day month accrues more than its plan’s monthly allowance. In an autoscaling node pool, each node accrues allowance only for the hours it exists, so the pool’s total allowance follows its node count.
Worker node allowances are pooled at the team level with the allowances of all the team’s Droplets. Outbound transfer beyond the team’s pool is billed at $0.01 per GiB, the same rate as Droplets. For details on how the team transfer pool works, see Droplet bandwidth billing.