Droplet Bandwidth Billing Update Scheduled June 2018

Bandwidth Billing Policy as of June 1, 2018

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. If you have two Droplets with 1000 GB/month allowance each, you can transfer 1500 GB of outbound data with one Droplet and 100 GB with the other, and you will not accrue any overage.

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.

Below are answers to frequently asked questions about the differences between the previous system and the current system. To see charges for all DigitalOcean products with transfer limits, see Bandwidth Billing.

What Changed?

In June 2018, we made three major changes to bandwidth billing:

More flexible transfer limits

To reduce the chance that you exceed your free transfer limits, we pooled the transfer allowance at the account level instead of the Droplet level.

For example, say you have two $5 Droplets (1000GB/month allowance) that run all month. One Droplet transfers 1500GB of outbound data and the other transfers 100GB.

  • Under the old plan, you would pay for 500GB of overage.
  • Under the new plan, you wouldn’t be charged at all.

By pooling the data transfer allowance at the account level, we aim to give you the greatest flexibility in how you use it.

Reduced data transfer prices

Starting in 2013, each Droplet was billed at $.02/GB for data transfer beyond its included allowance. We halved the price of excess data transfer from $.02/GB to $.01/GB.

For example, the cost of 1000GB of overage would be $20 under the old plan and is $10 under the new plan.

Automated bandwidth billing

In the early days, we billed manually for excess transfer — and to be honest, it didn’t always happen. Now we can’t forget to bill for overage, but based on historical usage patterns, less than 1% of our users will exceed their pooled allowance.

Frequently Asked Questions

When will this pricing change go into effect?

Starting on June 1, 2018, outbound data transfer in excess of the pooled allowance will be tracked. Charges will appear on the July 1 invoice.

How will this change my costs?

Based on our analysis of the historical usage patterns of our customers, less than one percent of users will exceed their pooled allowance.

To help you understand how this change may affect you, we will collect usage data and display projections about your transfer pool starting on April 24 and throughout the month of May on your account’s Billing page.

The first bandwidth bill under the new pricing will appear on the invoice for July 1, based on usage during the month of June.

How does this affect Spaces data transfer?

Spaces has its own allowance separate from Droplets. Spaces transfer usage does not count towards Droplets transfer usage.

Is there a way to buy more allowance in bulk to avoid the $0.01/GB additional charges?

We do not offer prepaid services specific to data transfer. However, if you add credit to your account using PayPal, that balance will be automatically used toward data transfer charges as needed.

My account is part of the January 2013 grandfathering announcement. Are you changing this now?

No, all accounts grandfathered will continue to be treated as such.

Will prices change again in the future? How often do you expect to adjust the price per GB?

While we do not have immediate plans to adjust prices, we do plan to continue offering the most cost-effective data transfer in the industry.

I am a reseller and host several different clients within the same account. Is there a way to track bandwidth usage of individual Droplets separately so I can bill my customers accordingly?

We do not provide per-Droplet bandwidth usage metrics yet. In the meantime:

  • Businesses should consult their DigitalOcean account managers with questions or concerns.

  • DigitalOcean team accounts provide a dedicated invoice for the team’s resources and can be used to isolate client infrastructure. The data transfer pool for a team is based specifically on the Droplets in the team account and can be used to isolate clients.

  • Application and infrastructure monitoring services like New Relic and command line tools like vnStat can provide insight on a per-server basis.