Qwen Turbo Status, Model IDs and Migration Guide

Last verified: August 4, 2026. Hosted lifecycle notice (route-specific): Alibaba Cloud’s Bailian / China Model Studio lifecycle page schedules the hosted IDs qwen-turbo and qwen-turbo-realtime for decommissioning on October 10, 2026. Its replacement guidance is the latest Qwen 3.7 and 3.6 models rather than one named one-to-one successor.

QwenCloud international has a different documented status. Its Marketplace card and text-model matrix still listed qwen-turbo as a Legacy model on August 4, 2026, while QwenCloud’s own deprecation table did not include Turbo. We did not find qwen-turbo-realtime in the current QwenCloud international text-model matrix. Confirm the provider, deployment scope, endpoint, key, and account notice before migrating; the Bailian notice is not a universal QwenCloud or provider-wide retirement.

For the affected Bailian / China Model Studio route, the lifecycle policy says the APIs remain functional before the deadline, although QPM and TPM may be reduced during the notice period. From the official decommissioning time, inference calls to those hosted IDs fail. This page reports a documentation review, not a successful live request.

Qwen Turbo current status

Exact ID	Bailian / China Model Studio	QwenCloud international at August 4, 2026	Safe action
qwen-turbo	Bailian / China Model Studio schedules decommissioning on October 10, 2026	Still listed as Legacy in the text-model matrix and exposed by its Marketplace card; Turbo is absent from QwenCloud’s current deprecation table	Stop new Bailian deployments, test an appropriate current Qwen 3.7 or 3.6 model for that workload, and verify the international account separately
qwen-turbo-realtime	Bailian / China Model Studio schedules decommissioning on October 10, 2026	No current international QwenCloud listing was verified; no availability claim is made	Check the exact realtime product, endpoint, event flow, deployment scope, and account notice; do not assume a one-to-one replacement
qwen-turbo-latest, qwen-turbo-2025-07-15, qwen-turbo-2025-04-28, qwen-turbo-2025-02-11, qwen-turbo-2024-11-01, and qwen-turbo-1101	The current Bailian / China Model Studio lifecycle table lists these snapshots as offline	No cross-route availability conclusion was drawn from the Bailian table	Remove them from Bailian primary and fallback configurations; do not describe them as currently callable without a dated, authenticated route-specific test
qwen-turbo-2024-09-19 and qwen-turbo-2024-06-24	The Bailian / China Model Studio lifecycle table records retirement on January 30, 2026	No cross-route availability conclusion was drawn	Remove them from affected Bailian configurations and fallbacks

Historical release notes can explain how a rolling alias behaved at an earlier date, but they do not override the current lifecycle table for the route being used. The Bailian table now lists qwen-turbo-2025-04-28 and several later Turbo snapshots as offline, while QwenCloud international still documents the separate qwen-turbo service as Legacy. Keep those provider paths separate.

Capabilities documented for the legacy family

• Modality: text generation; the current visual-model list does not include Qwen Turbo.
• Alibaba Cloud Model Studio legacy route: qwen-turbo is listed with a 1M context window and support for Function Calling, built-in tools, and structured output.
• Thinking: hybrid thinking, disabled by default for the Turbo series.
• QwenCloud international legacy route: qwen-turbo is listed with a 128K context window, 16K maximum output, Function Calling, and structured output; built-in tools are not listed. The dated qwen-turbo-2024-11-01 row, not the current rolling qwen-turbo row, is the 1M entry in the QwenCloud matrix.
• Current pricing regions: Singapore for International deployment and Beijing for Chinese-mainland deployment.

These are service features, not evidence of a fixed downloadable architecture. The rolling mainline can change, so record the request date and pin an available dated snapshot when reproducibility matters.

Is Qwen Turbo a 14B model or a downloadable checkpoint?

Alibaba documents Qwen Turbo as a managed API service and does not publish current Turbo weights or a current public parameter count. Claims that the hosted ID is exactly a 14B checkpoint, a specific Mixture-of-Experts configuration, or a downloadable Qwen-14B variant are not supported by the current product documentation.

Open Qwen checkpoints can be self-hosted, but they are separate models. Do not substitute one into a Turbo article without naming its exact checkpoint, license, context, and test conditions. If local deployment is the goal, use the Qwen download guide.

What should replace Qwen Turbo?

For the Bailian / China Model Studio IDs covered by the October 10, 2026 notice, Alibaba recommends the latest Qwen 3.7 and 3.6 models. The notice does not designate one exact, behaviorally identical successor for both Turbo routes. Choose a candidate only after fixing the provider, deployment scope, endpoint family, modality, latency target, and cost limit.

Existing workload	Candidate direction	What must be retested
Bailian / China Model Studio text generation or tool use	Compare currently documented Qwen 3.7 and 3.6 models in the same deployment scope; the lifecycle notice names a series, not one formal successor ID	Answer quality, Thinking defaults, function calls, structured output, context tiers, rate limits, latency, and list price
Bailian qwen-turbo-realtime	Choose a currently supported realtime route for the required modality and scope; no one-to-one realtime replacement is named	WebSocket or streaming endpoint, authentication, client and server events, media formats, interruption handling, latency, quotas, and billing
QwenCloud international qwen-turbo	Treat it as a separate Legacy service and use QwenCloud’s current selector when planning new work	QwenCloud key, base URL, exact ID, availability, protocol, limits, deprecation table, and effective price

qwen3.7-flash on QwenCloud and qwen3.6-flash on Model Studio are route-specific evaluation candidates, not interchangeable aliases and not documented as a universal one-line replacement for qwen-turbo-realtime.

Migration checklist

1. Complete the Bailian / China Model Studio production cutover before October 10, 2026; do not rely on a fallback that still points to qwen-turbo or qwen-turbo-realtime on that route.
2. Search application configuration, environment variables, gateways, scheduled jobs, evaluation scripts, dashboards, and retry or fallback chains for both exact IDs.
3. Inventory every exact model ID, provider, deployment scope, region, base URL, protocol, and Thinking setting. For realtime clients, also record the socket endpoint, event schema, input and output formats, voice or modality settings, and reconnect behavior.
4. Remove snapshots that the Bailian / China Model Studio lifecycle table lists as offline or retired from affected code and fallback lists.
5. Run the old and candidate model on the same permission-cleared prompts in the same route and scope where possible.
6. Test final-answer quality, Thinking behavior, tool calls, structured JSON, long prompts, streaming, rate limits, and error handling.
7. Use current provider list pricing, separately dated promotions, and measured token usage; do not infer “cheapest” or “fastest” from the Turbo or Flash name.
8. For latency, use warm-ups and repeated trials, then report median and P95 with the date and output cap.
9. Pin a dated snapshot when repeatability is more important than rolling improvements and that exact route still offers it.

Verification status and test limits

We checked the Bailian / China Model Studio lifecycle table and official notice, QwenCloud Marketplace card, QwenCloud text-model matrix, QwenCloud deprecation table, and provider pricing documentation on August 4, 2026. This was a documentation review. No authenticated request to qwen-turbo, qwen-turbo-realtime, or a proposed replacement was completed, so this page reports no independent availability, output, latency, throughput, cost, or quality result.

Before a production migration, make a small paid request in your own eligible workspace without exposing the key. Record the HTTP status, request ID, usage, region, exact model ID, snapshot, thinking setting, and timestamp. Compare current families in the Qwen models directory and read the Qwen Flash guide before choosing the replacement.

Official sources

• Alibaba Cloud Bailian / China Model Studio lifecycle table
• Alibaba Cloud official Qwen Turbo decommissioning notice
• QwenCloud international qwen-turbo Marketplace card
• QwenCloud international text-model matrix
• QwenCloud international model-deprecation table
• Alibaba Cloud Model Studio text-generation model matrix
• Alibaba Cloud Model Studio list pricing and discounts