DeepSeek "limit"? Many netizens reported that they received a prompt: the usage limit has been reached.

📅 2026-11-16

Abstract:

The free usage quota of the domestic large model DeepSeek is suspected to be restricted. On November 16, “DeepSeek usage quota has reached the upper limit” became a hot search on Weibo. Many users reported on social media that DeepSeek has adjusted the usage quota of the App and web version, including limiting long conversations, daily usage quota, and single text input length.

As of press time, DeepSeek has not yet made an official response to this. It is worth noting that DeepSeek’s quota is mainly targeted at App applications and web version C-sides for ordinary users, rather than API interfaces used by developers.

Judging from user feedback published on social platforms, the relevant restriction standards seem to be inconsistent, and the changes mainly come from three major aspects: Many users received prompts saying that due to "insufficient computing power", "long conversations that are inactive for more than 7 days are no longer supported"; some users pointed out that the upper limit of single input text has been shortened to about 40,000 words; another user said that after using DeepSeek continuously for less than 2 hours, they received a prompt that "the usage quota has reached the upper limit due to busy servers".


Source: social platform

Analysis pointed out that the tight supply of computing resources may be the reason behind DeepSeek’s quota limit.

Data from the global model aggregation platform OpenRouter shows that during the week from November 9 to November 15, the number of Token (word elements) calls of DeepSeek V4.1 Flash 1017 reached 59.2 trillion, ranking first in the world.

DeepSeek's official status page records that since October this year, the platform has experienced 8 service interruptions, covering conversation services and APIs of V4 Pro and V4.1 Flash. Among them, the failure lasted for more than 4 hours on October 15. This was also the failure with the largest impact and longest duration in October. Synchronization of C-side web pages, App conversation services, and V4 Pro and V4.1 Flash APIs was limited.

On November 3, #DeepSeek collapsed# once again became a hot search topic. In the evening of that day, according to the DeepSeek status page, at about 16:58, the DeepSeek web page/API was partially interrupted. The affected components included the DeepSeek V4.1 Flash API service, conversation service, and DeepSeek V4 Pro API service.

On November 13, DeepSeek officially opened the Family Bucket application API. By turning on the corresponding parameters in the original API, you can obtain deep thinking search, file input and other dialogue functions; voice and related underlying capabilities have also opened independent interfaces (including OCR, ASR, TTS, etc.), supporting individual or combined calls. Developers can easily implement complex dialogue functions in their own applications, and even reproduce the complete DeepSeek App 1:1.

Related tags

Related articles

Comments

0/500
Captcha (click to refresh)
No comments yet