Details Thank you for your trust in Alibaba Cloud Backup Service. The ECS disaster recovery feature（EBS async replication） will end public preview and will be officially charged from 10:00 AM, August 19, 2025 (UTC+08). A new billing item is added, ECS disaster recovery（EBS async replication）. After it takes effect, all existing users and new users who use this function will be charged based on billing items. ECS will continue to charge fees for pay-as-you-go ECS instances and EBS disks created during ECS disaster recovery.For more details, see Pay-as-you-go. The cost of EBS async replication will continue to be charged by ECS. For more details, see Overview of disk disaster recovery. Billing Rules ECS disaster recovery（EBS async replication） is charged according to the number of disaster recovery instances and protection duration, for more details, see Cloud Backup price details and EBS async replication feature introduction.

Effected time July 25, 2025 02:00:00 - July 25, 2025 06:00:00 (UTC+08) Changes To improve service quality and system stability, the infrastructure and network team will perform network equipment upgrades on July 25, 2025 (UTC+08). The changes are Software maintenance/upgrade, cold patch. Effected scope Singapore Zone A/ B Description The upgrades will cause 2 brief network jitters/delays/packet losses, each lasting around 3 seconds. Do not perform business operations during this time. We apologize for any inconvenience.

Alibaba Cloud has updated the Service Level Agreement ("SLA") for Data Transmission Service (DTS), including modifications to the scope of exclusions. In accordance with the terms of our Service Level Agreement, we are notifying you that the changes will take effect on September 1, 2025 (Singapore Time) for existing Data Transmission Service (DTS) contracts in force beyond such date. For new purchases or renewals of the Data Transmission Service (DTS) resources on or after the date of this announcement, the revised Service Level Agreement will apply immediately. You may review the updated Service Level Agreement in the Product SLA Center > If you have any questions, please contact us via support tickets. Thank you for choosing Alibaba Cloud.

To enhance the reliability of the Data Disaster Recovery feature, we are planning to optimize corresponding functionalities. Please review the details below: Affected Scope: The Data Disaster Recovery feature in Data Management (DMS) - formerly Database Backup Service (DBS) Risk Overview: If you have a backup plan configured with "Single Backup" as the Full-scale Backup Frequency, the full backup relies on manual triggering. If incremental backup is later enabled, there is a risk of being unable to restore data to a specific point in time due to the lack of a valid full backup set. Mitigation Measures Product Adjustment: Starting from August 20, 2025, Singapore Time, we will prohibit enabling incremental backups for logical backup plans where the Full-scale Backup Frequency is set to "Single Backup". This adjustment applies to both existing and new backup plans that meet the criteria. Required User Action: To avoid the potential data recovery failures, you must modify the configuration of the affected backup plans before the product adjustment takes effect by changing the Full-scale Backup Frequency from "Single Backup" to "Periodic Backup". For example, you can configure full backups to occur weekly on Tuesdays and Fridays during off-peak hours (e.g., 3 AM). For detailed modification steps, please refer to the documentation. Important Reminder: According to the applicable Product Service Level Agreement (SLA), if you hold affected resources and fail to take the necessary actions as outlined in this notice, any resulting losses or risks will not be covered under the SLA. You will need to assume all relevant responsibilities and consequences. We sincerely appreciate your ongoing support and understanding as we strive to provide you with an exceptional cloud service experience. If you have any questions, please feel free to contact us via a support ticket.

Effected time July 23, 2025 02:00:00 - July 23, 2025 06:00:00 (UTC+08) Changes To improve service quality and system stability, the infrastructure and network team will perform network equipment upgrades on July 23, 2025 (UTC+08). The changes are Software maintenance/upgrade, cold patch. Effected scope Singapore Zone A/ B Description The upgrades will cause 2 brief network jitters/delays/packet losses, each lasting around 3 seconds. Do not perform business operations during this time. We apologize for any inconvenience.

Impacted Product Public authoritative DNS on international site (China site is not affected) Effective At July 25, 2025 (UTC +8) Content To enhance service stability, Alibaba Cloud DNS console is updated on July 25, 2025 (UTC+8). This update will not affect your services or DNS resolution. Upgrade: Non-Alibaba Cloud domains must be bound to a paid public authoritative DNS instance. DNS resolution for non-Alibaba Cloud domains that are not bound to a paid instance is still active but cannot be modified. The free edition has no resolution nodes outside the Chinese Mainland with no SLA commitment. We recommend using the paid edition. The paid edition has hundreds of nodes in 27 regions globally, accelerating global resolution and ensuring resolution stability.

Details Thank you for your support and attention to Alibaba Cloud OSS service. The OSS accelerator feature of OSS will officially start commercial charging from Aug 18, 2025. If you no longer need it, please delete it in time before charging, please refer to : Create, modify, and delete OSS accelerator Billing Rules You are charged based on the capacity of the OSS accelerator configuration that you request and the duration of use. For detailed information, please refer to: OSS Accelerator Fees.

Update content ApsaraMQ for RocketMQ in the corresponding region, including access methods over TCP, MQTT, and HTTP Upgrade Impact During the update, the following issues may occur: 1. Second-level transient connections may occur in the ApsaraMQ for RocketMQ console and each service node of the cluster. The transient connection duration is positively correlated with the scale of the cluster. In most cases, transient connections do not affect business because the automatic retry mechanism is triggered on clients. However, exception logs are generated and message delays may occur. 2. Messages may be duplicated. Make sure that message idempotence is performed on applications based on best practices. 3. During the update, do not manage resources such as creating or deleting topics in the ApsaraMQ for RocketMQ console. 4. If you access ApsaraMQ for RocketMQ over HTTP, transient connections may occur or connection requests may be rejected. The issue lasts for less than 1 minute. Make sure that the reconnection and retry mechanisms are configured on clients. You can also use the monitoring feature provided by ApsaraMQ for RocketMQ to monitor important business. To configure the monitoring feature, go to the ApsaraMQ for RocketMQ console and click Monitoring and Alerting in the left-side navigation pane of the Instance Details page. We apologize for the inconvenience. If you have questions, submit a ticket to contact ApsaraMQ for RocketMQ technical support.

Upgrade impact During the upgrade windows, access and connection to the RabbitMQ related services of the message queue may be interrupted or refused. Each interruption or refusion of access or connection is not expected to exceed 1 minute, please implement a reconnection and retry mechanism in the client portal. If you need to perform management operations on the console, please avoid the upgrade windows.

Effected time July 23, 2025 00:00:00 - July 23, 2025 06:00:00 (UTC+08) Changes To improve service quality and system stability, the infrastructure and network team will perform network equipment upgrades on July 23, 2025 (UTC+08). The changes are Software maintenance/upgrade, cold patch. Effected scope Singapore Zone A/ B Description The upgrades will cause 2 brief network jitters/delays/packet losses, each lasting around 3 seconds. Do not perform business operations during this time. We apologize for any inconvenience.