Why Are There Still Fees Deducted After My Resource Has Already Been Deleted?

Possible Causes

If there are still fees generated from a deleted resource, the possible causes are as follows:

• Associated resources not released
  • You may have released only the primary instance (such as an ECS). The associated pay-per-use resources are not released and will continue to be billed.
  • For example, you deleted an RDS for MySQL DB instance, and still have a manual backup that continues to be billed. To avoid incurring extra fees, delete the manual backup together with the DB instance.

• Bill delay
  • For pay-per-use resources, you use them first, and are then charged based on usage at a fixed interval. Fees are deducted with a certain delay. If you disable a resource, there may still be fees deducted for previous usage, but you will no longer be billed for the resource.
  • For example, if an ECS (settled by hour) is deleted at 08:30, the fees generated from 08:00 to 09:00 are usually deducted at about 10:00.

Troubleshooting

• Analyze fee deduction sources: Log in to the Billing Center and choose Billing > Bill Details. Check the cloud resource of each amount.
• Check expenditure time: On the Bill Details page, check whether the Expenditure Time of the released pay-per-use resource is within its billing period.
• Check associated resources: When releasing the instance, check and release its associated pay-per-use resources, such as ECSs and EIPs. For details, see How Can I Stop an ECS from Being Billed? and Releasing or Unsubscribing from an EIP.