Use cases
Software Products E-commerce MSPs Schools Development & Marketing DevOps Agencies Help Desk
Company
Internet Status Blog Pricing Log in Get started free

Alibaba Cloud Outage History

Every past Alibaba Cloud outage tracked by IsDown, with detection times, duration, and resolution details.

There were 13 Alibaba Cloud outages since December 2022. The 6 outages from the last 12 months are summarized below, with incident details, duration, and resolution information.

Major April 21, 2026

April 2026: Partial Cloud Service Disruption in Korea (Seoul) Zone B

Detected Apr 21, 2026 6:26 PM EDT · Resolved Apr 21, 2026 6:30 PM EDT · Duration 4 minutes

A cooling system anomaly at Alibaba Cloud's Korea Zone B data center caused disruptions to Elastic Compute Service (ECS), Apsara File Storage NAS, and Elastic Block Storage (EBS) services. Engineers executed emergency shutdown procedures to protect affected cloud products and began migration operations. The cooling system was progressively restored, power was recovered, and cloud services underwent phased restoration.

Major April 20, 2026

April 2026: 【异常(处理中)】杭州、上海地域实时计算Flink管控服务异常

Detected Apr 20, 2026 4:34 AM EDT · Resolved Apr 20, 2026 4:37 AM EDT · Duration 4 minutes

Alibaba Cloud experienced an anomaly with Realtime Compute for Apache Flink management services in the Hangzhou and Shanghai regions, affecting console access and OpenAPI calls while job execution remained unimpacted. The incident also caused monitoring display and alert issues for some cloud database and network products, though instance operations continued normally. The 4-minute incident was actively addressed by Alibaba Cloud engineers.

Major March 20, 2026

March 2026: Zone B Indonesia (Jakarta) Abnormality in Network Access

Detected Mar 20, 2026 8:19 AM EDT · Resolved Mar 20, 2026 8:23 AM EDT · Duration 4 minutes

On March 20, 2026, Alibaba Cloud experienced a network access abnormality in Zone B of the Indonesia (Jakarta) region affecting cross-domain and cross-zone public network connectivity. The incident impacted multiple services including ECS, OSS, SLB, EIP, PolarDB, AnalyticDB for MySQL, and Lindorm for approximately 4 minutes. Engineers intervened and fully recovered the affected devices, with ECS services being progressively restored afterward.