litellm - ✅(Solved) Fix [Bug]: deepseek-v3.2-maas is global on vertex [1 pull requests, 1 comments, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
BerriAI/litellm#23859Fetched 2026-04-08 00:54:20
View on GitHub
Comments
1
Participants
1
Timeline
7
Reactions
0
Author
Participants
Timeline (top)
labeled ×3closed ×1commented ×1cross-referenced ×1

Error Message

Error fetching response:Error: 404 litellm.NotFoundError: Vertex_aiException - [{ "error": { "code": 404, "message": "Publisher Model projects/*******/locations/us-west2/publishers/deepseek-ai/models/deepseek-v3.2-maas was not found or your project does not have access to it. Please ensure you are using a valid model version. For more information, see: https://cloud.google.com/vertex-ai/generative-ai/docs/learn/model-versions", "status": "NOT_FOUND" } } ]. Received Model Group=deepseek-ai/deepseek-v3.2-maas Available Model Group Fallbacks=None

Fix Action

Fixed

PR fix notes

PR #23864: fix(model-prices): correct supported_regions for Vertex AI DeepSeek models

Description (problem / solution / changelog)

Relevant issues

Fixes https://github.com/BerriAI/litellm/issues/23859

Pre-Submission checklist

  • I have Added testing in the tests/test_litellm/ directory, Adding at least 1 test is a hard requirement - N/A, data-only change to model pricing JSON
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem

Type

🐛 Bug Fix

Changes

The supported_regions for Vertex AI DeepSeek models were incorrect, causing 404 errors when calling deepseek-v3.2-maas (routed to us-west2 instead of global).

Updated per Google Cloud official docs:

ModelBeforeAfter
deepseek-v3.2-maasus-west2global
deepseek-v3.1-maasus-west2us-central1
deepseek-r1-0528-maas(missing)us-central1
deepseek-ocr-maas(missing)us-central1

Changed files

  • model_prices_and_context_window.json (modified, +9/-3)

Code Example

Error fetching response:Error: 404 litellm.NotFoundError: Vertex_aiException - [{
"error": {
"code": 404,
"message": "Publisher Model projects/*******/locations/us-west2/publishers/deepseek-ai/models/deepseek-v3.2-maas was not found or your project does not have access to it. Please ensure you are using a valid model version. For more information, see: https://cloud.google.com/vertex-ai/generative-ai/docs/learn/model-versions",
"status": "NOT_FOUND"
}
}
]. Received Model Group=deepseek-ai/deepseek-v3.2-maas
Available Model Group Fallbacks=None
RAW_BUFFERClick to expand / collapse

Check for existing issues

  • I have searched the existing issues and checked that my issue is not a duplicate.

What happened?

A bug happened!

<img width="2127" height="897" alt="Image" src="https://github.com/user-attachments/assets/c24e9197-a920-419e-9c53-45c3e56dab58" /> <img width="1001" height="659" alt="Image" src="https://github.com/user-attachments/assets/3e607c67-64c3-4d90-8845-2b484ea73e45" />

Steps to Reproduce

  1. input a vialid vertex json
  2. vertex_ai/deepseek-ai/deepseek-v3.2-maas

Relevant log output

Error fetching response:Error: 404 litellm.NotFoundError: Vertex_aiException - [{
"error": {
"code": 404,
"message": "Publisher Model projects/*******/locations/us-west2/publishers/deepseek-ai/models/deepseek-v3.2-maas was not found or your project does not have access to it. Please ensure you are using a valid model version. For more information, see: https://cloud.google.com/vertex-ai/generative-ai/docs/learn/model-versions",
"status": "NOT_FOUND"
}
}
]. Received Model Group=deepseek-ai/deepseek-v3.2-maas
Available Model Group Fallbacks=None

What part of LiteLLM is this about?

Proxy

What LiteLLM version are you on ?

v1.82.3

Twitter / LinkedIn details

No response

extent analysis

Fix Plan

The fix involves handling the NotFoundError exception when the specified model version is not found.

  • Check if the model version exists before attempting to use it.
  • If the model version does not exist, either use a default model version or prompt the user to select a valid model version.
  • Update the code to handle the NotFoundError exception and provide a meaningful error message.

Example code snippet:

try:
    # Attempt to use the specified model version
    model_version = "deepseek-v3.2-maas"
    # Code to use the model version
except litellm.NotFoundError as e:
    # Handle the NotFoundError exception
    print(f"Model version {model_version} not found. Please ensure you are using a valid model version.")
    # Either use a default model version or prompt the user to select a valid model version
    default_model_version = "default-model-version"
    # Code to use the default model version

Verification

To verify that the fix worked, test the code with a valid model version and an invalid model version. The code should handle the NotFoundError exception and provide a meaningful error message when an invalid model version is used.

Extra Tips

  • Ensure that the model version exists and is accessible before attempting to use it.
  • Handle exceptions properly to prevent crashes and provide meaningful error messages.
  • Consider implementing a fallback mechanism to use a default model version when the specified model version is not found.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING