This topic describes the billing rules of Global Traffic Manager (GTM) 3.0.
Billing rules
1. Billing method
GTM 3.0 instances are billed on a monthly or yearly subscription basis.
2. Billing cycle
The billing cycle of a GTM 3.0 instance is determined by the subscription duration of the instance. You can select the subscription duration of a GTM 3.0 instance when you purchase the instance. You can select 1 Month, 3 Months, 6 Months, 1 Year, 2 Years, or 3 Years.
3. Prices
3.1 Prices for GTM 3.0 instances of different editions
Edition | Price | Pricing |
Standard Edition | USD 20 per month | You are charged USD 20 for a GTM 3.0 instance of Standard Edition per month. |
Ultimate Edition | USD 140 per month | You are charged USD 140 for a GTM 3.0 instance of Ultimate Edition per month. |
3.2 Prices for health check tasks
If you enable the health check feature on the Internet, you must create a health check task. Specifically, you must select a health check node for each IP address. By default, 100 health check tasks are configured for a GTM 3.0 instance. You can increase the number of health check tasks when you purchase a GTM 3.0 instance. The health check tasks are only used for the GTM 3.0 instance you purchased. You cannot separately purchase or use health check tasks.
Edition | Unit price |
Standard Edition | You are charged USD 12 for every 100 health check tasks per month. |
Ultimate Edition | You are charged USD 48 for every 100 health check tasks per month. |
For example, when you create health check tasks for two addresses in an address pool, you select three Border Gateway Protocol (BGP) nodes: Zhangjiakou, Qingdao, and Hangzhou. In this case, the number of health check tasks is 6. Formula: Number of health check nodes × Number of IP addresses in the address pool = 6.
Expiration
GTM notifies you of instance expiration seven days, three days, and one day before the expiration date of your GTM 3.0 instance.
If you do not renew the instance before it expires, the instance is unavailable.
The GTM 3.0 instance is released and the data about the associated domain names is deleted seven days after the instance expires.
NoteThe configuration data of health check templates, addresses, and address pools is not deleted.