Vendor reports: degradedResolved · vendor status “resolved”Official status API

Anomaly in Realtime Compute for Apache Flink Management Service in China (Hangzhou) and China (Shanghai) Regions

Reported by Alibaba Cloud · Cloud & Infrastructure · source last read 4 min ago

Official source (opens in a new tab)
Vendor start
Apr 20, 2026, 07:13 UTC
Vendor's clock
Resolved
Apr 20, 2026, 08:25 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 02:42 UTC
Statuswall's clock
Duration
1 h 12 min
From vendor start and resolution

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • Alibaba Cloud reports degraded: "Anomaly in Realtime Compute for Apache Flink Management Service in China (Hangzhou) and China (Shanghai) Regions".[E1, E2]
  • The vendor marked it resolved at 2026-04-20 08:25 UTC.[E3, E7]

Affected products and regions

  • Regions: cn-shanghai, cn-hangzhou.[E5]

What is unknown

  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-11-11 02:42 UTC · summary s1, evidence 10090007d4e8718d

Evidence (8)
  1. E1Alibaba Cloud reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Anomaly in Realtime Compute for Apache Flink Management Service in China (Hangzhou) and China (Shanghai) Regions". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-04-20 07:13 UTC. (vendor) source (opens in a new tab)
  5. E5Regions stated by the vendor: cn-shanghai, cn-hangzhou. (vendor) source (opens in a new tab)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-04-20 08:25 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 02:42 UTC. (Statuswall)

Affected scope

cn-shanghai, cn-hangzhou

Components: not stated by the vendor

From the vendor's structured data.

Potential relevance

Alibaba Cloud is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Apr 20, 2026, 07:13 UTCVendor-reported startVendor time
  2. Apr 20, 2026, 08:25 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:42 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall