Huawei Cloud CEO Zhou Yu Feng announced at the Huawei Connect 2026 event plans for the commercial launch of a cloud service based on the Ascend 950 Lingqu cluster. The launch in China is scheduled for September 30, and access for the global market will open on November 30.
These dates define the timeline for Ascend 950 compute SKUs and do not merely describe the SuperPoD architecture. Customers will be able to reserve a cluster connected via UnifiedBus consisting of 1024 cards as a managed cloud offering according to the published schedule.
Huawei stated that the Ascend 950 system utilizes its UnifiedBus interconnect, marketed as Lingqu, to assemble a cluster of 1024 accelerators. This cluster is capable of providing up to 1 EFLOPS of computation in FP8 format and 2 EFLOPS in FP4 format, and also features 256 TB of unified memory available globally.
The design is engineered to support end-to-end training of large models without the need for additional cluster partitioning or adaptation, maintaining thousand-card job execution within a single memory address space.
The commercial window for cloud services fits into a broader Ascend development roadmap presented at the same event. Chairman Wang Tao noted that over 1000 Ascend supernodes have already been deployed, and Ascend 950 supernodes have entered a phase of scalable commercial use.
Furthermore, the Ascend 960DT is planned for release in the first quarter of 2027, and the Ascend 960PR in the third quarter, with a stated release pace of approximately one major Ascend generation annually, including long-term stages 970 and 980.
For potential buyers, the key information is the specific calendar with the launch first in China and then globally, as well as the cluster specification: 1024 cards, EFLOPS class throughput (FP8/FP4), and 256 TB of unified memory via UnifiedBus. Huawei Cloud positions Ascend 950 Lingqu as a ready-to-use AI cluster service, rather than a theoretical architecture, offering internal availability at the end of September and international availability two months later for teams needing supernode-scale training without building the infrastructure themselves.


