Is the QwenCloud API down? Live status, latency & uptime by region
· rebuilt about every 30 minutes
Is the QwenCloud API down right now?
Reachable from all 4 regions
Last successful probe Nov 8, 10:45 UTC · every 5 minutes from 4 region(s)
Every probe from every region reached the qwencloud API successfully in the last 72 hours. Measured from outside qwencloud’s own network, independently of its status page; full log: measured AI API incidents.
Real requests: not measured for QwenCloud — only the API host is probed here, so errors limited to specific models are invisible to these probes. That is exactly what a status page tends to report, hence the line below.
QwenCloud publishes no machine-readable status page, so there is nothing to cross-check against.
As of November 08, 2026, the qwencloud AI API responds in 155 ms p50 (edge, time-to-first-byte) from Asia (Tokyo) — its fastest measured region — with 100% uptime. Slowest is South America (Santiago) at 732 ms p50.
Measured since November 8, 2026; there is no history before that date (details).
Endpoint response (TTFB), 24 h
155 ms
Typical (p50) from Asia (Tokyo), the fastest region
Uptime, 24 h
100%
56 probes across 4 region(s)
Failed probes, 72 h
0
of 56 probes, all regions
Reported by QwenCloud, 72 h
—
no machine-readable status page
Was QwenCloud down in the last 3 days?
No. All 56 probes from 4 region(s) reached the qwencloud API in the last 72 hours.
QwenCloud publishes no machine-readable status page, so there is nothing to set against the measurements above.
Is QwenCloud getting faster or slower?
Endpoint response (TTFB) · milliseconds · lower is faster
Last 72 hours · UTC · newest time on the right · current hour is incomplete.
Each line shows a region’s typical response per hour (p50), using the same scale. A gap means no successful timed probe in that hour.
typical response per hour (p50)all probes succeededsome failed (under half)half or more failedno probes recorded
Probe counts by region
Europe (Germany): 0 failed / 14 endpoint probes · 70 hour(s) without dataUS (Central): 0 failed / 14 endpoint probes · 70 hour(s) without dataAsia (Tokyo): 0 failed / 14 endpoint probes · 70 hour(s) without dataSouth America (Santiago): 0 failed / 14 endpoint probes · 70 hour(s) without data
Chart details
The strip shows endpoint probe outcomes, not model-request success. Adjacent hours with all successes or no data are joined. Hover an hour for its recorded values.
Latest is the most recent hourly p50 with data. Median is the median of hourly p50 values over these 72 hours. The “slower than usual” label means latest is at least 25% above that median; it is a relative change, not a fixed speed rating.
How fast is the QwenCloud API from each region?
Endpoint response (TTFB) · last 24 hours · milliseconds (ms) · lower is faster.
How to read these metrics
Endpoint response (TTFB)Network connection and the first response byte, without model inference.
Typical · p5050% of successful timed samples finish within this time.
Slower · p9595% of successful timed samples finish within this time.
Region
Typical (p50 TTFB)
Slower (p95)
Uptime
Asia (Tokyo)
155 ms
173 ms
100%
Europe (Germany)
355 ms
361 ms
100%
South America (Santiago)
732 ms
750 ms
100%
US (Central)
415 ms
428 ms
100%
Measured from Asia (Tokyo), qwencloud responds in 155 ms; from South America (Santiago) the same API takes 732 ms — 4.7× longer for an identical request. That difference is the network path, not the model, and it applies to every call you make.
What is actually being measured here?
A probe in each region opens a real connection to qwencloud’s own API host every five
minutes and times DNS resolution, the TCP handshake, the TLS handshake and the first byte of the
response. Nothing is routed through a gateway or aggregator, so these figures describe
qwencloud’s infrastructure rather than a reseller’s. Uptime counts a probe as failed only when the
service genuinely fails — a 401 from an unauthenticated probe means the endpoint answered
correctly and is counted as up, while a 410 Gone means the API has been shut down and is counted as
neither (rule).
Measured since November 8, 2026. Since November 8, 2026 the probes measure ap-southeast-1.maas.qwencloudapi.com/compatible-mode/v1/models; there is no history before that date. QwenCloud (qwencloud.com) is a separate Alibaba platform with its own accounts, console and API keys, not Alibaba Cloud Model Studio and its DashScope endpoint. The qwen API at dashscope-intl.aliyuncs.com is a separate series with its own page. Source: https://docs.qwencloud.com/developer-guides/getting-started/regions, checked November 8, 2026.
What this page does not tell you
These are edge latency numbers: the time before the model begins generating. They
say nothing about answer quality, throughput, price, or how long a full completion takes — those
depend on the model you call. Edge latency matters because it is unavoidable: it is paid on every
request, before a single token exists, and no prompt engineering removes it. Where an API key is
available, inference time-to-first-token is measured separately and shown on the region pages with the
model named next to the figure. Likewise, an unauthenticated probe cannot see errors that hit only some
models or some accounts — the kind a status page usually reports — which is why QwenCloud’s
own reports are shown next to the measurements rather than folded into them.
— embed code