Expenses and Costs:Understanding unexpected costs

Possible causes: Active pay-as-you-go resources exist in your account — possibly in an infrequently used region or created by another user with account access.

Troubleshooting steps

Troubleshoot by viewing active resources from the console homepage:

• Check active resources: Log in to the Alibaba Cloud console. On the Overview page, check cloud resources in all regions. Pay close attention to regions you do not frequently use and check for active pay-as-you-go resources.

  

Troubleshoot by viewing your billing data:

Old console

• Review your bill summary: Go to Billing Center > Overview of Monthly Bill, select a Billing Cycle at the top, and review the summary of your spending. You can also view the spending distribution by product at the bottom.

  

• Analyze billing details: Go to Bill Details and filter by item or billing cycle. When reviewing the details, focus on fields such as Bill Type, Product, Product Details, Region, Instance ID, Billable Item, and Discounted Amount.

  

New console

• Review your bill: Go to Expenses and Costs > Overview of Monthly Bill, select a Billing Cycle, and analyze your overall spending By Product.

• Analyze billing details: Go to Bill Details and filter by a statistical dimension or billing cycle. When reviewing the details, focus on fields such as Billing Method, Product Name, Offering Name, Instance ID, Region, Billable Item, and Amount Payable.

  

Possible causes: Your subscription resource has associated pay-as-you-go components. Common scenarios:

• Your subscription ECS instance has a traffic-billed public IP address, incurring hourly charges per public bandwidth billing rates.

• Your subscription ECS instance has a pay-as-you-go cloud disk attached, billed per block storage billing rates.

• You created a snapshot for your ECS instance. Snapshots default to pay-as-you-go billing method per snapshot billing.

• RDS instances have data backup enabled by default (cannot be disabled). Backups within the free backup size quota are free; excess usage is billed per Backup fees.

Troubleshooting steps

Old console

Identify the source of charges: On the Bill Details page, set the view to group by Billable Item and set the cycle to Day or Details. Filter the Billing Method field by pay-as-you-go bill to analyze the specific billable items. Manage associated resources: Periodically check for and release associated resources that you no longer need. For example, delete unneeded snapshots and check if an automatic snapshot policy is active. Delete the automatic snapshot policy to prevent further charges.

New console

Identify the source of charges: On the Bill Details page, set the view to group by Billable Item, set the cycle to Day or Details, and filter the Billing Method field by pay-as-you-go bill to analyze the specific billable items. Manage associated resources: Periodically check for and release associated resources that you no longer need. For example, delete unneeded snapshots and check if an automatic snapshot policy is active. Delete the automatic snapshot policy to prevent further charges.

Possible causes: Shutting down or stopping a resource does not always stop billing. If charges persist after deleting a resource instance, common reasons include:

• Associated resources were not released

  • The main instance (such as an ECS instance) was released, but associated pay-as-you-go resources like Elastic IP Address (EIP) or snapshots were not. These continue to incur charges.

  • If you deleted an RDS MySQL instance but configured a policy to retain backups after release, these backup files are retained. According to the feature's rules, backup storage is free for seven days after the instance is released. After seven days, you are billed for the storage.

• Billing delay

  • Bills for pay-as-you-go resources are generated on a cyclical basis (for example, hourly). After you release a resource, you will still be billed for the final usage cycle. For example, if you release a resource at 10:08, the bill for the 10:00-11:00 hour will be generated after 11:00.

Troubleshooting steps

1. Analyze the source of charges: Go to the Bill Details page. Set the view to group by Billable Item and set the cycle to Details to find the cloud resource that is incurring charges.

2. Check the usage time: On the Bill Details page, review the usage time to confirm if it falls within the billing cycle of the released resource.

3. Check associated resources: When you release an instance, make sure to also release its associated pay-as-you-go resources, such as by deleting snapshots, releasing cloud disks, or releasing pay-as-you-go EIP instances.

Possible causes: Free trial products use a postpaid model. A notification is sent before the trial expires to prevent service interruptions. When the trial ends, the instance is not automatically released — it converts to pay-as-you-go billing method. Additionally, usage exceeding free quota limits is billed at standard rates.

Possible causes

• The resource plan you purchased does not cover the billable item that is incurring charges. For example, an Object Storage Service (OSS) resource plan for Standard - Zone-Redundant Storage cannot offset charges for outbound traffic.

• The resource plan does not apply to the region where you are using the product.

• The resource plan has expired or its quota has been exhausted.

Troubleshooting steps

1. Check the resource plan status: Log in to the Billing & Costs console > Account > Resource Plan. Check the Status and Applicable Region to confirm that the resource plan is still valid and has a remaining balance.

2. Confirm the coverage: Review the billing documentation for the cloud product to confirm the resource plan's coverage. Then, use the Bill Details page to verify whether the specific billable item should have been covered.

Possible causes: Sudden cost increases typically result from traffic spikes, auto-renewal of a resource, or resources purchased by another account user.

• A sharp increase in traffic or data usage raises costs for usage-billed resources. Examples include outbound traffic from ECS, outbound traffic from Object Storage Service (OSS) (public internet downloads), and Content Delivery Network (CDN) outbound traffic in Chinese mainland.

• If auto-renewal is enabled for a subscription product, the system automatically renews the instance before expiration.

Troubleshooting steps

Old console

Analyze detailed bills and usage: Use the Bill Details page to identify the time, specific resource name, and billable item associated with the cost increase. Then, review the Usage Details to compare resource usage between the high-cost period and a normal period.
Analyze auto-renewals: Go to the Renewal Management page. On the auto-renewal tab, check for any unexpected auto-renewal settings. In Bill Details, check for transactions with a Transaction Type of Renewal.

New console

Analyze detailed bills and usage: Use the Bill Details page to identify the time, specific resource name, and billable item associated with the cost increase. Then, review the Usage Details to compare resource usage between the high-cost period and a normal period.
Analyze auto-renewals: Go to the Renewal Management page. On the auto-renewal tab, check for any unexpected auto-renewal settings. In Bill Details, check for transactions with a Transaction Type of Renewal.

Explanation: Alibaba Cloud calculates prices to 10 decimal places. During settlement, amounts are aggregated and rounded to two decimal places. The fractional difference is recorded as a "rounding adjustment" and appears only on the last day of each month's bill.