Why is my Linode bill higher than expected?

Powered-off Linodes still charge your card

The most common reason for an unexpected Linode bill is leaving a powered-off instance running on your account.

Charges accrue for any service present on an Akamai Cloud account even if it is powered off or unused. Akamai still maintains your disk data, and underlying resources like RAM and network capacity stay reserved for you in the hypervisor. If you shut down a VM through the OS or Cloud Manager, you are still paying its full hourly rate up to its monthly cap.

The same rule applies to other attached resources. Active services such as Longview Pro, Block Storage, or an additional IPv4 address continue to bill until you remove them from your account entirely. As we noted when looking at why a powered-off Droplet still bills on DigitalOcean and how stopped instances work on Vultr, cloud providers rent capacity, not compute state. If you do not intend to use the instance again, you must delete it.

How Akamai Cloud calculates hourly rates, caps, and mid-month invoices

Akamai Cloud uses a hybrid billing model. Services accrue charges at an hourly rate up to a monthly cap, and usage is always rounded up to the nearest hour.

A standard invoice is automatically generated on the first day of each month for the previous month's usage, and your default payment method is charged automatically. But you might also see charges land before the month ends. Akamai generates a mid-month bill if your account reaches a specific spending threshold within a single month, which is initially $50.00 for many users. If you have a history of on-time payments, Akamai may increase that threshold over time.

Akamai accepts Visa, Mastercard, American Express, and Discover, and you can add credit using PayPal transfers. But maintaining a valid credit card on file is required by the Master Services Agreement. If you signed up with a promotional credit, your credit card gets charged only after you exhaust the promotional credit amount or after the credit window expires.

Keep these mechanics in mind when managing your instances:

• Hourly caps: For services with a monthly rate, you are never billed more than the monthly rate for that service, excluding network transfer overages. A 1 GB VM at $0.0075/hr deleted after 24 hours of use is billed $0.18.
• Uncapped plans: Starting July 1, 2026, G8 dedicated Linodes, GPU Linodes, and additional IPv4 addresses are billed for actual hours used each month without a monthly price cap.
• Resizing traps: When you resize a service, you create a new billable service that appears as a separate line item on your monthly invoice. If you resize a Linode to a larger plan and then return it to the original plan in the same billing cycle, you are billed for three separate services. The combined hourly rate for these three items can easily exceed the original plan's monthly cap.
• Daylight saving time: Services without a monthly cap that run for an entire month log 721 hours in November (which adds an hour) and 743 hours in March (which subtracts an hour).
• Binary conversion: Object Storage, Block Storage, and compute network transfer use base-2 conversion, where 1 GB is 2^30 bytes (1 GiB) and 1 TB is 2^40 bytes (1024 GBs).

Network transfer pools and overage charges

Network transfer overage is the second major source of billing surprises. Akamai pools transfer across your instances, but the rules depend heavily on plan types, regions, and traffic direction.

Older Linode plans include an outbound network transfer allotment that scales from 0 to 20 TB per month based on the plan family and size. Most core data centers pool this allowance into a global network transfer pool. If an individual Linode uses more outbound bandwidth than its plan includes, you are not charged overages as long as the total outbound transfer across all your services stays within your global or region-specific pool.

However, several newer setups do not share in this pool:

• Plans without transfer: Transfer is not included in NVIDIA RTX PRO 6000 Blackwell Server Edition GPU plans, NVIDIA RTX 4000 GPU plans, NVIDIA Quadro RTX 6000 plans, Accelerated plans, G8 Dedicated CPU plans, or Linodes in distributed compute regions. For these, all outbound transfer is billed.
• Region-specific pools: Some newer data centers track usage in a separate region-specific pool rather than the global pool. In distributed compute regions, network transfer is not pooled at all. In some newer data centers, services and transfer may be billed at separate rates due to higher regional infrastructure costs.
• NodeBalancers: NodeBalancers consume network transfer, but they do not add any transfer allowance to your pool.
• Object Storage: Object Storage consumes transfer and adds 1 TB per month to your global network transfer pool, but it adds zero allowance to region-specific pools like Jakarta and São Paulo. Outbound transfer from Object Storage over public IPv4 and public IPv6 is metered, even when sent to other services in the exact same data center.
• Proration: If a Linode is not active for the entire month, its transfer allowance is prorated based on the hours it was active.

All inbound network transfer is free and unmetered across all plans. Outbound transfer to other services in the same data center is also free and unmetered, provided it routes over an IPv6 address, a private VLAN, or a private IPv4 address. But outbound traffic to a public IPv4 address in the same data center is metered. Private network traffic over VLANs or within a Virtual Private Cloud (VPC) never counts against your transfer allowance. Managed Databases do not consume network transfer or add to the allowance for customers using IPv6.

Any transfer that exceeds your monthly allotment is billed based on the service region and is charged at the end of the billing period.

Tracking transfer and checking your uninvoiced balance

Akamai Cloud sends automated email notifications to your account email when your account hits 80%, 90%, and 100% of your transfer pool size. You can also monitor your usage directly before the invoice arrives.

In Cloud Manager, click Monthly Network Transfer Pool underneath the list of Linodes, NodeBalancers, or Object Storage Buckets. This opens a modal showing your active pools, transfer used, pool sizes, and the date usage resets. To check an individual server, click Linodes in the left navigation menu, pick the instance, and open the Network tab.

If you use the command line, check your current month's transfer utilization in GB with the Linode CLI:

linode-cli account transfer

To see accrued hourly charges, open Cloud Manager and go to the Billing page under Administration. Keep in mind that Linode's uninvoiced balance view tracks the accrued hourly run rate for instances and storage, but it excludes network transfer overages. Overages are calculated and added only when the final invoice is generated.

How to stop further billing on Akamai Cloud

Pausing, powering off, or shutting down an instance will not stop charges from accruing. To stop further billing, you must remove paid services from your account or cancel your account completely.

To delete a Linode in Cloud Manager:

1. Select Linodes from the sidebar menu.
2. Locate the Linode you want to remove.
3. Click its ... menu and select Delete.
4. Click Delete Linode in the confirmation box.

Removing a service makes its data irretrievable. When you delete a Linode, any attached Backup service is also deleted, meaning you cannot restore from earlier backup snapshots. However, if the Linode was active for at least 24 hours before deletion, Akamai automatically generates a Recovery image.

If you choose to cancel your Akamai Cloud account entirely, you may receive a final bill for all charges that accrued during the current billing period before cancellation. Users who cancel their account within the first 7 days can receive a full refund. Beyond that window, refunds are only considered for payments made within the last 180 days and come with a $5 processing fee deducted from the payout.

Automated spend monitoring with Costbrake

If you want an external safeguard against runaway cloud costs, Costbrake watches your spend across platforms like Linode, AWS, Azure, Google Cloud, Cloudflare, and Vercel.

Costbrake connects to Akamai Cloud using a read-only personal access token with Account: Read Only permissions and No Access for everything else. It checks your uninvoiced balance and flags unexpected changes early. On the Free plan ($0 for 2 provider connections and 3 budgets), Costbrake runs checks hourly. On Pro ($12/month) and Team ($39/month), checks run every 5 minutes.

You get alerts when an hour costs more than 3x the 7-day baseline and at least $5 over normal, along with budget warnings at 50%, 80%, and 100%. A forecast alert tells you if your pace over the last 72 hours will push month-to-date spend past your budget before month-end, and a new-charge alert fires whenever a service first appears above $1. Alerts route to email on all plans, Slack, Discord, and webhooks on Pro, and PagerDuty on Team.

Because powered-off Linodes continue billing, Costbrake does not offer brakes for Akamai Cloud. For other supported providers, Costbrake includes opt-in, admin-confirmed brakes that can pause or cap workloads without deleting data. To see how other platforms handle budget ceilings, read our guide on which cloud and AI providers let you set a hard spending cap. You can review Costbrake pricing or run an agent setup by giving your AI coding agent the setup URL.