Network Fee Adjustment for PolarDB for MySQL Global Database Network (GDN)
Dec 29, 2025
PolarDBAffected Time
To continuously enhance the stability and performance of the Global Database Network (GDN) feature in PolarDB for MySQL, we will optimize the underlying network architecture for certain cross-region data synchronization scenarios and begin charging network fees accordingly. Please find the details below:
Effective Date: April 1, 2026 (Singapore Time, GMT+8)
Affected Feature: PolarDB for MySQL – Global Database Network (GDN)
Scenarios Subject to Network Fees
- Scenario 1: Primary cluster in Chinese Mainland, secondary cluster outside Chinese Mainland
(e.g., Chinese Mainland → China (Hong Kong), Singapore, etc.)
- Scenario 2: Primary cluster outside Chinese Mainland, secondary cluster in Chinese Mainland
(e.g., Singapore → Chinese Mainland)
Scenarios Not Subject to Network Fees
- Scenario 1: Both primary and secondary clusters located within Chinese Mainland
(e.g., China (Chengdu) → China (Shenzhen))
- Scenario 2: Both primary and secondary clusters outside Chinese Mainland
(e.g., Singapore → Philippines (Manila))
Impact Summary
- Existing GDN Instances: If you already use GDN, any new secondary clusters added on or after the effective date that fall under the above fee-applicable scenarios will incur network charges based on actual traffic. Existing replication links will remain unaffected aand will not incur additional fees.
- New Purchases: For new GDN instances created on or after the effective date, pay-as-you-go network fees will apply if they meet the fee-applicable criteria. Please refer to upcoming official documentation for specific pricing standards.
We appreciate your continued understanding and support of Alibaba Cloud. We will consistently strive to provide you with an excellent cloud service experience.
If you have any questions or need assistance, please feel free to contact us by submitting a support ticket. Our team is ready to help!