DeepSeek V4 daily log
Daily updates from February 15, 2026 through March 8, 2026. The timeline blends official-channel checks, media reports, and community signals so teams can track momentum without chasing noise.
Throughout this window, official pages and API changelogs continued to list V3.2 as the flagship model. Most V4 detail came from third-party reports and technical commentary, so we label each day by the dominant source type rather than presenting speculation as verified fact.
Use this log to plan around likely windows, not to time a release. The safest posture is to keep pipelines flexible with V3.1, R1, Math-7B, Janus-Pro-7B, and VL2, then upgrade as soon as V4 becomes officially available.
Each card is a compact daily brief. "Official" summarizes what is visible in public docs, API logs, and product pages that day. "Media" captures coverage, analyst notes, and community signals. This split is intentional so teams can separate confirmed status from external commentary.
Recurring themes from late February show up across the log: the 1M-context upgrade, speculation about a short launch note followed by a longer technical report, and hints about a phased rollout. We include those threads only when they shaped the daily conversation.
Official pages continued to list V3.2 as the flagship model. API changelogs and public repositories showed no V4 release notes, weights, or new model identifiers. Product and pricing pages remained unchanged, with no new endpoints or version flags.
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.
No official statement appeared on the website, API docs, or GitHub. Public channels remained unchanged from earlier in the week.
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.
The public API log still stopped at the prior V3.2 update. No V4 model names or configuration flags were visible in official documentation.
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.
No changes appeared in official product pages. Release status remained unconfirmed.
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.
Official channels stayed quiet with no new model listings or API updates. V3.2 remained the public flagship.
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.
No release announcement, blog post, or API update arrived on the anticipated launch day. Public assets remained unchanged.
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.
Official documentation still showed no V4 model identifiers. API changelogs remained at the previous version update.
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.
Website and API logs continued to list V3.2 as the newest flagship. No V4 entries or release notes appeared.
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.
Official channels still lacked any V4 naming, model endpoint, or change log entry. Public repositories showed no new release artifact.
The media narrative coalesced around an early-March window. Reports noted that official confirmation had not arrived despite widening coverage.
No official statements or API updates were published. V3.2 remained the visible flagship.
Regional outlets aligned on "this week/next week" expectations, highlighting multimodal capability and domestic chip compatibility. Service stability concerns appeared alongside the hype.
Official pages stayed unchanged, with no V4 release notes or public API identifiers.
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.
No official confirmation appeared in the API log or product pages. The only confirmed infrastructure signal remained the earlier 1M context test.
Reports referenced a "sealion-lite" internal test with native multimodal capability and million-token context. Additional coverage emphasized optimization focus on domestic chip stacks.
Official channels still showed no V4 mention. API logs and public repos remained unchanged.
Infrastructure providers and trackers pointed to early March, citing the 1M context upgrade and steady leak chatter as supporting signals.
No new public documentation or model entries appeared.
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.
The official stance remained silent, with no V4 release artifacts.
Opinion pieces suggested a March window and framed the delay as product-readiness or strategy, rather than cancellation. Coverage remained speculative.
Public documentation continued to list V3.2 as the newest release. No V4 references surfaced.
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.
No official schedule or roadmap was published.
Community threads expressed impatience with shifting windows, landing on March as the new expectation while acknowledging the absence of formal confirmation.
There were no official updates or new release notes.
Analysts debated whether V4 could reverse perceived market-share erosion. The focus shifted from spec claims to execution, stability, and commercialization.
Official channels stayed quiet on release timing.
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.
No release or documentation update appeared on the expected date.
Podcasts and commentary reframed the slip as a strategic pause, shifting expectations toward March and emphasizing the need for readiness over hype.
Official materials remained unchanged, with no V4 naming or API updates.
Technical blogs focused on Engram-style memory, mHC, and sparse attention as prerequisites for million-token context. The narrative moved toward feasibility analysis.
No official V4 release note, API change, or model identifier appeared. Public pages continued to list V3.2 as flagship.
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.