Error 502: what to do when mimo-v2.5 fails

A 502 means the gateway received an invalid response from the upstream model service: the request reached the gateway, but the hop to the upstream failed.

502 Bad Gateway means the gateway received an invalid response from the upstream model service. The request reached the gateway; the failure happened on the hop from gateway to upstream, usually due to an upstream restart or a dropped connection.

mimo-v2.5 is served by Xiaomi. 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 service is unavailable or returned a malformed response. The recommended first action is: Retry once — 502s are usually transient.

Common causes

  • The upstream model service is unavailable or returned a malformed response
  • An upstream node is restarting
  • The gateway-to-upstream connection was interrupted
  • The model was temporarily taken offline

How to fix

  • Retry once — 502s are usually transient
  • Switch to an equivalent model from another vendor
  • If only one model keeps returning 502, its upstream is unhealthy
  • Try again later or contact us

Retry with exponential backoff

The snippet below retries when mimo-v2.5 returns 502, 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 = 'mimo-v2.5'


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
VendorXiaomi
Context1M
CapabilitiesReasoning, Tools, Files, Open Weights, Vision, Audio
API formatsopenai, openai-response, openai-response-compact, anthropic, gemini, openai-alpha-search
Billing formulap * 0.14 + cr * 0.0028 + c * 0.28

FAQ

How many retry attempts is reasonable?

You usually do not need to change business code, just the call cadence. Retrying is the most effective first step. With billing p * 0.14 + cr * 0.0028 + c * 0.28, failed requests are not counted toward usage. Set the retry ceiling to 3–5 attempts and add jitter. Use exponential backoff for retryable errors and return immediately for the rest.

How should I monitor 502 in production?

Group the errors by time and node first; the pattern is usually obvious once you do. Keep the request ID and the raw response body, otherwise nothing can be traced. This model is served by Xiaomi, so upstream status follows the vendor’s own announcements. Reproduce it once in a staging environment with the same request body.

Is 502 related to the capability of the model itself?

It is usually transient and recovers on its own. The capability tags for this model are Reasoning, Tools, Files, Open Weights, Vision, Audio. If it persists for several minutes, contact platform support to confirm upstream status. Decide account-level versus model-level first; the two need completely different handling.

Is 502 on mimo-v2.5 related to request body size?

This is a client-side configuration issue; nothing changes server-side. The 1M context window sets the maximum input per request; anything beyond it is rejected outright. Truncate or summarise long inputs — it noticeably reduces 502.

Other errors on this model

Other models with the same error

Back to the model page

Data updated: 2026-10-10 08:15

Technical SupportLive Support
Back to Top