Help Center/ Elastic IP/ FAQs/ Billing and Payments/ Why Am I Still Being Billed After My EIP Has Been Unbound or Released?
Updated on 2024-08-13 GMT+08:00
View PDF
Share

Why Am I Still Being Billed After My EIP Has Been Unbound or Released?

Symptom

After my EIP is unbound from an instance or is released, the EIP is still being billed.

Yearly/monthly EIPs are prepaid and you have already paid for the EIPs during the validity period. Unbinding an EIP or modifying its bandwidth does not affect the fees. This section describes the possible causes only for pay-per-use EIPs.

Possible Causes

Table 1 Possible causes that pay-per-use EIPs are billed

EIP Status

Billed By

Possible Cause

EIP is unbound from an instance.

Pay-per-use EIP billed by traffic
  • EIP reservation price: If a pay-per-use EIP is unbound from an instance, the reservation price will be billed.

    If your EIP is no longer required, release it to stop the billing.

  • Traffic: will not be billed.

Pay-per-use EIP billed by bandwidth

Pay-per-use EIP added to a shared bandwidth
  • EIP reservation price: If a pay-per-use EIP is unbound from an instance, the reservation price will be billed.

    If your EIP is no longer required, release it to stop the billing.

  • Shared bandwidth: will continue to be billed.

    A shared bandwidth and an EIP are billed separately. Unbinding and releasing an EIP will not affect the billing of the shared bandwidth. If you do not need the shared bandwidth anymore, delete it.

EIP is released.
  • Pay-per-use EIP billed by traffic
  • Pay-per-use EIP billed by bandwidth

The EIP, traffic, and bandwidth will stop being billed. If you find that you are still being billed, check whether your account has a shared bandwidth.

Pay-per-use EIP added to a shared bandwidth

A shared bandwidth and an EIP are billed separately. Unbinding and releasing an EIP will not affect the billing of the shared bandwidth. If you do not need the shared bandwidth anymore, delete it.
Parent topic: Billing and Payments