Error 503: what to do when qwen-turbo fails

A 503 means the service is temporarily unavailable, usually due to maintenance or overload. Unlike 429, it is not about your quota — it is a capacity problem on the server side.

503 Service Unavailable means the service cannot handle the request right now, usually from overload or maintenance. The distinction from 429 matters: 429 means your quota is used up, 503 means server capacity is short. Increase the backoff interval rather than swapping keys.

qwen-turbo is served by Alibaba. Everything on this page — triggers, fixes and measured data — is compiled from the real runtime behaviour of this model at the gateway layer.

At this gateway, the most common trigger is: The upstream model is overloaded. The recommended first action is: Retry later with a longer backoff.

Common causes

  • The upstream model is overloaded
  • The service is under maintenance or rolling out
  • The node in your region is unavailable
  • A sudden traffic spike

How to fix

  • Retry later with a longer backoff
  • Switch to a less loaded equivalent model
  • Avoid batch jobs during peak hours
  • Watch our announcements

Retry with exponential backoff

The snippet below retries when qwen-turbo returns 503, up to 5 attempts, with an increasing wait plus random jitter so concurrent calls do not retry in lockstep. Read the base URL and API key from environment variables — never hardcode them.

import os, time, random
import requests

BASE  = os.getenv("OPENAI_BASE_URL")   # e.g. https://<your-gateway>/v1
KEY   = os.getenv("OPENAI_API_KEY")
MODEL = 'qwen-turbo'


def chat(messages, retries=5):
    """Retry with exponential backoff + jitter."""
    for i in range(retries):
        try:
            r = requests.post(
                BASE + "/chat/completions",
                headers={"Authorization": "Bearer " + KEY},
                json={"model": MODEL, "messages": messages, "stream": True},
                timeout=60,
            )
            if r.status_code == 429 or r.status_code >= 500:
                time.sleep(min(2 ** i + random.uniform(0, 1), 30))
                continue
            r.raise_for_status()
            return r.json()
        except requests.exceptions.Timeout:
            time.sleep(min(2 ** i + random.uniform(0, 1), 30))
    raise RuntimeError("gave up after " + str(retries) + " retries")


print(chat([{"role": "user", "content": "hello"}]))

Key facts for this model

API endpointhttps://api.airai.cc/v1
OpenAI-compatibleOpenAI-compatible
VendorAlibaba
Context1M
CapabilitiesReasoning, Tools
API formatsopenai, openai-response, openai-response-compact, anthropic, gemini, openai-alpha-search
Billing formulap * 0.05 + c * 0.5) : tier("standard", p * 0.05 + c * 0.2

FAQ

Do I need to upgrade my plan to fix 503 on qwen-turbo?

It is mainly a quota matter, not a fault in the model itself. With billing p * 0.05 + c * 0.5) : tier("standard", p * 0.05 + c * 0.2, the cost of long output comes mostly from output tokens. Check your balance and rate limits in the console before debugging code. When estimating cost from p * 0.05 + c * 0.5) : tier("standard", p * 0.05 + c * 0.2, include the retry budget.

Do failed requests count against my rate limit quota?

No charge — only output actually produced counts toward usage. Only the output already produced is billed; the failed part is not. Billing follows p * 0.05 + c * 0.5) : tier("standard", p * 0.05 + c * 0.2, so no output means no charge. Input price is about $0.05 per million tokens. Check your balance and rate limits in the console before debugging code. When estimating cost from p * 0.05 + c * 0.5) : tier("standard", p * 0.05 + c * 0.2, include the retry budget.

Which status codes are worth retrying, and which never help?

You usually do not need to change business code, just the call cadence. Retrying is the most effective first step. With billing p * 0.05 + c * 0.5) : tier("standard", p * 0.05 + c * 0.2, failed requests are not counted toward usage. Set the retry ceiling to 3–5 attempts and add jitter.

Is incomplete output from qwen-turbo the same thing as 503?

Group the errors by time and node first; the pattern is usually obvious once you do. If it only happens in production, it is usually an environment difference, not the model. This model is served by Alibaba, so upstream status follows the vendor’s own announcements. Log the request ID on every failure — it beats the status code when debugging. Reproduce it once in a staging environment with the same request body.

Other errors on this model

Other models with the same error

Back to the model page

Data updated: 2026-10-10 15:50

Technical SupportLive Support
Back to Top