Vertex AI
deepseek-v3.1-maas model retirement
Stopped workingSubscribe to Vertex AIShare
On October 21, 2026, the model deepseek-v3.1-maas reached retirement on Vertex AI. Requests targeting this model fail since that date. The deprecation was initially announced on July 21, 2026.
The error you get
What Vertex AI answers a call to deepseek-v3.1-maas once the model is gone, as recorded from real responses:
{"error":{"code":404,"message":"Publisher model `projects/{project}/locations/{region}/publishers/google/models/deepseek-v3.1-maas` was not found or your project does not have access to it. Ensure you are using a valid model name and that the model is available in the specified region.","status":"NOT_FOUND"}}What to use instead of deepseek-v3.1-maas
Self-deploy DeepSeek-V3.1 on Model Garden.
In Vertex AI's words
Model ID: deepseek-v3.1-maas; Deprecation date: July 21, 2026; Retirement date: October 21, 2026; Self-deploy alternative: Self-deploy DeepSeek-V3.1 on Model Garden
Facts
- API
- Vertex AI
aiplatform.googleapis.com - Model
deepseek-v3.1-maas- Released
- August 28, 2025 (models.dev)
- Kind
- Model retirement
- Announced
- July 21, 2026
- Takes effect
- October 21, 2026
- Calls after that day
- Fail
- Source
- Deprecations page
- Last updated
- Verified
- , against Vertex AI's own pages
Questions
When does deepseek-v3.1-maas shut down?
Calls to the model deepseek-v3.1-maas on Vertex AI stopped working on October 21, 2026.
What happens to calls after October 21, 2026?
They have failed since October 21, 2026.
What error does deepseek-v3.1-maas return once it is shut down?
Vertex AI answers HTTP 404: "Publisher model `projects/{project}/locations/{region}/publishers/google/models/deepseek-v3.1-maas` was not found or your project does not have access to it. Ensure you are using a valid model name and that the model is available in the specified region.". Send another model to fix it.
When was deepseek-v3.1-maas released?
deepseek-v3.1-maas was released on August 28, 2025, according to models.dev.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
deepseek-v3.1-maas on other APIs 1
-
No date
Vertex AI
deepseek-ai/deepseek-v3.1-maasModel retirement Deprecated, no date
More from Vertex AI 10
-
deepseek-ocr-maasModel retirement Stopped working -
deepseek-r1-0528-maasModel retirement Stopped working -
deepseek-v3.2-maasModel retirement Stopped working -
glm-4.7-maasModel retirement Stopped working -
glm-5-maasModel retirement Stopped working -
gpt-oss-20b-maasModel retirement Stopped working -
kimi-k2-thinking-maasModel retirement Stopped working -
llama-3.3-70b-instruct-maasModel retirement Stopped working -
minimax-m2-maasModel retirement Stopped working -
multilingual-e5-large-instruct-maasModel retirement Stopped working
You fixed this one by hand.
Okapi opens the pull request with the fix before the next breaking change reaches your code.