Caixin and Zaobao describe different DeepSeek compute notices, and neither is a rule the company has published
Yang Zirui’s Caixin story is timed 3:03 p.m. GMT+8 on Wednesday. It says that since 15 November, long chats idle for 72 hours are no longer processed, and that a long document stops at 20 pages or 10,000 tokens. Zaobao’s Monday story, citing two Chinese business papers, also has users reporting a seven-day cutoff and a cap near 40,000 Chinese characters. Both say there is no paid consumer plan.
Short2 minIn-depth
Priya Shah2 min read
- DeepSeek
- China
- Compute
- Chat

Photo: VCG, via CaixinSource page
DeepSeek has started telling people on its website and app that it cannot keep processing long chats, and the notices in two news reports do not describe the same limit. Yang Zirui’s Caixin story, published at 3:03 p.m. GMT+8 on Wednesday, says that since 15 November users have seen a company notice that long conversations inactive for 72 hours can no longer be processed, because of a shortage of computing resources. The same story says that when the app reads a long document it warns it can take only the first 20 pages, or 10,000 tokens, and cites the same reason. Users complained on Xiaohongshu and offered to pay, Caixin writes. DeepSeek charges through its API and has no paid tier for the consumer chat.
Lianhe Zaobao’s account is from Monday, at 12:50, and it is less singular. Citing the Science and Technology Innovation Board Daily and Yicai, it says several users received a notice that, because of “insufficient computing capacity, long conversations inactive for more than seven days are no longer supported,” and that a single text input has been cut to about 40,000 Chinese characters. Other users, the same story says, were told that conversations inactive for more than 72 hours are no longer supported. Some also hit a daily cap. The notice they reported reads: “Usage limit reached due to high server demand.” Zaobao says DeepSeek has not published a standard set of limits or an explanation. The 72 hours is in both stories. The seven-day wording, the 40,000-character input, and the daily cap are in Zaobao’s. The 20-page and 10,000-token document line is in Caixin’s. Neither story quotes a DeepSeek blog post that picks one rule.
What the two pieces agree on is the reason users are being given, and the absence of a subscription that would buy a way around it. Zaobao says some people were willing to pay and wanted reliable access, and that DeepSeek offered no paid option for them. It also separates this from two earlier outages: a partial failure of the site and the API on 7 November, when the chat showed “Server busy. Please try again later,” and an outage of nearly five hours on 15 October that hit the site, the app and the API. Those, it writes, were interruptions. The new notices name insufficient computing capacity. Zaobao paraphrases founder Liang Wenfeng, in a July discussion with investors, as saying computing resources were the real constraint on the team. It does not print that as a direct quotation, and it treats talk of a future paid plan as speculation. The developer API is a different product, with its own prices. These notices are about the free chat.


