Status / Qwen (Alibaba Cloud)
Q Live monitoring · checked every 2 minutes · last check 38s ago
Is 通义千问 down? Qwen (Alibaba Cloud) status right now
No, 通义千问 is up and working normally.
Operational Current status
100% Uptime 24h
100% Uptime 30 days
1931 ms API response time
Last 24 hours 05:03 UTC · 0 checks · 0 failed · avg — 05:33 UTC · 0 checks · 0 failed · avg — 06:03 UTC · 0 checks · 0 failed · avg — 06:33 UTC · 0 checks · 0 failed · avg — 07:03 UTC · 0 checks · 0 failed · avg — 07:33 UTC · 0 checks · 0 failed · avg — 08:03 UTC · 0 checks · 0 failed · avg — 08:33 UTC · 0 checks · 0 failed · avg — 09:03 UTC · 0 checks · 0 failed · avg — 09:33 UTC · 0 checks · 0 failed · avg — 10:03 UTC · 0 checks · 0 failed · avg — 10:33 UTC · 0 checks · 0 failed · avg — 11:03 UTC · 0 checks · 0 failed · avg — 11:33 UTC · 0 checks · 0 failed · avg — 12:03 UTC · 0 checks · 0 failed · avg — 12:33 UTC · 0 checks · 0 failed · avg — 13:03 UTC · 0 checks · 0 failed · avg — 13:33 UTC · 0 checks · 0 failed · avg — 14:03 UTC · 0 checks · 0 failed · avg — 14:33 UTC · 0 checks · 0 failed · avg — 15:03 UTC · 0 checks · 0 failed · avg — 15:33 UTC · 0 checks · 0 failed · avg — 16:03 UTC · 0 checks · 0 failed · avg — 16:33 UTC · 0 checks · 0 failed · avg — 17:03 UTC · 0 checks · 0 failed · avg — 17:33 UTC · 0 checks · 0 failed · avg — 18:03 UTC · 0 checks · 0 failed · avg — 18:33 UTC · 0 checks · 0 failed · avg — 19:03 UTC · 0 checks · 0 failed · avg — 19:33 UTC · 0 checks · 0 failed · avg — 20:03 UTC · 0 checks · 0 failed · avg — 20:33 UTC · 0 checks · 0 failed · avg — 21:03 UTC · 0 checks · 0 failed · avg — 21:33 UTC · 0 checks · 0 failed · avg — 22:03 UTC · 0 checks · 0 failed · avg — 22:33 UTC · 0 checks · 0 failed · avg — 23:03 UTC · 0 checks · 0 failed · avg — 23:33 UTC · 0 checks · 0 failed · avg — 00:03 UTC · 0 checks · 0 failed · avg — 00:33 UTC · 0 checks · 0 failed · avg — 01:03 UTC · 0 checks · 0 failed · avg — 01:33 UTC · 0 checks · 0 failed · avg — 02:03 UTC · 0 checks · 0 failed · avg — 02:33 UTC · 1 checks · 0 failed · avg 855 ms 03:03 UTC · 15 checks · 0 failed · avg 480 ms 03:33 UTC · 15 checks · 0 failed · avg 377 ms 04:03 UTC · 15 checks · 0 failed · avg 415 ms 04:33 UTC · 15 checks · 0 failed · avg 632 ms 24h ago now
API response time (24h) 0 1110 2221 p50 298 ms · p95 1007 ms (ms, UTC)
90-day uptime history 2026-06-27: no data 2026-06-28: no data 2026-06-29: no data 2026-06-30: no data 2026-07-01: no data 2026-07-02: no data 2026-07-03: no data 2026-07-04: no data 2026-07-05: no data 2026-07-06: no data 2026-07-07: no data 2026-07-08: no data 2026-07-09: no data 2026-07-10: no data 2026-07-11: no data 2026-07-12: no data 2026-07-13: no data 2026-07-14: no data 2026-07-15: no data 2026-07-16: no data 2026-07-17: no data 2026-07-18: no data 2026-07-19: no data 2026-07-20: no data 2026-07-21: no data 2026-07-22: no data 2026-07-23: no data 2026-07-24: no data 2026-07-25: no data 2026-07-26: no data 2026-07-27: no data 2026-07-28: no data 2026-07-29: no data 2026-07-30: no data 2026-07-31: no data 2026-08-01: no data 2026-08-02: no data 2026-08-03: no data 2026-08-04: no data 2026-08-05: no data 2026-08-06: no data 2026-08-07: no data 2026-08-08: no data 2026-08-09: no data 2026-08-10: no data 2026-08-11: no data 2026-08-12: no data 2026-08-13: no data 2026-08-14: no data 2026-08-15: no data 2026-08-16: no data 2026-08-17: no data 2026-08-18: no data 2026-08-19: no data 2026-08-20: no data 2026-08-21: no data 2026-08-22: no data 2026-08-23: no data 2026-08-24: no data 2026-08-25: no data 2026-08-26: no data 2026-08-27: no data 2026-08-28: no data 2026-08-29: no data 2026-08-30: no data 2026-08-31: no data 2026-09-01: no data 2026-09-02: no data 2026-09-03: no data 2026-09-04: no data 2026-09-05: no data 2026-09-06: no data 2026-09-07: no data 2026-09-08: no data 2026-09-09: no data 2026-09-10: no data 2026-09-11: no data 2026-09-12: no data 2026-09-13: no data 2026-09-14: no data 2026-09-15: no data 2026-09-16: no data 2026-09-17: no data 2026-09-18: no data 2026-09-19: no data 2026-09-20: no data 2026-09-21: no data 2026-09-22: no data 2026-09-23: no data 2026-09-24: 100.00% up · 0 failed / 61 checks 90 days ago 100% uptime today
Incident history Alibaba does not publish a machine-readable status page. Outages are detected by ModelBank’s own probes (see the 90-day history above).
FAQ Is 通义千问 down? No, 通义千问 is up and working normally. ModelBank checks Qwen (Alibaba Cloud) every 2 minutes from Cloudflare’s global network. Last check: 38s ago.
What is 通义千问’s uptime? Measured by ModelBank: 100% in the last 24 hours, 100% over 30 days and 100% over 90 days.
What should I do if 通义千问 is not working? First check this page and the official status page. If 通义千问 is up for everyone else, try clearing cache, logging out and in, switching network, or checking your API key and rate limits (HTTP 429). If it is a real outage, switch to an alternative model — see the alternatives on this page — or use a router with automatic failover.
Having problems with 通义千问? 0 reports in the last hour · 0 in 24h
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Signals
Our API probe API responded HTTP 401 in 1931 ms
Official status not published
Status since 2h ago
Alibaba models USD per 1M input / output tokens
Alternatives if it’s down
Embed this status [](https://modelbank.ai/status/qwen)
Get notified when 通义千问 goes down We’ll email you the moment ModelBank detects a 通义千问 outage, and again when it recovers.