DeepSeek V4 status: latest news & release notes

Reuters followed up with reports on the V4 preview and Huawei Ascend supernode support, while Sina Finance and CNBC framed the day as a major public milestone. Reporting emphasized that V4 was now discussed as usable and deployable rather than speculative.

Sina Finance and Tencent Cloud developer coverage highlighted million-context usability claims and launch-day market reaction. Reuters and CNBC framed the preview in the broader global AI competition context, and vLLM published support notes for DeepSeek-V4-Pro and DeepSeek-V4-Flash.

MyDrivers and Sina Finance relayed reports of a leaked full V4 spec sheet, including 1.6T-parameter and 1M-context claims. The day was driven by exposure-style reporting rather than confirmed primary release documentation.

Tokenmix argued V4 timing might slip to May or June due to Ascend-chip dependency and training bottlenecks, while Reuters-linked “coming weeks” expectations remained the dominant mainstream baseline. The day reflected analysis divergence rather than consensus.

InfoQ Chinese reporting focused on broader corporate moves, including financing context around Liang Wenfeng. Coverage increasingly interpreted V4 as part of a larger strategy stack, not only a standalone model release event.

Remio.ai pushed high-specificity claims around 1T parameters, 1M context, and open-source weights, then linked those assumptions to AI competition and chip-policy implications. Discussion intensity rose, but the claims remained second-hand and unconfirmed by primary official notes.

EvoLink.AI and similar technical commentary sources kept extrapolating release timing, architecture direction, and use-case fit from existing public signals. The day's narrative centered on million-context and efficiency expectations with growing market consensus.

Reuters DeepSeek coverage continued to update on training and chip context, reinforcing DeepSeek's strategic role in Chinese AI. Although not a direct V4 release note, the reporting sustained high confidence that launch-stage movement was near.

Most coverage still leaned on Reuters' April 3 line that V4 would launch in the coming weeks and run on Huawei chips. Chinese and English reporting continued integrating hardware compatibility into the core V4 narrative instead of treating it as a side topic.

A Reddit r/DeepSeek OSINT thread concentrated discussion on release timing, training bottlenecks, and architecture adjustments. Community confidence rose, but the evidence base remained inferential rather than official.

EvoLink.AI and related technical commentary shifted focus to context length, model architecture direction, and training cadence. Mention frequency for MoE, million-scale context, and domestic-chip adaptation increased noticeably.

Taibo coverage reiterated a late-April release expectation, reinforcing timelines already circulating from prior days. Most daily discussion repeated and strengthened existing launch-window expectations rather than introducing new first-hand evidence.

Caixin's morning brief explicitly wrote that V4 was expected in late April, signaling that timing expectations had moved from niche rumor channels into mainstream business coverage. The day emphasized schedule confidence more than technical disclosure.

Alibaba Cloud Developer Community discussed potential technical and industry impact, while Taipei Times framed DeepSeek's upcoming model as part of a broader geopolitical AI contest. Coverage positioned V4 as a strategic event, not just a routine version bump.

Gizchina published a long-form summary saying V4 was expected in late April with larger scale and stronger context capability. The piece mostly synthesized Reuters-linked signals rather than introducing new primary disclosures.

AASTOCKS, citing Sina Tech language, said founder Liang Wenfeng had internally indicated a late-April V4 launch window. Reports also repeated claims that major Chinese tech firms had stocked next-gen AI chips ahead of rollout, increasing market confidence without official confirmation.

This silent tiering update made the capability gap visible in everyday use, spiking community excitement and driving a surge of X discussion. It also signaled a shift from "universal access with no tiers" toward refined operations and compute scheduling.

No new long-form reporting surfaced; discussion mostly repeated the April 3 Reuters/The Information claims about Huawei Ascend deployment. Community chatter mentioned brief service instability rumors but offered no evidence, and overall attention stayed muted.

X threads clustered around April launch guesses and repeated rumor specs (1T MoE, 1M+ context, multimodal, low pricing) alongside talk of Ascend 950PR adaptation. No new mainstream reporting surfaced beyond continued Reuters-driven chatter and prediction-market odds.

No new exclusives appeared. Tech outlets such as EET-China amplified the Reuters chip story, while X/Reddit debated earlier Ascend 910B training issues and claimed optimization was complete.

Zaobao and other regional press reposted Reuters, framing V4 as fully on Huawei Ascend hardware. Community chatter spiked around a “Huawei edition” and hardware-compatibility delays.

Reuters, citing The Information, said V4 runs entirely on Huawei-designed chips and that large domestic orders were placed ahead of launch. The report claimed DeepSeek delayed the release to rewrite low-level code for domestic-chip compatibility and pointed to a launch in the coming weeks; Huawei and DeepSeek declined to comment.

Coverage stayed light and repeated late-March “April window” talk, while community threads urged waiting for official confirmation.

Little new coverage arrived; scattered X/Reddit mentions said V4 was “soon” but added no evidence. Developers continued testing V3.2 agent performance.

Community talk stayed steady but thin, reiterating April timing without new leaks or benchmarks.

Media coverage was quiet, and community threads kept to “waiting for confirmation” while comparing V3.2 agent behavior.

X posts claimed service access issues and subtle output shifts, fueling “V4 is coming” chatter. Rumors of a timed launch spread without verification, while community threads repeated that MiMo-V2-Pro was not V4.

A Reddit OSINT report suggested hardware bottlenecks, a partial shift from Huawei Ascend to Nvidia optimization, and raised April launch odds to ~75%. The report spread in community circles but drew no mainstream follow-up.

Coverage was mostly reprints of earlier reports about coding-first, long-context, and multimodal claims. Community attention softened as developers shifted to V3.2 agent testing and waited for confirmation.

No new mainstream reports surfaced. Community threads revisited the March 9 “V4 Lite” trace and noted all earlier windows had expired. X posts repeated “see you in April” with no fresh data.

X posts cited an alleged insider hint about a much larger new base model and claimed DeepSeek prioritized domestic chip partners over Nvidia/AMD early access; Polymarket odds for a March launch ticked up while Reuters' Xiaomi clarification continued to circulate.

Coverage stayed light; scattered X posts speculated V4 was imminent but offered no new evidence beyond prior reports.

An EvoLink.AI release-date recap said every earlier window had slipped, reiterated Reuters' Xiaomi attribution for Hunter Alpha, and kept April as the most cited possibility. It summarized expected V4 themes (coding focus, long-code prompts, Engram memory, 1M context) while noting API limits remained at 128K.

Discussion continued to orbit April timing and multimodal/1M-context rumors, with some posts revisiting the brief "V4 Lite" site update from March 9. No new leaks or benchmarks surfaced.

Most mentions were reprints of the March 18 Reuters clarification. Community threads focused on architecture speculation rather than new signals.

Coverage was sparse and largely recycled earlier reporting, with community discussion centered on an April window and rumored multimodal support.

Follow-up reports said Xiaomi's MiMo-V2-Pro would pilot with multiple agent frameworks and offer a brief free-access window. Luo Fuli described the reveal as a "quiet ambush" on X, while outlets such as Times of India and Independent emphasized that V4 remained unreleased. Developers kept testing the model on OpenRouter and comparing it with V3.2.

Reuters reported that the OpenRouter "Hunter Alpha" stealth model was Xiaomi's MiMo-V2-Pro internal test, not DeepSeek V4. The report reiterated that V4 had not launched and that April was the earliest rumor window, shifting community discussion away from stealth-model speculation.

X (Twitter) threads predicted a "next weekend" or April launch and repeated claims about 1T parameters, native multimodality, and domestic-chip optimization. A Medium analysis framed the delay around leaked benchmarks and geopolitics, while LinkedIn users again claimed access to the OpenRouter stealth models. Cybernews-style roundups highlighted expected coding and reasoning gains alongside lower API pricing rumors.

Dataconomy summarized Whale Lab leak claims: multimodal V4, SWE-bench Verified scores around 83.7%, a brief V4 Lite appearance on March 9, and the continued presence of Hunter Alpha and Healer Alpha as unclaimed stealth tests. Reports converged on an April launch delay, while LinkedIn and tech blogs echoed the low-cost, open-source positioning.

A Sohu article claimed V4 entered a "countdown" to a late-March release and listed 1M-token context, native multimodality, mHC/Engram efficiency gains, and domestic-chip support. The report cited no official links, so community threads treated it as unverified while comparing the claims with the OpenRouter stealth models.

KuCoin news cited Whale Lab reporting that V4 would land in April with stronger coding and long-memory performance plus multimodal support. A YouTube recap repeated the same claims and emphasized domestic chip alignment. Community testing chatter around Hunter Alpha and Healer Alpha continued, but none of it linked to official sources.

OpenRouter surfaced two anonymous "stealth" models labeled Hunter Alpha (1T parameters, 1M context, agentic workflows) and Healer Alpha (multimodal reasoning across vision/audio/text). YouTube creators framed the listings as a surprise V4 launch, while mobileproxy.space and community forums amplified unverified claims about coding and long-context performance. Most discussion still cautioned that the models were not officially confirmed.

Coverage focused on OpenRouter listing anonymous models dubbed “Hunter Alpha??and “Healer Alpha,??plus a Hugging Face upload labeled “DeepSeek-V4-INT8.??Community threads treated these as potential V4 testing signals while reiterating that none of it was officially confirmed.

Rumor roundups consolidated claims about anonymized OpenRouter models and possible INT8 preparation, but none linked to primary documentation. Discussions emphasized that timing and model naming remained speculative.

Market and tech outlets cited alleged model-weight screenshots and anonymous-model sightings on OpenRouter, predicting a near-term release window. Most reports framed the signals as unverified and urged caution.

Chinese tech outlets and community testers reported a site-side update they labeled “V4 Lite,??citing a jump to million-token context and stronger long-document and coding performance. The naming and release status remained community-driven rather than official.

Tracking sites reiterated that V4 had not launched by March 8. Commentary shifted from concrete dates to readiness discussions, with most voices pointing to the first or second week of March as the next realistic window.

Investor and community boards floated midnight-release theories tied to partner schedules. Posts were clearly marked as speculation and did not include official links or changelog proof.

News trackers summarized the missed windows and emphasized that V4 had not launched as of March 6. Analysts revisited Engram, mHC, and MODEL1 references as possible architecture hints, but none were verified by official sources. Several posts tied the 1M-context test to a late-stage infrastructure shakedown rather than a public release.

Market commentary focused on potential volatility if V4 launched in March, recalling prior swings around R1. Reports centered on macro impact rather than verifiable technical disclosures.

With policy meetings underway, analysis framed V4 as a strategic milestone tied to domestic hardware alignment. Articles cited prior reports but did not add new official evidence. Coverage focused more on market impact and supply-chain readiness than on verifiable technical disclosures.

Community posts peaked around the Lantern Festival prediction, sharing unverified comparisons and labeling them as rumor. The absence of official confirmation became the dominant signal.

Some blogs used "released" language without official confirmation. Investor Q&A responses suggested no formal pre-test access for certain partners, reinforcing that a public launch had not yet occurred. Spec sheets circulated with multimodal and long-context claims, but none linked to primary documentation.

Coverage leaned on end-February reports, repeating the "next week" release line and emphasizing multimodal support, million-token context, and domestic chip alignment. Several outlets repeated the idea of a short launch note followed by a longer technical report later.

The media narrative coalesced around an early-March window. Reports noted that official confirmation had not arrived despite widening coverage.

Regional outlets aligned on "this week/next week" expectations, highlighting multimodal capability and domestic chip compatibility. Service stability concerns appeared alongside the hype.

Multiple outlets reported a next-week release and suggested a Lite-first rollout. Training scale and schedule slip explanations appeared in parallel. Posts also highlighted a brief technical note at launch followed by a longer report later, but no formal schedule was published.

Reports referenced a "sealion-lite" internal test with native multimodal capability and million-token context. Additional coverage emphasized optimization focus on domestic chip stacks.

Infrastructure providers and trackers pointed to early March, citing the 1M context upgrade and steady leak chatter as supporting signals.

Most reporting reused earlier claims without new evidence. The lack of an official release note was repeatedly highlighted. Several posts recycled the same timing window and architecture talking points without adding primary sources.

Opinion pieces suggested a March window and framed the delay as product-readiness or strategy, rather than cancellation. Coverage remained speculative.

Trackers noted a quiet day with no new primary sources. The 1M context test remained the only persistent signal. Commentary focused on readiness checklists rather than fresh disclosures.

Community threads expressed impatience with shifting windows, landing on March as the new expectation while acknowledging the absence of formal confirmation.

Analysts debated whether V4 could reverse perceived market-share erosion. The focus shifted from spec claims to execution, stability, and commercialization.

Coverage highlighted MoE upgrades, memory mechanisms, and dual-track releases as delay drivers. Late February or early March became the most cited window. Commentary also pointed to rollout sequencing and infrastructure hardening as likely causes.

Podcasts and commentary reframed the slip as a strategic pause, shifting expectations toward March and emphasizing the need for readiness over hype.

Technical blogs focused on Engram-style memory, mHC, and sparse attention as prerequisites for million-token context. The narrative moved toward feasibility analysis.

Coverage recycled benchmark-leak claims and connected them to the 1M context upgrade. The day set the tone for a rumor-heavy two-week stretch. Several summaries urged teams to wait for official model cards before treating any spec sheet as final.