| GTM Standard Edition | GTM Ultimate Edition | GTM 3.0 Standard Edition | GTM 3.0 Ultimate Edition |
Network-wide recovery time = Time required for identifying failures and performing failovers + Time required for the new configuration to take effect on the entire network | If the health check interval is set to 1 minute, the time to live (TTL) period is set to 60 seconds, and the number of consecutive failures is set to 2, GTM can identify a failure and perform a failover within about 3 minutes. Theoretically, the new configuration takes effect on the entire network within about 60 seconds. The actual period depends on the TTL periods that are specified by ISPs. | If the health check interval is set to 15 seconds, the TTL period is set to 1 second, and the number of consecutive failures is set to 2, GTM can identify a failure and perform a failover within about 1 minute. Theoretically, the new configuration takes effect on the entire network within about 1 second. The actual period depends on the TTL periods that are specified by ISPs. | If the health check interval is set to 1 minute, the TTL period is set to 60 seconds, and the number of consecutive failures is set to 2, GTM can identify a failure and perform a failover within about 3 minutes. Theoretically, the new configuration takes effect on the entire network within about 60 seconds. The actual period depends on the TTL periods that are specified by ISPs. | If the health check interval is set to 15 seconds, the TTL period is set to 1 second, and the number of consecutive failures is set to 2, GTM can identify a failure and perform a failover within about 1 minute. Theoretically, the new configuration takes effect on the entire network within about 1 second. The actual period depends on the TTL periods that are specified by ISPs. |
Load balancing policy type | Load balancing policy based on the geographical location | Load balancing policy based on the geographical location and load balancing policy based on latency | Closest to Source (load balancing policy based on the geographical location), Order, Poll, and Weight | Closest to Source (load balancing policy based on the geographical location), Order, Poll, and Weight |
Load balancing policy based on latency (supported address types) | Supported (IPv4 address) | Supported (IPv4 address) | Not supported | Not supported |
Address type | IPv4 address, IPv6 address, and domain name | IPv4 address, IPv6 address, and domain name | IPv4 address, IPv6 address, and domain name | IPv4 address, IPv6 address, and domain name |
Health check interval | 60 seconds | 15 or 60 seconds | 60 seconds | 15 or 60 seconds |
Policies for load balancing between address pools | Active/standby policy | Active/standby policy | Closest to Source, Order, Poll, and Weight | Closest to Source, Order, Poll, and Weight |
Policies for load balancing between addresses | Round robin and weight-based policy | Round-robin and weight-based policy | Load balancing between address pools and between application service IP addresses | Load balancing between address pools and between application service IP addresses |
Request line | ISP lines in the Chinese mainland, which include China Unicom, China Telecom, China Mobile, Dr. Peng Group, and Alibaba Cloud regional lines, regional lines in North China, South China, East China, Northeast China, Northwest China, Southwest China, and Central China, and continental lines outside the Chinese mainland Note Supported lines are also affected by the edition of the Alibaba Cloud DNS instance that is associated with the access domain name. | ISP lines in the Chinese mainland, which include China Unicom, China Telecom, China Mobile, Dr. Peng Group, CERNET, CBN, Alibaba Cloud regional lines, and ISP provincial and municipal lines, regional lines in North China, South China, East China, Northeast China, Northwest China, Southwest China, and Central China, and continental and national or regional lines outside the Chinese mainland Note Supported lines are also affected by the edition of the Alibaba Cloud DNS instance that is associated with the access domain name. | ISP lines in the Chinese mainland, which include China Unicom, China Telecom, China Mobile, Dr. Peng Group, CERNET, CBN, Alibaba Cloud regional lines, and ISP provincial and municipal lines, regional lines in North China, South China, East China, Northeast China, Northwest China, Southwest China, and Central China, and continental and national or regional lines outside the Chinese mainland Supported lines are also affected by the edition of the Alibaba Cloud DNS instance that is associated with the access domain name. | ISP lines in the Chinese mainland, which include China Unicom, China Telecom, China Mobile, Dr. Peng Group, CERNET, CBN, Alibaba Cloud regional lines, and ISP provincial and municipal lines, regional lines in North China, South China, East China, Northeast China, Northwest China, Southwest China, and Central China, and continental and national or regional lines outside the Chinese mainland Supported lines are also affected by the edition of the Alibaba Cloud DNS instance that is associated with the access domain name. |
Combination of regional lines and ISP lines | Not supported | Not supported | Supported | Supported |
Maximum number of address pools configured for an instance | 10 | 20 | 30 | 50 |
Maximum number of IP addresses and domain names in an address pool | 20 | 20 | 30 | 50 |
Minimum number of available addresses | 1 to 200 | 1 to 200 | The number of available addresses can be specified by proportion. | The number of available addresses can be specified by proportion. |
Minimum global TTL | 60 seconds Note The TTL value is also affected by the edition of the Alibaba Cloud DNS instance that is associated with the access domain name. | 1 second Note The TTL value is also affected by the edition of the Alibaba Cloud DNS instance that is associated with the access domain name. | You can specify a custom value. The custom value is not affected by the edition of the Alibaba Cloud DNS instance. | You can specify a custom value. The custom value is not affected by the edition of the Alibaba Cloud DNS instance. |
Maximum number of health check nodes | Unlimited | Unlimited | Unlimited | Unlimited |
Combination of different health check templates | Not supported | Not supported | Supported | Supported |
Number of health check tasks per month | 100 | 100 | 100 | 100 |
Number of SMS notifications per month | 1,000 | 2,000 | 1,000 | 2,000 |
Custom alert notification methods based on alert event types | Supported | Supported | Supported | Supported |
Elastic Compute Service (ECS)
Container Compute Service (ACS)
