Alibaba Cloud Notice

[Upgrade] Notice of Upgrade of Network Equipment located in Alibaba Cloud São Paulo Node

Wed, 26 Aug 2026 10:14:31 GMT

Affected Time

2026-08-27 12:00:00 ~ 2026-08-27 18:00:00 (UTC+08)

Upgrade content:

upgrade of network equipment located in Alibaba Cloud São Paulo node.

Upgrade impact:

Users accessing Alibaba Cloud node in São Paulo through Telefonica(AS12956) might be impacted. Under normal circumstances, the users have no perception on the impact. In abnormal cases, route convergence may cause two minute-level jitters. The jitter basically has no effect on the long-connection service with automatic reconnection function. Please ensure that you implement the reconnection and retry mechanism in your services to enhance the fault tolerance of your services.

We apologize for the inconvenience caused to you. If you have any questions, please contact us for consultation and feedback.

Announcement on Amendments to the Service Level Agreement (SLA) for Model Inference Service of Aliba

Wed, 26 Aug 2026 10:14:08 GMT

Affected Time

2026-09-28 00:00:00 (UTC+08) [Subject to the actual change time]

Changes

To measure service availability more objectively and improve the service experience, we will update the Service Level Agreement (SLA) for the Model Inference Service of Alibaba Cloud Model Studio. This amendment mainly covers the following two items:

Deduplication of 5XX Failed Requests

When calculating the error rate per 5-minute interval, Model Studio determines whether 5XX failed requests are identical by computing a hash value based on the request parameters. Within one Time Interval, multiple failed requests with the same hash value submitted by the same Alibaba Cloud account to the same model shall be counted as one single failed request. If any one of these requests succeeds, none shall be counted as a failed request.

SLA Not Applicable to Deprecated Models

Service errors arising from models that have been officially deprecated by the platform shall not be counted in the SLA error rate. Deprecated models are no longer subject to the service availability commitment under this Agreement.

The above amendments shall take effect on September 28, 2026. Your continued use of the Model Inference Service of Model Studio after the effective date shall be deemed as your acceptance of the amended Agreement. You may review the full terms on the agreement page: Alibaba Cloud Model Studio - Model Inference Service Level Agreement.

Thank you for your support of Alibaba Cloud Model Studio.

Announcement on Commercial Billing for the Cloud Sandbox Snapshot Feature

Tue, 25 Aug 2026 07:10:29 GMT

Affected Time

2026-09-07 00:00:00 (UTC+08) 后

Change content

Effective from 00:00 Beijing Time on September 7, 2026 (UTC+8), the Cloud Sandbox Snapshot feature will begin commercial billing.

Feature Overview

The Snapshot feature supports full-state snapshots (including memory and disk) of running sandboxes. Based on these snapshots, you can restore a sandbox within seconds or clone multiple new sandboxes. This is suitable for scenarios such as resuming long-running agent tasks from breakpoints, achieving cold starts within seconds through environment pre-warming, and parallel cloning for exploration.

Pricing

Snapshot Storage Usage = Memory Specification * 2 + Disk Specification

Cost = Snapshot Storage Usage * Disk Unit Price * Duration

Disk Unit Prices:

- Mainland China regions: USD 0.00031896 per GiB per hour

- Regions outside Mainland China: USD 0.00025308 per GiB per hour

Change impact

Snapshots created before the introduction of commercial billing will officially incur charges starting from 00:00 on September 7. Please delete or retain them as needed.

[Product Discontinuation] Selected DMS Disaster Recovery Backup Capabilities

Tue, 25 Aug 2026 05:58:31 GMT

Affected Time

2027-03-01 00:00:00 (UTC+08)

Change Details

Dear Alibaba Cloud Customer,

Thank you for using Alibaba Cloud. Due to product capability adjustments, DMS Disaster Recovery will discontinue the following backup capabilities at 00:00 on March 1, 2027 (Beijing Time):

Oracle logical backup and the related restore and download capabilities;
MariaDB logical backup and the related restore and download capabilities;
PolarDB for PostgreSQL (PPAS) logical backup and the related restore and download capabilities;
Redis logical backup and the related restore and download capabilities;
PolarDB-X (formerly DRDS) logical backup and the related restore and download capabilities;
MongoDB incremental backup, point-in-time recovery, and incremental backup data download capabilities.

Impact

For Oracle, MariaDB, PolarDB for PostgreSQL (PPAS), Redis, and PolarDB-X (formerly DRDS), the related console entry points, OpenAPIs, and service endpoints will no longer be available after the discontinuation date. New purchases, renewals, backup operations, restores, and downloads will stop at the same time.

Historical backup data created before the discontinuation date will no longer be available for restore or download through the original logical backup workflow.

The database products themselves are not affected. Oracle physical backup and restore capabilities will remain available.

For MongoDB, this change applies only to the incremental backup workflow. After the discontinuation date, incremental backup, point-in-time recovery, and incremental backup data downloads will no longer be available. Full backups and restores from full backup sets are not affected.

Recommended Actions

Oracle users are advised to switch to DMS Disaster Recovery physical backup for Oracle and verify both backup and restore operations before the discontinuation date. If physical backup does not meet your requirements, restore the logical backups that you need to retain to a new instance, or download them to local or self-managed storage.

No direct replacement is available for the affected MariaDB, PolarDB for PostgreSQL (PPAS), Redis, or PolarDB-X logical backup capabilities. Restore the backups that you need to retain to a new instance, or download them to local or self-managed storage before the discontinuation date. Complete a restore test to verify that the retained data is usable.

There is no replacement or migration path for the MongoDB incremental backup workflow. Assess the impact of losing point-in-time recovery on your recovery objectives, update your backup and recovery plan, and download any incremental backup data that must be retained.

If you have any questions, submit a ticket to Alibaba Cloud or contact your account manager.

[Product Discontinuation] DMS Disaster Recovery Legacy Console and Features

Tue, 25 Aug 2026 05:58:28 GMT

Affected Time

2027-03-01 00:00:00 (UTC+08)

Change Details

Dear Alibaba Cloud Customer,

Thank you for using Alibaba Cloud. As part of a product architecture upgrade, DMS Disaster Recovery will discontinue its legacy console and the following legacy features at 00:00 on March 1, 2027 (Beijing Time):

Storage pools;
Backup policies;
Backup data transfer;
Logical groups;
Batch backup;
Snapshot list;
AWS data source backup;
Migration tasks;
Restore drills.

After the discontinuation date, the related console entry points, OpenAPIs, service endpoints, and existing feature workflows will no longer be available. Features that involve separate purchases or subscriptions will also stop accepting new purchases and renewals.

Impact

The legacy console will stop providing services. Its domains and entry points will redirect to the new DMS Disaster Recovery console. Existing backup plans can continue to be managed in the new console, but the legacy features listed in this notice will not be carried over.

The following changes will apply:

Storage pools will no longer support queries, configuration changes, or API operations. Creation of new storage pools is already unavailable.
Backup policies will no longer support creation, editing, cloning, queries, or association with backup plans.
Backup data transfer, including secondary storage pools, transfer policies, and scheduled or event-triggered transfers, will stop.
Logical groups will no longer support creation, editing, deletion, or data source management.
Batch backup will no longer support selecting multiple data sources and creating backup plans in one operation.
The snapshot list page and its standalone query workflow in the legacy console will be removed. Existing sandbox functionality for RDS backup plans is not affected.
Full and incremental backup pages and related queries for AWS data sources will no longer be available.
Migration tasks will no longer support purchase, configuration, start, pause, resume, completion, or management operations.
Existing restore drill plans will stop running. The restore drill task list and historical report access will also be removed.

Recommended Actions

Use the new DMS Disaster Recovery console to manage your backup plans, and update any bookmarks or links that point to the legacy console.

Complete the following actions before the discontinuation date:

Download or export any storage pool, backup data transfer, or AWS data source backup data that must be retained.
Configure backup plans separately for each data source if you currently use batch backup.
Complete any active migration tasks, or confirm their termination, data retention, and resource release arrangements.
Disable existing restore drill plans and save any reports that must be retained. Use manual restore tests if recovery verification is still required.
Review dependencies on backup policies and logical groups. No equivalent replacement is currently available for these features.

If you have any questions, submit a ticket to Alibaba Cloud or contact your account manager.

Security Center Agentic CSPM: Free-Tier Periodic Scanning Switch Adjustment Notice

Mon, 24 Aug 2026 09:12:51 GMT

Affected Time

2026-08-31 18:00:00 (UTC+08)

Changes

Starting from August 31, 2026, we will gradually adjust the periodic scanning switch for free-tier users of Alibaba Cloud Security Center Agentic Cloud Security Posture Management.

Free Detection Capabilities Remain Unchanged: This adjustment only affects the status of the periodic scanning switch. The check items, detection scope, and other capabilities available to free-tier users remain unchanged. You can continue to use the full range of free configuration risk detection services.

Periodic Scanning Switch Adjustment: If you currently have periodic scanning enabled and have not made any policy changes since setting it up, the system will automatically turn it off after the adjustment. You can log in to the console to re-enable it at any time — the steps remain the same.

Impact

Free tier users:

If you currently have periodic scanning enabled and wish to continue using it, please log in to the Security Center console after the adjustment and re-enable the periodic scanning switch in the detection settings of Cloud Security Posture Management. Once re-enabled, the system will resume automatic scanning on a periodic basis. If you do not require automatic periodic scanning, you can manually trigger scans at any time through the console. Scan results and reports will remain the same as before.

Paid users:

No action is required. Your services will not be affected.

【Product Change】Offline announcement for CloudMonitor 1.0 Kubernetes Container Monitoring

Mon, 24 Aug 2026 08:42:34 GMT

Affected time

2026-09-28 Offline

Change and impact

To continuously improve the Kubernetes container monitoring experience, the Kubernetes container monitoring capability of CloudMonitor 1.0 has been progressively consolidated into Managed Service for Prometheus. The console access entry for the original feature has now been closed. For details, please refer to the Announcement on the discontinuation of the Kubernetes container monitoring feature of CloudMonitor.

CloudMonitor 1.0 will discontinue the Kubernetes container monitoring backend service starting from 10:00 (UTC+8) on September 28, 2026. After the service is discontinued, you will no longer be able to use the Kubernetes container monitoring feature of CloudMonitor 1.0.

If your account currently still has Kubernetes container monitoring data being reported. Please confirm as soon as possible whether any of your business services still depend on this feature. If it is still in use, we recommend switching to the container monitoring service provided by Managed Service for Prometheus to avoid monitoring interruptions.

Action required

Managed Service for Prometheus can support your existing container monitoring scenarios and provides richer monitoring metrics and built-in dashboards. For specific operations, please refer to Configure Managed Service for Prometheus.

If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

AliwareMQ for MQTT upgrade notice in Sep 2026

Mon, 24 Aug 2026 07:36:35 GMT

Affected Time

2026-09-01 22:00:00 ~ 2026-09-02 07:00:00 (UTC+08) [Hangzhou, Shanghai, Shenzhen, Beijing, Public, Zhangjiakou, Chengdu, Qingdao, Hohhot,Guangzhou,Wulanchabu,Heyuan]

2026-09-03 22:00:00 ~ 2026-09-04 02:00:00 (UTC+08) [Singapore, Hong Kong, Tokyo, Sydney, Kuala Lumpur, Jakarta, Manila]

2026-09-08 22:00:00 ~ 2026-09-09 07:00:00 (UTC+08) [Hangzhou, Shanghai, Shenzhen, Beijing, Public]

2026-09-10 08:00:00 ~ 2026-09-10 12:00:00 (UTC+08) [Dubai, Riyadh, Frankfurt, London]

2026-09-15 22:00:00 ~ 2026-09-16 07:00:00 (UTC+08) [Dubai, Riyadh, Frankfurt, London]

2026-09-17 14:00:00 ~ 2026-09-17 18:00:00 (UTC+08) [Silicon Valley, Virginia]

2026-09-22 22:00:00 ~ 2026-09-23 07:00:00 (UTC+08) [Hangzhou, Shanghai, Shenzhen, Beijing, Public]

2026-09-24 22:00:00 ~ 2026-09-25 07:00:00 (UTC+08) [Zhangjiakou, Chengdu, Qingdao, Hohhot,Guangzhou,Wulanchabu,Heyuan]

During the upgrade, the MQTT console and each service node in the cluster may experience a second-level flash (the flash time is positively related to the cluster scale). The client application needs to set automatic reconnection to avoid affecting the business. During the upgrade period, there may be a small number of failures in message sending, and the application should implement a retry mechanism for disconnection failures; at the same time, there may be message delays. For administrative operations on the console, please avoid maintenance windows. Sorry for the inconvenience caused to you, if you have any questions, please feel free to contact us through the ticket.

Coupon Eligibility Update for Cloud Marketplace Curated Second-Party Products

Mon, 24 Aug 2026 07:06:12 GMT

变更内容

Starting 00:00 CST on August 28, 2026, general-purpose coupons will no longer apply to any products in the Cloud Marketplace Curated Second-Party category.

变更影响

Starting 00:00 CST on August 28, 2026, general-purpose coupons will no longer apply to any products in the Cloud Marketplace Curated Second-Party category — including the currently listed products below and all products subsequently onboarded under this category:

Product Name	SKU Code
mrsp	Accio Work Business
mrsp	Accio Work Personal

[Network Upgrade] Upgrades on Aug. 28, 2026(Supplement)

Mon, 24 Aug 2026 06:53:58 GMT

Affected Time

2026-08-28 00:00:00 ~ 2026-08-28 06:00:00

Effected time

Aug. 28, 2026 00:00:00 - Aug. 28, 2026 06:00:00 (UTC+08)

Changes

To improve service quality and system stability, the infrastructure and network team will perform network equipment upgrades on Aug. 28, 2026 (UTC+08). The changes are Software maintenance/upgrade, cold patch.

Effected scope

Bangkok Zone A

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.

[Product Change] Discontinuation Notice for Legacy APIs of Simple Log Service

Mon, 24 Aug 2026 04:46:03 GMT

Affected Time

2026-08-27 00:00:00 (UTC+08)

Description:

Thank you for your continued support of Alibaba Cloud. Due to service upgrades, the following legacy APIs of Simple Log Service (SLS) will be officially discontinued on August 27, 2026:

ListLogStoreTopics
GetData
GetDataMeta
GetMetricData

After the discontinuation, these APIs will no longer provide any services, and all related API calls will fail.

Recommendation:

If you still need to use the above APIs, or if you have any other related questions, please feel free to contact us at any time by submitting a ticket or calling our service hotline.

【Product Change】General Availability announcement for AI Gateway New Serverless Version

Mon, 24 Aug 2026 03:21:45 GMT

Affected time

2026-09-01, General Availability

Change and impact

Dear Alibaba Cloud user, the public beta of the new Serverless edition of AI Gateway will end on August 31 and will be officially commercialized as of September 1. Existing public beta instances will be retained by default and automatically converted to commercial instances, with no migration required for instance configurations or business data. If you no longer wish to continue using the relevant instances, please delete them before the official commercialization on September 1 to avoid incurring charges after commercialization. For more details about public preview, please refer to <Public preview of AI Gateway Serverless (new)>.

Action required

This upgrade has no impact on new users. Public beta users should evaluate whether to continue using the service; if not, please delete your instances promptly to avoid incurring bills after commercialization.

If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

[Product Change] Name Changes of Alibaba Cloud's Managed Security Service

Mon, 24 Aug 2026 02:12:16 GMT

Dear customer,

We are sending you this notice to notify you about the name changes of Managed Security Service that will take place at 18:00 CST (UTC+8) August 31, 2026.

The changes will affect the following services:

Managed Security Service will be changed to Managed Security Service.

Thank you for your continued support! If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

August 25, 2026 Price Adjustment of Domain Names Notice

Sat, 22 Aug 2026 09:26:50 GMT

Affected Time

2026-08-25 00:00:00 (UTC+08)

Price Adjustment Reason

Due to the increase in registry costs, after careful consideration, it is decided to adjust the domain name price as follows at 00:00 on August 25th, 2026.

Price Adjustment TLDs

.skin: Renewal Price: $19.99/year, Transfer Price: $19.99

.hosting/.game: Registration Price: $413/first year, Renewal Price: $440/year, Transfer Price: $440

.tickets: Registration Price: $469/first year, Renewal Price: $500/year, Transfer Price: $500

Alibaba Cloud is committed to providing users with high-quality domain name services. In the future, we will continue to adjust (decrease/increase) domain name prices in a timely and reasonable manner according to changes in domain name costs, and always provide you with high-quality professional services! Thank you for your understanding and support!

Sep 2026 Simple Message Queue (formerly MNS) Upgrade Notice

Sat, 22 Aug 2026 09:26:38 GMT

Affected Time

2026-09-01 12:00:00 ~ 2026-09-01 18:00:00 [UK (London), US (Silicon Valley), US (Virginia), US (Atlanta), Mexico]

2026-09-01 22:30:00 ~ 2026-09-02 05:00:00 [China (Beijing), China North 2 Ali Gov 1, China North 2 Finance, Singapore, China (Qingdao), UAE (Dubai)]

2026-09-03 22:30:00 ~ 2026-09-04 05:00:00 [South Korea (Seoul), China (Hong Kong), China North West 2 (Zhongwei), China (Guangzhou)]

2026-09-08 22:30:00 ~ 2026-09-09 05:00:00 [China (Shanghai), China East 2 Finance, China (Shenzhen), China South 1 Finance, China (Ulanqab), China (Ulanqab) GIC]

2026-09-10 22:30:00 ~ 2026-09-11 05:00:00 [China (Hangzhou), China East 1 Finance, China (Zhangjiakou), Japan (Tokyo), Thailand (Bangkok), China (Hohhot)]

2026-09-15 22:30:00 ~ 2026-09-16 05:00:00 [China (Beijing), Singapore, Malaysia (Kuala Lumpur), Malaysia (Johor), Philippines (Manila)]

2026-09-17 05:30:00 ~ 2026-09-17 12:00:00 [Germany (Frankfurt), SAU (Riyadh)]

2026-09-17 22:30:00 ~ 2026-09-18 05:00:00 [China (Shanghai), China East 2 Finance, China (Shenzhen), China South 1 Finance, China (Chengdu), Indonesia (Jakarta)]

2026-09-22 22:30:00 ~ 2026-09-23 05:00:00 [China (Hangzhou), China East 1 Finance, China (Zhangjiakou), China (Heyuan), Heyuan ACDR Auto]

Upgrade Impact

During the upgrade, MNS related services and console access may be interrupted or be denied to connect. Each crash or connection refused will not exceed 1 minute. Please be prepared for the interruption. For management operations, please avoid the maintenance period.

We apologize for any inconvenience caused. If you have any questions, please feel free to contact us by submitting a ticket any time.

Notice of Tax Rule Changes in Uzbekistan

Sat, 22 Aug 2026 09:26:11 GMT

Dear Customer,

Pursuant to the Uzbekistan government's regulations on cross-border digital services, starting from 1 September 2026, Alibaba Cloud is required to collect a 12% Uzbekistan value-added tax (VAT) on the services provided to non-business customers who are not VAT-registered(B2C) in Uzbekistan. All VAT collected from customers in Uzbekistan will be remitted to the Uzbekistan tax authority.

To confirm your VAT-registered status, please proceed to Console, access "Expense and Costs - Invoices- Tax ID" to fill in your VAT Registration Number ("VRN"). For customers who do not provide a VRN, Alibaba Cloud will assume they are not VAT-registered and collect a 12% Uzbekistan VAT.

If you have any further questions, please feel free to contact your Alibaba Cloud business representative or our support team by opening a support ticket through the console.

Thank you for your ongoing support.

Alibaba Cloud

Notice of Tax Rule Changes in Kenya

Sat, 22 Aug 2026 09:25:57 GMT

Dear Customer,

Pursuant to the Kenya government's regulations on cross-border digital services, starting from 1, September 2026, Alibaba Cloud is required to collect a 16% Kenya value-added tax (VAT) on the electronic services provided to all customers in Kenya. All VAT collected from customers in Kenya will be remitted to the Kenya tax authority (Kenya Revenue Authority ).

If you have any further questions, please feel free to contact your Alibaba Cloud business representative or our support team by opening a support ticket through the console.

Thank you for your ongoing support.

Alibaba Cloud

【Product Change】Change/Upgrade announcement for Link Visual Root Cert & Domain

Sat, 22 Aug 2026 09:25:42 GMT

Affected time

2026-09-18 Change/Upgrade

Change and impact

Thanks for your support of Alibaba Cloud. The globally trusted root certificate GlobalSign Root R1 issued by the third-party certificate authority GlobalSign is approaching expiration. This is an industry-wide, scheduled root certificate transition and not a change initiated by Alibaba Cloud. Alibaba Cloud Link Visual will therefore upgrade its root certificate and access domains across multiple regions. Please update the root certificate on your devices and switch to the new domains before the applicable regional switch time.

Scope of affected devices: devices that use video activation codes.

If you do not complete these actions in time, your devices will be unable to connect to Alibaba Cloud Link Visual after the certificate expires. The regional switch schedule is as follows:

Shanghai, Shenzhen, and Germany: September 18, 2026, 00:00:00 (Beijing Time, UTC+8)
Japan, US (Silicon Valley), and US (Virginia): October 31, 2026, 00:00:00 (Beijing Time, UTC+8)
Singapore: Submit a ticket to confirm the switch time.

Action required

If your online services rely on this service, submit an Alibaba Cloud ticket to obtain the latest Alibaba Cloud Link Visual SDK and complete the upgrade before the applicable regional switch time to avoid service disruption.

Update method: Submit an Alibaba Cloud ticket to obtain the latest Alibaba Cloud Link Visual SDK.

If you have any questions, please contact us via our support hotline or by submitting a ticket.

If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

ApsaraMQ for RocketMQ September 2026 Upgrade Notice

Sat, 22 Aug 2026 09:25:29 GMT

Affected Time

2026-09-02 22:30:00 ~ 2026-09-03 05:00:00 (UTC+08) [cn-shenzhen, cn-beijing, mq-internet-access, cn-hongkong, cn-shanghai-finance-1, cn-chengdu, cn-shenzhen-finance-1, cn-guangzhou, cn-fuzhou]

2026-09-07 22:30:00 ~ 2026-09-08 05:00:00 (UTC+08) [cn-hangzhou, cn-beijing, cn-qingdao, cn-zhangjiakou, cn-north-2-gov-1, cn-wulanchabu, cn-beijing-finance-1, ap-northeast-1]

2026-09-09 10:00:00 ~ 2026-09-09 12:00:00 (UTC+08) [eu-central-1, eu-west-1]

2026-09-09 22:30:00 ~ 2026-09-10 05:00:00 (UTC+08) [cn-shanghai, cn-shenzhen, ap-southeast-1, cn-hongkong, ap-southeast-7, cn-zhengzhou, cn-guangzhou, ap-southeast-5, cn-qingdao-acdr-ut-1]

2026-09-14 22:30:00 ~ 2026-09-15 05:00:00 (UTC+08) [cn-hangzhou, cn-shanghai, mq-internet-access, cn-qingdao, ap-northeast-1, ap-northeast-2, cn-wulanchabu, ap-southeast-6]

2026-09-16 14:00:00 ~ 2026-09-16 18:00:00 (UTC+08) [us-east-1, us-west-1, us-southeast-1, na-south-1]

2026-09-16 22:30:00 ~ 2026-09-17 05:00:00 (UTC+08) [cn-beijing, cn-shenzhen, cn-hongkong, ap-southeast-1, cn-hangzhou-finance, cn-heyuan, cn-huhehaote, ap-southeast-3]

2026-09-21 22:30:00 ~ 2026-09-22 05:00:00 (UTC+08) [cn-hangzhou, cn-shanghai, cn-qingdao, ap-southeast-1, cn-chengdu, ap-southeast-3, ap-southeast-5, cn-shenzhen-finance-1]

2026-09-23 07:00:00 ~ 2026-09-23 10:00:00 (UTC+08) [me-east-1, me-central-1]

2026-09-23 22:30:00 ~ 2026-09-24 05:00:00 (UTC+08) [cn-shenzhen, cn-beijing, cn-zhangjiakou, cn-north-2-gov-1, cn-zhengzhou, ap-southeast-6, cn-heyuan, ap-southeast-7, cn-huhehaote]

2026-09-28 22:30:00 ~ 2026-09-29 05:00:00 (UTC+08) [cn-shanghai, cn-hangzhou, cn-zhangjiakou, mq-internet-access, cn-hangzhou-finance, cn-beijing-finance-1, ap-northeast-2, cn-shanghai-finance-1]

Update Content

ApsaraMQ for RocketMQ in the corresponding region, including access methods over TCP, MQTT, and HTTP

Upgrade Impact

During the upgrade, you may experience the following:

1. Sub-second disconnections may occur on the console and individual cluster nodes (duration is proportional to cluster scale), potentially accompanied by brief message latency. While the built-in client-side automatic retry mechanism typically ensures business continuity, a small number of exception logs may appear in your application as an expected behavior.

2. Message duplication may occur during the upgrade. Please ensure your applications implement idempotent message consumption following best practices to prevent duplicate data from impacting your business.

3. Please refrain from performing management operations such as creating or deleting topics in the console during the upgrade to avoid operation failures or configuration anomalies caused by service state changes.

4. HTTP access may experience brief disconnections or connection rejections, with each incident typically lasting no more than 1 minute. Ensure your clients are configured with appropriate reconnection and retry strategies to guarantee eventual request success.

Additionally, we recommend monitoring your critical workloads in real time using the monitoring feature. For configuration details, please click Monitoring and Alerting in the left-side navigation pane of the RocketMQ console.

We sincerely apologize for any inconvenience caused. Should you have any questions or require assistance, please feel free to submit a ticket at any time. Thank you for your understanding and cooperation.

[Product Change] Name Changes of Alibaba Cloud's JVS Agent Suite

Sat, 22 Aug 2026 09:24:19 GMT

Dear customer,

We are sending you this notice to notify you about the name changes of JVS Agent Suite that will take place at 18:00 CST (UTC+8) September 7, 2026.

The changes will affect the following services:

JVS Agent Suite will be changed to Agentic Computer.

Thank you for your continued support! If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

[Network Upgrade] Upgrades on Aug. 27, 2026(Supplement)

Sat, 22 Aug 2026 09:24:08 GMT

Affected Time

2026-08-27 08:00:00 ~ 2026-08-27 14:00:00

Effected time

Aug. 27, 2026 08:00:00 - Aug. 27, 2026 14:00:00 (UTC+08)

Changes

To improve service quality and system stability, the infrastructure and network team will perform network equipment upgrades on Aug. 27, 2026 (UTC+08). The changes are Software maintenance/upgrade, cold patch.

Effected scope

Frankfurt Zone C/ A

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.

ApsaraMQ for RabbitMQ September 2026 Upgrade Notice

Sat, 22 Aug 2026 09:23:05 GMT

Affected Time

2026-09-01 22:30:00 ~ 2026-09-02 03:00:00 (UTC+08) [Hangzhou, Shenzhen, Zhengzhou, Chengdu]

2026-09-03 22:30:00 ~ 2026-09-04 03:00:00 (UTC+08) [Beijing, Shanghai, Kuala Lumpur]

2026-09-08 10:30:00 ~ 2026-09-08 15:00:00 (UTC+08) [Frankfurt, Silicon Valley, Virginia]

2026-09-08 22:30:00 ~ 2026-09-09 03:00:00 (UTC+08) [Tokyo, Singapore, Jakarta, Hong Kong, Saudi Arabia, Manila, Thailand, Dubai, Wulanchabu, Wulanchabu-Gic]

2026-09-10 22:30:00 ~ 2026-09-11 03:00:00 (UTC+08) [Hangzhou, Shanghai, Beijing, Shenzhen, Qingdao, Huhhot, Zhangjiakou, Guangzhou, Beijing-Finance, Shanghai-Finance, Hangzhou-Finance]

2026-09-15 22:30:00 ~ 2026-09-16 03:00:00 (UTC+08) [Hangzhou, Shenzhen, Zhengzhou, Chengdu]

2026-09-17 22:30:00 ~ 2026-09-18 03:00:00 (UTC+08) [Beijing, Shanghai, Jakarta]

2026-09-20 22:30:00 ~ 2026-09-21 03:00:00 (UTC+08) [Hong Kong]

2026-09-22 10:30:00 ~ 2026-09-22 15:00:00 (UTC+08) [Frankfurt, Silicon Valley, Virginia]

2026-09-22 22:30:00 ~ 2026-09-23 03:00:00 (UTC+08) [Tokyo, Singapore, Kuala Lumpur, Hong Kong, Saudi Arabia, Manila, Thailand, Dubai, Wulanchabu, Wulanchabu-Gic]

2026-09-24 22:30:00 ~ 2026-09-25 03:00:00 (UTC+08) [Hangzhou, Shanghai, Beijing, Shenzhen, Qingdao, Huhhot, Zhangjiakou, Guangzhou, Beijing-Finance, Shanghai-Finance, Hangzhou-Finance]

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.

Optimized billing time field display for per-minute billed products

Fri, 21 Aug 2026 02:37:45 GMT

Affected Time

2026-08-21 00:00:00 (UTC+08)

Dear Alibaba Cloud customer,

To help you reconcile your bills more clearly, we plan to optimize the display of billing time fields for per-minute billed products, including Model Studio. This adjustment affects only the display of times; it does not affect the actual billed amount.

What's changing

The "Service Start Time" and "Service End Time" fields in your bill will change from displaying the time of fee calculation to displaying the time when you actually initiated the calls.

Field	Before	After
Service start/end time	Minute of fee calculation	Minute of your actual calls
Consumption time	Unchanged	Unchanged
Bill amount	Unchanged	Unchanged

What to note

After the adjustment, please note the following two changes:

Usage generated within the same minute may appear as multiple bill records with the same service time because it was billed in batches. If this happens, please combine the usage and amounts of these records when reconciling—the total amount is unaffected.

The "Consumption Time" field itself remains unchanged, but because "Service Start Time" now shows your actual call time, the two may no longer match. Please use "Service Start Time" to determine the period to which usage belongs.

Rollout timeline

This adjustment will be gradually rolled out starting August 21, 2026, and is expected to take full effect in early September.

[Network Upgrade] Upgrades on Aug. 26, 2026(Supplement)

Thu, 20 Aug 2026 08:34:17 GMT

Affected Time

2026-08-26 01:00:00 ~ 2026-08-26 07:00:00

Effected time

Aug. 26, 2026 01:00:00 - Aug. 26, 2026 07:00:00 (UTC+08)

Changes

To improve service quality and system stability, the infrastructure and network team will perform network equipment upgrades on Aug. 26, 2026 (UTC+08). The changes are Software maintenance/upgrade, cold patch.

Effected scope

Jakarta Zone A

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.

Anti-DDoS Native Enhanced EIP (Malaysia Region) Network Offline Announcement

Thu, 20 Aug 2026 07:22:13 GMT

Affected Time

2026-08-27 00:00:00 ~ 2026-08-27 06:00:00 (UTC+08)

Upgrade content

Anti-DDoS Native Enhanced EIP(Malaysia Region) Network Offline Announcement

Impact of the upgrade

During the upgrade, there will be no impact on business theoretically.In extreme cases, long connections may be interrupted 1 to 2 times (within 30 seconds each time). The client can be restored by reconnecting. Please implement a reconnection and retry mechanism in the client.

We apologize for the inconvenience caused to you. If you have any questions or need to make an appointment to change the time, you can contact us at any time through DingTalk group or work order. Thank you for your support and cooperation!

Anti-DDoS Proxy (Outside Chinese Mainland) Sec-CMA 2.0 Protection System Upgrade Notice

Thu, 20 Aug 2026 05:41:54 GMT

Affected Time

2026-08-28 00:00:00 ~ 2026-08-28 06:00:00 (UTC+08)

Upgrade content

Anti-DDoS Proxy (Outside Chinese Mainland) Sec-CMA 2.0 protection system upgrade to improve DDoS attack protection capabilities

Impact of the upgrade

During the upgrade window, traffic goes through Anti-DDoS Proxy may experience increased latency, short-term retransmissions or minor packet loss, and 1-2 reconnections for long TCP sessions. Please ensure reconnection and retry mechanisms for relevant services to enhance service fault tolerance.

Please refer to the relevant notification in your Message/Email for details on affected instances. If you have not received a notification, then the instances under your account are not affected.

We apologize for any inconvenience caused. If you have any questions, please feel free to contact us by submitting a ticket any time.

【Product Change】Restriction announcement for ACR Personal Edition: Untagged Image Data

Wed, 19 Aug 2026 07:35:23 GMT

Affected time

2026-09-19

Change and impact

Change Details

Usage restrictions will be introduced for all image manifests and associated image layers that are not referenced by any image tag. The system will automatically identify and restrict access to unreferenced image data. Image artifacts will only be accessible through tags.

Impact

Image manifests and associated image layers that are not referenced by any tag will no longer be accessible.
This change will not affect image push operations.

Action required

For both existing and newly added image data that is not referenced by any tag, we recommend using image tags to manage and maintain your images. Please follow standardized tag-based push and pull practices to ensure that images stored in ACR Personal Edition are retained and remain accessible.

If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

[Network Upgrade] Upgrades on Aug. 21, 2026(Supplement)

Mon, 17 Aug 2026 07:36:58 GMT

Affected Time

2026-08-21 00:00:00 ~ 2026-08-21 06:00:00

Effected time

Aug. 21, 2026 00:00:00 - Aug. 21, 2026 06:00:00 (UTC+08)

Changes

To improve service quality and system stability, the infrastructure and network team will perform network equipment upgrades on Aug. 21, 2026 (UTC+08). The changes are Software maintenance/upgrade, cold patch.

Effected scope

Bangkok Zone A
Jakarta Zone A

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.

Notice on the Discontinuation of New Purchases and Service Support for Lingma

Sat, 15 Aug 2026 05:23:52 GMT

Affected Time

2026-09-15 22:00:00 (UTC+08)

2027-04-15 22:00:00 (UTC+08)

2027-09-15 22:00:00 (UTC+08)

Scope and Impact of the Change

Due to product upgrade adjustments, certain individual and enterprise subscriptions under Qoder CN will gradually stop supporting new purchases, additional seats, renewals, and service support.

This upgrade only affects certain products originally under Lingma and Tongyi Lingma. It does not affect other products under Qoder CN.

This change applies to the following six products:

Qoder CN (formerly Lingma) Individual Pro: lingma_individualPro_public_cn
Qoder CN (formerly Lingma) Individual Credits Resource Pack: lingma_addOnPackPersonal_public_cn
Qoder CN (formerly Lingma) Enterprise Standard: lingma_enterpriseStandard_public_cn
Qoder CN (formerly Lingma) Enterprise Standard Shared Credits Resource Pack: lingma_addOnPackStandard_public_cn
Tongyi Lingma Enterprise Dedicated Edition: lingma_enterpriseDedicated_public_cn
Tongyi Lingma Enterprise Dedicated Edition: lingma_enterpriseDedicated_public_intl

Specific Timeline

Starting from 22:00 on September 15, 2026:

New purchases of Qoder CN (formerly Lingma) individual subscriptions and individual Credits resource packs will stop.
New purchases of Qoder CN (formerly Lingma) Enterprise Standard, Qoder CN (formerly Lingma) Enterprise Standard Credits resource packs, and Tongyi Lingma Enterprise Dedicated Edition will stop.
Qoder CN (formerly Lingma) Individual,Qoder CN (formerly Lingma) Enterprise Standard, and Tongyi Lingma Enterprise Dedicated Edition will no longer receive new models.

Starting from 22:00 on April 15, 2027:

Renewals for Qoder CN (formerly Lingma) individual subscriptions will stop.
Renewals and additional seats for Qoder CN (formerly Lingma) Enterprise Standard and Tongyi Lingma Enterprise Dedicated Edition will stop.
IDE updates will stop. New versions of the IDE will no longer support login with former Lingma accounts.

Starting from 22:00 on September 15, 2027:

Existing Qoder CN (formerly Lingma) and Tongyi Lingma subscriptions will stop providing services.
Individual and enterprise users are advised to plan ahead and complete the upgrade to the new Qoder CN All-in-One subscription before this date. If you have any questions about existing contracts or subscription rights, please contact your business manager or reach out to us by submitting an order.

Recommended Actions

Both former Lingma individual users and enterprise users can upgrade to the Qoder CN ( Full Suite) subscription. A single subscription unlocks the full suite of Qoder CN product capabilities, including Qoder CN IDE, Qoder CN JetBrains Plugin, Qoder CN CLI, QoderWake CN, Qoder CN Mobile, and Qoder CN Cloud Agents.

After upgrading, you will continue to receive model updates and expert suite support for Qoder CN IDE and the JetBrains Plugin. Capabilities such as Quest, RepoWiki, Agent sessions, and Subagents can also be used on demand and will no longer be subject to the daily usage limits of former Lingma. In addition, after upgrading to Qoder CN ( Full Suite) , your AI conversation history under the original account will continue to be retained and remain available for normal use.

If you have any questions, please feel free to contact us at any time through a support ticket or our service hotline.

ApsaraMQ for MQTT Billing Notice for VPC Dedicated Access Points

Fri, 14 Aug 2026 16:03:27 GMT

Affected Time

2026-09-14 00:00:00 (UTC+08)

Billing start date: September 14, 2026

Billing details: Starting from September 14, 2026, VPC dedicated access points of ApsaraMQ for MQTT will be officially commercialized and billed. For details about the billing standards, see the help documentation.

Alibaba Cloud hereby reminds you that if you no longer need this service, please unsubscribe from or release the relevant instances before billing starts to avoid incurring fees.

If you have any questions, please feel free to contact us at any time by submitting a ticket or calling the service hotline.

【Product Change】Modification announcement for Zero-amount pay-as-you-go orders for EBS

Fri, 14 Aug 2026 16:03:04 GMT

Affected time

2026-09-20 Modification

Change and Impact

Thank you for your support of Alibaba Cloud. To improve efficiency and user experience, starting from September 20, 2026, operations such as new purchases, configuration changes, and capacity expansions for pay-as-you-go cloud disks and elastic ephemeral disks of Block Storage (EBS) will have their order-related processes simplified, and zero-amount order records will no longer be generated. This change has no impact on the operation, usage, metering, billing, or historical order queries of the relevant products.

Impact of the Change

After this change takes effect, new purchases, configuration changes, and capacity expansions for pay-as-you-go cloud disks and elastic ephemeral disks — initiated through the product purchase page, the reconfiguration page, OpenAPI, SDKs, or other channels — will no longer generate zero-amount order records.

Related pay-as-you-go orders will no longer be displayed on the "My Orders" page in the Expenses and Cost Management console
Related pay-as-you-go orders will no longer be returned via BssOpenAPI (GetOrderDetail, QueryOrders, etc.)

Action required

If you need to obtain operation records for the relevant resources, you can query audit logs through the ActionTrail console or OpenAPI (https://www.alibabacloud.com/zh/product/actiontrail).

If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

【Model Studio】DeepSeek-V4-Flash-0731 Price Increase Notice

Fri, 14 Aug 2026 15:28:58 GMT

Affected Time

2026-08-17 00:00:00 (UTC+08)

Change Details

Effective 00:00:00 (UTC+8) on August 17, 2026, Model Studio will implement a price increase for the DeepSeek-V4-Flash-0731 model, transitioning to a Peak/Off-Peak pricing structure. Under this new model, Off-Peak rates will be set at 50% of Peak rates.

Off-Peak Hours: 22:00–08:00 (UTC+8)
Peak Hours: All other times

Detailed pricing information is as follows:

Region	Billing Item	Original Price (USD/1M tokens)	Time Period	New Price (USD/1M tokens)
Beijing、Global	Input	$ 0.138	Off-Peak	$0.212
			Peak	$0.424
	Output	$ 0.275	Off-Peak	$0.636
			Peak	$1.272
	Cache	$ 0.028	Off-Peak	$0.021
			Peak	$0.042
Singapore	Input	$ 0.2	Off-Peak	$0.22
			Peak	$0.44
	Output	$ 0.4	Off-Peak	$0.66
			Peak	$1.32
	Cache	$ 0.04	Off-Peak	$0.022
			Peak	$0.044

Thank you for your continued trust and support in Model Studio.

[Product Change] Name Changes of Alibaba Cloud's Multi-agent Governance and Collaboration Platform

Fri, 14 Aug 2026 04:32:53 GMT

Dear customer,

We are sending you this notice to notify you about the name changes of Multi-agent Governance and Collaboration Platform that will take place at 18:00 CST (UTC+8) August 28, 2026.

The changes will affect the following services:

Multi-agent Governance and Collaboration Platform will be changed to Alibaba Cloud AgentCore.

Thank you for your continued support! If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

AliwareMQ for MQTT supplementary upgrade notice in August 2026

Thu, 13 Aug 2026 11:48:42 GMT

Affected Time

2026-08-20 08:00:00 ~ 2026-08-20 12:00:00 (UTC+08) [Dubai]

2026-08-20 22:00:00 ~ 2026-08-21 02:00:00 (UTC+08) [Manila]

[Network Upgrade] Upgrades on Aug. 19, 2026(Supplement)

Thu, 13 Aug 2026 07:56:45 GMT

Affected Time

2026-08-19 00:00:00 ~ 2026-08-19 06:00:00

Effected time

Aug. 19, 2026 00:00:00 - Aug. 19, 2026 06:00:00 (UTC+08)

Changes

To improve service quality and system stability, the infrastructure and network team will perform network equipment upgrades on Aug. 19, 2026 (UTC+08). The changes are Software maintenance/upgrade, cold patch.

Effected scope

Singapore Zone B
Bangkok Zone A

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.

Web Application Firewall Web Core Protection, Bot Management, and Log Service upgrade notice

Thu, 13 Aug 2026 06:36:12 GMT

Affected Time

2026-09-10 00:00:00 (UTC+08)

Dear Alibaba Cloud users,

Alibaba Cloud Web Application Firewall (WAF) 3.0 will upgrade the Web Core Protection, Bot Management, and Log Service modules in terms of functionality and billing.

Effective dates

● Billing adjustment for Web Core Protection rules: Effective from 2026-09-10 00:00:00 (UTC+8).

● Billing criteria adjustment for Bot Management request processing fee: Effective from 2026-09-10 00:00:00 (UTC+8).

● Log Service upgrade: Phased rollout starting from 2026-08-14 00:00:00 (UTC+8).

Changes

1. Billing adjustment for Web Core Protection rules

Scope: WAF 3.0 pay-as-you-go edition

Description:

New billing logic

Previous billing logic

• Default template

–No protected objects exist under the WAF instance: 0 SeCU/hour.

–Protected objects already exist under the WAF instance: 10 SeCU/hour.

–Note: Billing applies at the above rates regardless of whether the template is enabled or disabled.

• Non-default template

–Billing rate: 10 SeCU/hour.

–Note: Billing applies at the above rates regardless of whether the template is enabled or disabled.

• Default template

– Template not bound to protected objects: 0 SeCU/hour.

– Template bound to protected objects: 3 SeCU/hour.

–Note: Billing starts from the time protected objects are bound, regardless of whether the template is enabled or disabled.

• Non-default template

–Billing rate: 3 SeCU/template/hour.

–Note: Billing applies at the above rates regardless of whether the template is enabled or disabled.

2. Billing criteria adjustment for Bot Management request processing fee

Scope: WAF 3.0 pay-as-you-go edition users who have activated Bot Management

Description:

The billing criteria for Bot Management -request processing fee will be strictly aligned with the existing billing rules documented on the official website, which define the billable request count as “the number of requests that hit protected objects within a complete hour.” After this alignment, the system will more accurately cover requests that hit protected objects.

Compared to the historical billing criteria, the revised billable request count will more completely and accurately reflect the actual protection status. As a result, this fee may increase.

During the phased rollout, the fee displayed in Bill Management may be inaccurate. The actual billed amount prevails.

3. Log Service upgrade

Scope: WAF 3.0 pay-as-you-go edition users who have activated Log Service

Description:

1. Underlying storage architecture upgrade and parallel strategy

WAF Log Service will undergo an underlying storage architecture upgrade. During the upgrade, the system will create a new Logstore for users who have activated Log Service and implement a dual-write mechanism for both the old and new Logstores, with log data stored in both simultaneously. This parallel period lasts 180 days, during which the new Logstore incurs no additional fees. After the parallel period ends, the old Logstore will stop accepting writes, and the system will retain only the new Logstore as the sole storage, billed at standard rates.

During the parallel period, it is normal for the Simple Log Service (SLS) console to display data from both the old and new Logstores simultaneously.

2. Automatically migrated configurations

This upgrade will automatically migrate the following low-risk configurations, which will take effect automatically on the new Logstore without requiring manual action:

● Hot storage TTL

● Infrequent access storage TTL

● Data retention period

● Index data lifecycle

● Logstore creation parameters such as Shard splitting

3. Manually handled configurations

Some configurations cannot be automatically migrated and require manual configuration on the new Logstore. For detailed instructions, see Log service migration guide.

Strictly follow Log service migration guide to complete the migration within the parallel period. If configurations that require manual migration are not completed, new logs may not be properly indexed or queried, which could affect your business operations.

4. Console changes during the phased rollout

A Logstore switching entry is added below the Log Service title, which allows you to switch between the old and new Logstores. After switching, the storage usage and button states are updated accordingly. Pay-as-you-go users can perform operations such as upgrading capacity, downgrading, configuring log settings, enabling log encryption, and disabling the service on both the old and new Logstores through the console.

5. Billing description

A new “Log Storage” billing item is added to the billing statement. The specific rules are as follows:

● During the parallel period: The billed amount for the new Logstore is 0 during the 180-day free period.

● After the parallel period: The new Logstore is billed at standard rates.

For WAF instances not covered during the phased rollout, the billed amount for this item is 0.

6. Operation mapping rules during the transition period

● Disabling Log Service: During the transition period, disabling Log Service will close both the old and new Logstores simultaneously.

● Re-enabling Log Service: If you re-enable Log Service after disabling it, the system will only activate the new Logstore and will no longer perform dual-write.

● Scaling operations: Capacity adjustments are performed simultaneously on both the old and new Logstores.

If you have any questions, feel free to contact us through the DingTalk security service group or your account manager. Thank you for your support and cooperation.

Security Center - Agentic CSPM Detection Capability Upgrade Notice

Thu, 13 Aug 2026 02:11:20 GMT

Affected Time

2026-08-21 00:00:00 ~ 2026-08-21 23:59:59 (UTC+08)

Change Description

To provide more comprehensive security protection for your cloud assets, starting from August 21, 2026, Security Center's "Agentic Cloud Security Posture Management (CSPM)" will add security detection support for the following cloud service instances: E-MapReduce (EMR) clusters, Microservices Engine (MSE) clusters, ApsaraMQ for RabbitMQ instances, ApsaraMQ for RocketMQ 5.0 instances, ApsaraMQ for RocketMQ 4.0 instances, and Simple Application Server instances. Along with the launch of these detection capabilities, the preceding instances will be included in the billable instance scope of CSPM and billed according to the current billing standards.

Impact of the Change

Subscription users:

After the upgrade takes effect, newly connected instances of the preceding types will be counted toward the billable instance quota you have purchased. You can adjust the connection scope in asset access management.

Pay-as-you-go users:

After the upgrade takes effect, the system will automatically calculate fees based on the number of billable instances actually connected each day. No action is required to obtain the new detection capabilities.

Note: Big data and message queue assets typically carry core business data and are prime targets for attackers. We recommend that you keep them connected for full protection. We also recommend that you review the connection status of the relevant instances before the effective date to confirm your protection scope in advance and avoid unexpected charges.

If you have any questions, please feel free to contact us via a ticket or the service hotline.

【Product Change】EOS announcement for EOS for RTC for Apache Flink Engine 11.1/11.2

Wed, 12 Aug 2026 10:14:30 GMT

Affected time

2027-02-07 EOS

Change and Impact

Affected time

VVR 11.1: End of Support (EOS) on December 4, 2026.
VVR 11.2: End of Support (EOS) on February 8, 2027.

Change and impact

To better serve our users, Alibaba Cloud Realtime Compute for Apache Flink has established a comprehensive Engine Lifecycle Management system (Lifecycle Policies). We would like to remind you to review these policies and check via the console or OpenAPI whether your current jobs are still running on engine versions that are approaching End of Support (EOS).

According to the Release Notes, VVR 11.1 (Apache Flink 1.20.1, GA on June 4, 2025) will reach EOS on December 4, 2026; VVR 11.2 (Apache Flink 1.20.2, GA on August 8, 2025) will reach EOS on February 8, 2027. After EOS, these versions will no longer receive technical support or security updates. To prevent potential security risks or stability issues from affecting your business, we strongly recommend that you upgrade the affected jobs as soon as possible.

Impact: Jobs that remain on VVR 11.1 or VVR 11.2 will no longer receive technical support or security updates after the respective EOS date.

Action required

Upgrade recommendations: Upgrade to VVR 11.3 or another higher version that has not reached EOS. Before upgrading, validate job dependencies, connector compatibility, and Savepoint compatibility. For details, see Upgrade the engine version of a deployment.

Upgrade support: If you encounter any issues during the upgrade or require technical guidance, please contact our technical support team. We are here to provide the necessary assistance to ensure your upgrade process is smooth and successful.

If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

[Product Change] Name Changes of Alibaba Cloud's Cloud Skills Portal

Wed, 12 Aug 2026 09:30:03 GMT

Dear customer,

We are sending you this notice to notify you about the name changes of Cloud Skills Portal that will take place at 00:00 CST (UTC+8) August 26, 2026.

The changes will affect the following services:

Cloud Skills Portal will be changed to Cloud Agent Catalog.

Thank you for your continued support! If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

【Product Change】Upgrade announcement for Agentless of Security Center

Wed, 12 Aug 2026 08:17:52 GMT

Affected time

2026-09-10 Upgrade

Change and Impact

To provide you with stronger risk detection and closed-loop remediation capabilities, the "Agentless Detection" capability of Security Center will be progressively switched to "Agentic Agentless Detection" starting September 10, 2026. Building on the existing scanning capability, this upgrade adds the following two capabilities:

Parallel Sandbox Analysis: A security Agent autonomously investigates and traces attack paths based on the complete system context, covering dimensions such as vulnerability root-cause remediation, baseline configuration hardening, and intrusion artifact cleanup, and delivers a remediation and hardening report tailored to your actual deployment environment rather than a generic fix template.

Intelligent Vulnerability Remediation: Provides one-click intelligent remediation for detected application and system vulnerabilities, and automatically generates a remediated custom secure image, extending "risk discovery" into "closed-loop remediation".

Price change details

Product and module	Capability	Before adjustment	After adjustment
Security Center – Agentless Detection (Pay-as-you-go)	Agentless detection scanning and analysis	Billing method: billed by the volume of asset data scanned; Price: $0.03/GB	Billing method: billed by the volume of asset data scanned (AI Parallel Sandbox Analysis included); Price: $0.13/GB
	Agentless detection remediation	Capability not yet available	Billing method: billed by the number of vulnerabilities successfully remediated; Price: $1.33 per vulnerability

Action required

Notes on entitlements for existing users:

After the adjustment takes effect, the system will automatically bill according to the latest billing method and price. If you wish to continue using the pay-as-you-go service of Agentic Agentless Detection, no action is required; if you no longer wish to use it, you can disable the feature before the adjustment takes effect.

New users: After the adjustment takes effect, purchases must be made at the new price.

Note: Due to the adjustment of the system billing rules, once you switch to the new billing mode, you will not be able to revert to the previous billing mode. Please confirm carefully before proceeding.

If you have any questions, please feel free to contact us by submitting a ticket or calling our service hotline. Thank you for your support and trust in Alibaba Cloud!

If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

【Product Change】Qoder Desktop Display Name and Installation Path Adjustment Notice

Tue, 11 Aug 2026 03:32:54 GMT

Affected time

2026-08-18, Adjustment

Change and Impact

To standardize product-related information, Qoder will roll out the following changes in phases:

Starting from August 11, 2026, with version 1.24.0, the displayed application name will be changed from Qoder to Qoder IDE.

Starting from August 18, 2026, with version 1.25.0, the application installation directory and related path names will be adjusted as follows:

macOS: The application path will be changed from Qoder.app/Contents/MacOS/Electron to Qoder IDE.app/Contents/MacOS/Qoder.
Windows: The installation directory will be changed from Qoder to Qoder IDE, and the main executable will be changed from Qoder.exe to Qoder IDE.exe.
Linux: The package name will be changed from qoder to qoder-ide, and the main executable path will be changed from /usr/share/qoder/qoder to /usr/share/qoder-ide/qoder-ide.

These changes only affect the desktop application name, application file names, and installation path names, and will not impact existing product functionality or user data. The contracting entity, subscription billing, service agreements, and other commercial arrangements will remain unchanged. Existing users can continue using the product normally after upgrading, with no need to migrate user data.

Action required

If you use terminal software whitelisting, security controls, unified distribution, or automated deployment, please complete the updates to the application file names, installation directory, and related path configurations before August 18, 2026, to avoid any impact on the installation, upgrade, and normal use of version 1.25.0 and subsequent releases.

If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

Anti-DDoS Service Telecom Network Upgrade Notice on August 25th and August 26th, 2026

Tue, 11 Aug 2026 03:02:33 GMT

Affected Time

2026-08-25 00:00:00 ~ 2026-08-25 06:00:00 (UTC+08)

2026-08-26 00:00:00 ~ 2026-08-26 06:00:00 (UTC+08)

Upgrade Content

Anti-DDoS Proxy (Chinese Mainland) telecom network upgrade.

Upgrade Impact

During the upgrade window, traffic goes through Anti-DDoS Proxy (Chinese Mainland) telecom network may experience 2-3 times network jitter. Please ensure that you implement the reconnection and retry mechanism in your services to enhance the fault tolerance of your services. We apologize for any inconvenience caused. If you have any questions, please feel free to contact us by submitting a ticket any time.

[Network Upgrade] Upgrades on Aug. 13, 2026(Supplement)

Tue, 11 Aug 2026 02:55:33 GMT

Affected Time

2026-08-13 14:00:00 ~ 2026-08-13 19:00:00

Effected time

Aug. 13, 2026 14:00:00 - Aug. 13, 2026 19:00:00 (UTC+08)

Changes

To improve service quality and system stability, the infrastructure and network team will perform network equipment upgrades on Aug. 13, 2026 (UTC+08). The changes are Software maintenance/upgrade, cold patch.

Effected scope

Mexico Zone A

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.

Notice of Update to the Service Level Agreement (SLA) for PolarDB

Mon, 10 Aug 2026 11:26:02 GMT

Affected Time

2026-08-18 00:00:00 (UTC+08) Change

Alibaba Cloud will revise the Service Level Agreement ("SLA") for PolarDB. This update is intended to improve the transparency and completeness of the agreement.

Details of the revision: The following statement has been explicitly added to the SLA.

PolarDB for MySQL on ENS instances are excluded from SLA coverage and are therefore not subject to any availability commitment.

PolarDB for MySQL on ENS instances have previously been explicitly disclosed to customers in relevant product documentation as being excluded from the provisions of this SLA. This revision formally incorporates this existing rule into the SLA to enhance transparency and clarity. This update constitutes a formal refinement only and does not involve any substantive change to customer rights.

To review the revised Service Level Agreement, please visit the Product SLA Center (https://www.alibabacloud.com/help/legal/latest/product-sla).

If you have any questions, please contact us via support tickets (https://workorder-intl.console.aliyun.com/#/ticket/createIndex).

Thank you for choosing Alibaba Cloud.

【Product Change】Upgrade announcement for International SMS Template

Mon, 10 Aug 2026 07:02:26 GMT

Affected time

2026-09-09 Upgrade

Change and Impact

Change content

Thank you for your support of Alibaba Cloud. The international station will provide a new version of the service (service upgrade announcement) on July 23, 2025. Customers can directly send international/Hong Kong, Macao and Taiwan messages without creating templates in advance.

Therefore, it is planned to offline the function of creating and editing international/Hong Kong, Macao and Taiwan message templates in OpenAPI and console pages at 00:00:00 on September 9, 2026.

Impact of change

After this offline change, if you need to add new message content, you need to use the upgraded solution (see "Response Suggestions" below) to send international/Hong Kong, Macao and Taiwan messages. There is no need to create templates in advance.

For templates that have been created in history, you can still use existing plans to send international/Hong Kong, Macao and Taiwan messages.

Scope of inflence

Functions planned to be offline:
1) OpenAPI, CreateSmsTemplate- apply for SMS templates, UpdateSmsTemplate- modify SMS template interface, no longer support TemplateType = 3 (international/Hong Kong, Macao and Taiwan messages);
2) Old version console-template management, no longer supports adding and editing templates.

Action required

1) OpenAPI: Use the `SendMessageToGlobe` interface directly to send SMS messages.

2) New Console – Bulk Messaging Assistant: Send international or Hong Kong/Macau/Taiwan messages directly without needing to create templates.

We recommend upgrading to the aforementioned alternatives to benefit from superior functionality and performance.

If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

【Product Change】Upgrade announcement for Bailian Model Monitoring, Alerting & Logging

Mon, 10 Aug 2026 02:39:13 GMT

Affected time

2026-08-17, Upgrade

Change and Impact

Thank you for your support of Alibaba Cloud. The Bailian Model Monitoring, Alerting & Logging features will be upgraded on August 17, 2026,00:00:00. After the upgrade, the usage paths will be adjusted as follows:

Menu Structure Changes:

Before: "Model Monitoring" (including monitoring and logging) and "Model Alerting" (independent menu)
After: "Model Monitoring & Alerting" (integrating monitoring and alerting, with Monitoring Tab and Alerting Tab) and "Model Logging" (independent log management, with Audit Log Tab and Inference Log Tab)

Capability Upgrades (all free):

Free real-time monitoring: No manual setup required; view model invocation data out of the box
Free alerting: Simple authorization to use, no advanced monitoring setup needed
Audit logs enabled by default: Automatically records key invocation metadata (Request ID, processing time, model name, API Key, usage, latency, status, etc.)

Action required

This upgrade will not affect your feature usage. All existing data and configurations will be automatically migrated, and historical data will be fully preserved. After the upgrade, the menu layout will be more centralized with shorter operation paths. For detailed operation guidance, please refer to the help documentation or contact your account manager.

If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

[Network Upgrade] Upgrades on Aug. 12, 2026(Supplement)

Mon, 10 Aug 2026 02:38:58 GMT

Affected Time

2026-08-12 01:00:00 ~ 2026-08-12 07:15:00

To improve service quality and system stability, the infrastructure and network team will perform network equipment upgrades on Aug. 12, 2026 (UTC+08). The 2 changes include:

1. Time: Aug. 12, 2026 01:00:00 - Aug. 12, 2026 07:00:00 (UTC+08)

Changes: Software maintenance/upgrade, cold patch
Effected scope:
- Jakarta 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.

2. Time: Aug. 12, 2026 01:15:00 - Aug. 12, 2026 07:15:00 (UTC+08)

Changes: Software maintenance/upgrade, cold patch
Effected scope:
- Jakarta Zone C
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.

[Update] Code Security beta is ending and moving to paid billing

Thu, 06 Aug 2026 08:32:29 GMT

Affected Time

2026-08-14 00:00:00 (UTC+08)

Affected Products

Code Security

Change Details and Impact

Thank you for your support. The Code Security Beta (waf_codesec_public_cn) will end on August 14, 2026.

I. Beta offline arrangement

After you go offline, the Beta console entry and the Beta instance are unavailable. Users of the Beta edition can migrate to the commercial edition. They only need to use the current UID to order the commercial edition. Existing projects and scan task can be automatically synchronized without reconfiguration. The data of an unmigrated instance in Beta cannot be restored after it is offline. You must complete the migration in advance.

2. Billing description of the commercial version

The commercial version of Code Security (China site (aliyun.com) Code: codesec_v1_public_cn ; International site code: codesec_v1_public_intl) Billing standard:

China site (aliyun.com) 1 yuan= 100 Credits; International site $0.14= 100 Credits
SAST: You are billed based on the actual scan consumption Credit.
SCA: Pay by dependency package, 50 credits /dependency package.

Recommendation

Beta users must use the current UID to order the commercial version before the offline date in the region where they are located, and existing projects and scan task can be automatically synchronized. No additional operations are required:
- China site: https://common-buy.aliyun.com/?commodityCode=codesec_v1_public_cn
- International site: https://common-buy-intl.alibabacloud.com/?commodityCode=codesec_v1_public_intl
Documentation:
- Alibaba Cloud China site: https://help.aliyun.com/zh/document_detail/3042459.html
- International site: https://www.alibabacloud.com/help/zh/code-security
If you have any questions, please do not hesitate to contact us by submitting a ticket or calling our service hotline.

【Product Change】Billing Notice: Prometheus Now Commercially Available

Wed, 05 Aug 2026 09:42:55 GMT

Affected time

2026-09-04 Commercially Available

Change and Impact

Managed Service for Prometheus will officially become commercially available in the following four newly launched regions starting at 10:00:00 (UTC+8) on September 4, 2026: Johor, Zhongwei, Paris, and Huabei 6 General Industry Cloud.

To avoid unnecessary charges, if you no longer need to use Managed Service for Prometheus, we recommend that you remove and uninstall the Prometheus agents from the corresponding environments. For specific steps, please refer toBasic Agent Management.

Important: Managed Service for Prometheus was already commercialized in 2019. This notice is regarding the subsequent commercial launch of newly added regions for Managed Service for Prometheus.

For detailed pricing information about Managed Service for Prometheus, please see the Prometheus instance billing

Action required

Please be informed of the above billing changes.

If you have any questions, please feel free to contact us via our support hotline or by submitting a ticket.

Agentic Operations Platform STAROps: Investigation and RCA Are Now Generally Available

Wed, 05 Aug 2026 05:52:58 GMT

Affected Time

2026-08-16 00:00:00 (UTC+08)

Starting from 2026-08-16 00:00:00, the Quick Investigation, Deep Investigation, and Alert Root Cause Analysis features in the Agentic Operations Platform STAROps will be upgraded from Beta to general availability. Using these features will consume credits based on actual usage.

When you actively use Quick Investigation or Deep Investigation from any STAROps entry point, credits will be consumed.
When you manually click Alert Analysis after receiving an alert, credits will be consumed.
If you have enabled Automatic Root Cause Analysis for alert rules in CloudMonitor 2.0 - Alert Center, credits will also be consumed automatically when an alert is triggered and analyzed. If you no longer need this feature, please disable it before the official billing starts.