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

Problems with TokenHub detected in Guangzhou

Reported by Tencent Cloud · Cloud & Infrastructure · source last read 3 min ago

Official source (opens in a new tab)
Vendor start
Nov 3, 2026, 09:03 UTC
Vendor's clock
Resolved
Nov 3, 2026, 10:35 UTC
Vendor's clock
First seen by Statuswall
Nov 11, 2026, 02:42 UTC
Statuswall's clock
Duration
1 h 31 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

  • Tencent Cloud reports degraded: "Problems with TokenHub detected in Guangzhou".[E1, E2]
  • The vendor marked it resolved at 2026-11-03 10:35 UTC.[E3, E7]

Affected products and regions

  • Regions: ap-guangzhou.[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 a1be9bd185e78065

Evidence (8)
  1. E1Tencent Cloud reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "Problems with TokenHub detected in Guangzhou". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor-reported start: 2026-11-03 09:03 UTC. (vendor) source (opens in a new tab)
  5. E5Regions stated by the vendor: ap-guangzhou. (vendor) source (opens in a new tab)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-11-03 10:35 UTC. (vendor) source (opens in a new tab)
  8. E8First seen by Statuswall: 2026-11-11 02:42 UTC. (Statuswall)

Affected scope

ap-guangzhou

Components: not stated by the vendor

From the vendor's structured data.

Potential relevance

Tencent 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. Nov 3, 2026, 09:03 UTCVendor-reported startVendor time
  2. Nov 3, 2026, 10:35 UTCVendor-reported resolutionVendor time
  3. Nov 11, 2026, 02:42 UTCFirst seen by Statuswall (vendor status: resolved)Seen by Statuswall