DigitalOcean Bandwidth Overage: $0.01/GiB, Transfer Pools, and When It Bites

Short answer

DigitalOcean Droplet bandwidth is a four-layer model — not “unlimited,” and not a mystery bill if you read the published meter:

So: free inbound ≠ free outbound ≠ per-Droplet silo ≠ App Platform rates.

What DigitalOcean publishes today

Paraphrased from DigitalOcean’s Bandwidth Billing docs and Droplet pricing Transfer column (as-of 2026-11-06 Asia/Shanghai — DO’s Bandwidth Billing page showed Last verified 5 Nov 2026; re-check the live URLs if you are buying later):

Bandwidth Billing (Droplets)

• Each Droplet plan includes free outbound data transfer; additional outbound is $0.01 per GiB.
• Inbound transfer to Droplets is free.
• Transfer allowance and usage are pooled at the team level across Droplets.
• Accrued transfer does not roll over between months; it cannot be transferred between teams.
• Public-interface outbound counts against the pool; IPv6 uses the public interface; VPC private Droplet↔Droplet uses the private interface; DO does not bill outbound it determines was dropped by a DigitalOcean firewall rule.
• Allowance accrues per second a Droplet exists, up to a maximum of 2,419,200 seconds (28 days) per monthly billing cycle.
• The Billing page’s Droplet Transfer (Bandwidth) Overview shows usage and projections (projections assume the same daily averages continue); a Bandwidth Detail CSV (Beta) is available from that section.
• DO links a Droplet bandwidth calculator from Bandwidth Billing.
• No regional variations on bandwidth pricing (per DO’s Bandwidth Billing page).

Separate products (one line each — do not confuse)

• App Platform outbound overage: $0.02/GiB (its own included transfer and team app pool) — not the Droplet $0.01 rate.
• Spaces has its own outbound transfer bucket and rules — a separate product from Droplet transfer; see DO’s Bandwidth Billing Spaces section if you use object storage.

Droplet pricing (Transfer column)

The official Droplet pricing page owns the Transfer column for Basic and other families. Full dated price matrix and caveats live on the DigitalOcean provider page — this guide owns bandwidth semantics, not a reprint of every optimized SKU. CPU-Optimized, General Purpose, Memory-Optimized, and Storage-Optimized Droplets have their own Transfer columns on that same official pricing page (verify there; we do not invent those rows here).

Included transfer by Basic Droplet band

Basic Droplet Transfer amounts from DigitalOcean’s public pricing table this pass. For the full matrix (vCPU, SSD, $/hr, $/mo) see DigitalOcean provider and Droplet pricing.

These Transfer figures are the plan’s contribution toward the team outbound pool when the Droplet exists for the full accrual window — not a guarantee you will never see overage, and not a HostStack “safe monthly GiB” invention.

Team pooling + proration in plain words

DO’s model in ordinary language:

• Pool, don’t silo. Two Droplets on the same team share one outbound pool. A Droplet that uses more than it contributed can still be fine if siblings leave headroom.
• Earn while it exists. For every second a Droplet exists, it accrues 1 / 2,419,200 of its plan’s transfer allowance toward the team pool, up to the plan max (28-day / 2,419,200-second cap per monthly cycle).
• Short-lived earns less. A Droplet that only exists part of the cycle contributes a prorated slice of its Transfer column — not the full monthly GiB figure on the price table.
• Powered-off still exists. DO’s accrual wording is “for every second a Droplet exists.” A powered-off Droplet still exists as a Droplet object, so it still accrues allowance under that wording. HostStack does not invent a separate destroy-vs-power-off exception beyond DO’s published “exists” language — destroy ends existence; power-off does not.
• No rollover. Unused accrued transfer does not carry into the next month.
• No team-to-team transfer. Allowance cannot be moved between teams.

DO’s own example shape (paraphrase): two Droplets that each include 1,000 GiB and run a full cycle put 2,000 GiB into the team pool; if they use 1,500 + 100 = 1,600 GiB outbound, they stay inside the pool with no overage.

What counts against the pool

Counts (outbound via the public network interface):

• Public egress from a Droplet
• IPv6 traffic (uses the public interface)

Does not bill / does not count the way public egress does (per DO):

• Inbound to Droplets (free)
• Droplet↔Droplet over VPC private interface
• Outbound DO determines was dropped by a DigitalOcean firewall rule

Kubernetes worker nodes contribute the free outbound allowance of their Droplet plan, prorated by how long the node exists, into the same team pool as Droplets; overage beyond the team pool is still $0.01/GiB. Details live on DO’s Bandwidth Billing page.

When overage actually bites

High-level patterns where public egress can chew through a team pool faster than the sticker Transfer column suggests — not a how-to for abuse, relays, or evasion:

• Media / large-file origin without a CDN — browsers and apps pulling big assets straight from the Droplet public IP.
• Open relays or anything that turns your Droplet into someone else’s pipe — out of scope for HostStack advice; read DO’s Acceptable Use / ToS.
• Public scrape / download targets — third parties hammering a public URL you host.
• Many Droplets all egressing publicly — team pool helps, but stacked public egress still sums into one meter.

HostStack will not invent a “you won’t hit overage,” a safe monthly GiB average, horror-bill anecdotes, or regional bandwidth price diffs (DO states there are no regional variations on bandwidth pricing).

If your product needs multi-TB predictable egress every month, model the included Transfer column + $0.01/GiB with DO’s bandwidth calculator, or compare Contabo’s fair-use + port-cap framing on the twin guide.

Contabo fair-use vs DO metered framing

Neither model is universally “cheaper.” DO wins when you want a clear included-GiB pool and a published overage price. Contabo wins when fair-use + port are acceptable and you prefer no per-GB invoice line. Full matrix: DigitalOcean vs Hostinger vs Contabo. Deep Contabo semantics: Contabo unlimited bandwidth / fair-use.

How to check usage

1. Billing → Droplet Transfer (Bandwidth) Overview — team usage and projections (updated daily; projections assume the same daily averages continue).
2. Bandwidth Detail CSV (Beta) — request from that Billing section for Droplets / load balancers / Kubernetes detail.
3. Droplet bandwidth calculator — estimate before you launch (also linked from Bandwidth Billing).
4. Billing alerts — set spend / invoice alerts in the DO control panel so overage is not a surprise line item (verify the exact alert UI in your team Billing settings; HostStack does not invent alert thresholds).

FAQ

Is inbound free?
Yes. DigitalOcean’s Bandwidth Billing page states inbound transfer to Droplets is free.

Does a powered-off or short-lived Droplet still accrue allowance?
Allowance accrues for every second a Droplet exists, up to the 28-day (2,419,200-second) cap per monthly cycle. Short-lived Droplets therefore earn less than a full-cycle Transfer column. A powered-off Droplet still exists, so under DO’s wording it still accrues. Destroying the Droplet ends existence. HostStack does not invent further destroy-vs-power-off rules beyond that published language.

App Platform vs Droplet overage rate?
Droplet additional outbound: $0.01/GiB. App Platform additional outbound: $0.02/GiB. Separate products, separate pools — do not mix rates.

Is Spaces the same pool?
No. Spaces has its own outbound transfer bucket and rules. One-line separation only here; see DO Bandwidth Billing for Spaces detail.

Are there regional bandwidth price differences?
DO’s Bandwidth Billing page states there are no regional variations on bandwidth pricing.

Where do I see Droplet prices and Transfer?
DigitalOcean provider deep-dive · official Droplet pricing.

Sources

• https://docs.digitalocean.com/platform/billing/bandwidth/
• https://www.digitalocean.com/pricing/droplets
• https://www.digitalocean.com/community/tools/bandwidth
• https://help.contabo.com/en/support/solutions/articles/103000271195-are-there-any-bandwidth-or-traffic-limits-at-contabo- (twin framing only)
• HostStack: DigitalOcean · Contabo fair-use · Contabo · three-way compare · Methodology · Disclosure

Last re-fetch: 2026-11-06 Asia/Shanghai. Soft digest brand Dealwright is separate; no counseling-brand links.

Next steps

Droplet pricing (official) DigitalOcean provider deep-dive Compare matrix Contabo fair-use twin

Soft CTA · DO links are official only (no DO affiliate) · disclosure applies. Contabo CJ CTAs live on Contabo-facing pages when used.