Overview
To simplify user configuration, the new version elevates instance-level configurations to user-level configurations. IPAM pools and health checks are no longer attached to individual instances but are configured globally and can be referenced by all GTM domain instances. Additionally, health checks support template configurations with built-in system templates, allowing you to use them immediately.
Release content
Optimization type | Optimization content |
Configuration optimization |
|
Scheduling optimization |
|
Ultimate disaster recovery |
|
Operations optimization |
|
Version comparison
GTM Standard Edition | GTM Ultimate Edition | GTM 3.0 Standard Edition | GTM 3.0 Ultimate Edition | |
Network-wide failback time = fault switching time + network-wide effective time | With health check interval set to 1 minute, TTL to 60 seconds, and consecutive failure count to 2, GTM can accurately detect failures and switch in about 3 minutes. After fault switching, theoretically, it can take effect across the network in about 60 seconds, but the actual situation depends on the cache setting time of carriers across the country. | With health check interval set to 15 seconds, TTL to 1 second, and consecutive failure count to 2, GTM can accurately detect failures and switch in about 1 minute. After fault switching, theoretically, it can take effect across the network in about 1 second, but the actual situation depends on the cache setting time of carriers across the country. | With health check interval set to 1 minute, TTL to 60 seconds, and consecutive failure count to 2, GTM can accurately detect failures and switch in about 3 minutes. After fault switching, theoretically, it can take effect across the network in about 60 seconds, but the actual situation depends on the cache setting time of carriers across the country. | With health check interval set to 15 seconds, TTL to 1 second, and consecutive failure count to 2, GTM can accurately detect failures and switch in about 1 minute. After fault switching, theoretically, it can take effect across the network in about 1 second, but the actual situation depends on the cache setting time of carriers across the country. |
Access policy type | Geographic location-based access policy | Geographic location-based access policy, access latency-based access policy | Source proximity (geographic location-based access policy), sequential, polling, weighted | Source proximity (geographic location-based access policy), sequential, polling, weighted |
Access latency-based policy (supported address types) | Supported (IPv4) | Supported (IPv4) | N/A | N/A |
Address Type | IPv4, IPv6, domain name | IPv4, IPv6, domain name | IPv4, IPv6, domain name | IPv4, IPv6, domain name |
Health Check Interval | 60 seconds | 15 seconds, 60 seconds | 60 seconds | 15 seconds, 60 seconds |
Load balancing policy between IPAM pools | Only primary/secondary policy | Only primary/secondary policy | Supports source proximity, sequential, polling, weighted scheduling policies | Supports source proximity, sequential, polling, weighted scheduling policies |
Load balancing policy between addresses | Supports polling, weight ratio | Supports polling, weight ratio | Supports load balancing for application service IPs and IPAM pools | Supports load balancing for application service IPs and IPAM pools |
Request lines | Supports mainland China by carriers (China Unicom, China Telecom, China Mobile, Dr. Peng, Alibaba Cloud detailed to Region), by regions (North China, South China, East China, Northeast, Northwest, Southwest, Central China), and overseas by continent Note Also affected by the Cloud DNS instance version bound to the GTM access domain | Supports mainland China by carriers (China Unicom, China Telecom, China Mobile, Dr. Peng, education network, radio and television network, Alibaba Cloud detailed to Region) and carrier-specific regions (to provinces and municipalities), by regions (North China, South China, East China, Northeast, Northwest, Southwest, Central China), overseas detailed to continents, countries (regions) Note Also affected by the Cloud DNS instance version bound to the GTM access domain | Supports mainland China by carriers (China Unicom, China Telecom, China Mobile, Dr. Peng, education network, radio and television network, Alibaba Cloud detailed to Region) and carrier-specific regions (to provinces and municipalities), by regions (North China, South China, East China, Northeast, Northwest, Southwest, Central China), overseas detailed to continents, countries (regions). Not affected by Cloud DNS instance version | Supports mainland China by carriers (China Unicom, China Telecom, China Mobile, Dr. Peng, education network, radio and television network, Alibaba Cloud detailed to Region) and carrier-specific regions (to provinces and municipalities), by regions (North China, South China, East China, Northeast, Northwest, Southwest, Central China), overseas detailed to continents, countries (regions). Not affected by Cloud DNS instance version |
Region and carrier line combination configuration (carrier lines and region lines do not conflict) | Not supported | Not supported | Yes | Yes |
Number of IPAM pools that can be created per instance | 10 IPAM pools | 20 IPAM pools | 30 IPAM pools | 50 IPAM pools |
IP address limit in 1 IPAM pool | 20 IPs & domain names | 20 IPs & domain names | 30 IPs & domain names | 50 IPs & domain names |
Minimum available address limit | 1-200 | 1-200 | Supports setting by percentage | Supports setting by percentage |
Global TTL (minimum) | 60 seconds Note Also affected by the Cloud DNS instance version bound to the GTM access domain | 1 second Note Also affected by the Cloud DNS instance version bound to the GTM access domain | Supports customization, not affected by Cloud DNS instance version | Supports customization, not affected by Cloud DNS instance version |
Number of health check monitoring nodes | Unlimited | Unlimited | Unlimited | Unlimited |
Multiple detection template combination detection | Not supported | Not supported | Support | Support |
Health check tasks (per month) | 100 | 100 | 100 | 100 |
Text message alarm notification items | 1000 text message notifications (monthly package) | 2000 text message notifications (monthly package) | 1000 text message notifications (monthly package) | 2000 text message notifications (monthly package) |
Alarm notification methods can be customized according to alarm event type | Support | Yes | Support | Support |
How to upgrade from old GTM to GTM 3.0
If you want to use the new version, you can purchase it and configure it in the new version, then go to DNS settings to point your subdomain to the CNAME access domain provided by the new GTM. For more information, see How to smoothly upgrade from the old version of GTM to GTM 3.0?
Pricing
The purchase method and pricing of GTM 3.0 are completely consistent with the currently running Global Traffic Management instances. Version upgrades will not affect the cost of GTM instances in use. For specific pricing information, see Product Billing.