DeepSeek V4 Pro is described in the supplied third-party snippets as an open-weight mixture-of-experts model from DeepSeek, released alongside the smaller V4 Flash for reasoning, software engineering, and agentic tasks. The case cites a Reddit user's report of V4 Pro being “soft-retired” and an attributed staff statement that V4.1 Flash outperforms it, but the supplied search snippets do not substantiate either claim or establish reduced availability. Instead, they describe V4 Pro API access through multiple providers; the explicit retirement notice concerns the legacy aliases deepseek-chat and deepseek-reasoner, not V4 Pro itself. The search answer's categorical retirement claim therefore exceeds the supporting snippets, and any effect on dependent deployments remains unverified.
Scott’s Model Perishability page already argues that rapid model replacement requires swappable dependencies; this report offers only an unverified example, not a substantiated availability change or a consequential party adopting his position. The hits establish no Scott dependency on V4 Pro, and although the radar tracks analogous Copilot deprecations, it does not establish prior coverage of this specific development.
ip:concept.model-perishabilityradar:github-copilot-model-deprecations
queries asked of Scott's wikis
- model retirement API lifecycle migration dependencies
- agent harness model routing fallback regression evaluations
- open weights sovereignty hosted API availability
- self-hosted inference provider concentration risk
- coding agents model upgrades cost performance tradeoffs
now 0 pts/hpeak 0 pts/hcomments 0/hpeers p0momentum: steady2 platformsage 794h
points/hour across evidence · reading as of 2026-10-12 02:59:37.977291+11:00 · deterministic, not a model opinion
2026-09-11T14:29:14Z
A new Reddit report claims V4 Pro was quickly restored, weakening the sustained-availability-loss hypothesis and raising the possibility of a short-lived routing reversal. Its title-only evidence does not verify restoration, so neither ongoing retirement nor a completed rollback is established.
2026-09-11T14:22:13Z
evidence attached: reddit.post.1wdg90y — The reported rapid un-retirement directly contradicts the open case’s hypothesis that DeepSeek V4 Pro availability is narrowing.
2026-09-10T19:38:49Z
The refreshed discussion reinforces the distinction between hosted endpoint substitution and withdrawal of open weights, but adds no independently verified availability change or measured regression. The staff-attributed routing and billing report remains meaningful testimony from one evidence lineage; neither broad retirement nor task-level equivalence is established.
2026-09-10T05:23:04Z
The refreshed comments add no new operational evidence: task preferences and capacity speculation do not independently confirm substitution or establish regressions. The case remains a staff-attributed temporary endpoint routing and billing change supported by one reconstructed evidence lineage, not a demonstrated retirement of V4 Pro weights or third-party access.
2026-09-10T00:24:01Z
The refreshed discussion adds no independent routing evidence or measured regressions; preferences for Pro remain anecdotal. The substantive report is still a staff-attributed temporary substitution of V4.1 Flash at Flash rates, not demonstrated retirement of V4 Pro weights or third-party access.
2026-09-09T22:34:21Z
The refreshed comments add no independent evidence or measured regressions; preferences for Pro do not establish the impact of the reported substitution. The case remains a staff-attributed temporary routing and billing change supported by one reconstructed evidence lineage, not demonstrated retirement of weights or third-party access.
2026-09-09T21:29:28Z
The refresh remains amplification of one staff-attributed report, with no independent routing evidence or measured task regressions. The episode concerns temporary endpoint substitution and Flash-rate billing, not established retirement of V4 Pro weights or third-party access; repeated discussion no longer warrants hourly review.
2026-09-09T19:42:37Z
Refreshed discussion adds no substantive evidence: task preferences and capacity speculation neither confirm routing nor establish regressions. The meaningful report remains a staff-attributed temporary substitution of V4.1 Flash behind the V4 Pro endpoint at Flash rates, not retirement of open weights or third-party access.
2026-09-09T17:27:01Z
Refreshed discussion adds preferences and speculation, not independent evidence of routing changes or measured regressions. The substantive report remains a staff-attributed temporary substitution behind the V4 Pro endpoint at Flash pricing, supported by one reconstructed evidence lineage—not withdrawal of open weights or third-party access.
2026-09-09T16:32:25Z
The refreshed discussion adds no independent evidence of endpoint substitution or measured regressions; task preferences and capacity speculation remain amplification of the same report. The case still concerns a staff-attributed temporary routing and billing change, not demonstrated retirement of V4 Pro weights or third-party access.
2026-09-09T14:33:46Z
The refreshed discussion adds no substantive change: task preferences and capacity speculation do not demonstrate deployment regressions. The actionable interpretation remains a staff-attributed temporary endpoint substitution at Flash pricing, not retirement of V4 Pro weights or third-party access; the Reddit screenshot and reconstructed post are one evidence lineage.
2026-09-09T13:35:22Z
Refreshed comments add no substantive evidence beyond previously reported task-specific preferences and speculative explanations. The case remains a staff-attributed temporary endpoint substitution at Flash pricing, supported by reconstructed testimony—not an established withdrawal of V4 Pro weights or third-party access.
2026-09-09T12:33:51Z
The discussion remains repetitive amplification: task-specific preferences do not establish deployment regressions or independently confirm endpoint routing. The meaningful claim remains a staff-attributed temporary substitution of V4.1 Flash at Flash rates, not a demonstrated retirement of V4 Pro weights or third-party access.
2026-09-09T11:30:06Z
The refreshed discussion repeats task-specific preferences and speculative explanations; it supplies neither independent routing confirmation nor measured deployment regressions. The substantive claim remains a staff-attributed temporary substitution behind the V4 Pro endpoint at Flash pricing, not withdrawal of open weights or third-party access.
2026-09-09T10:25:31Z
Refreshed discussion adds task-specific objections to replacing Pro with Flash, but no independent routing confirmation or measured regression. The case remains an attributed temporary endpoint substitution at lower pricing, not an established withdrawal of open weights or third-party access.
2026-09-09T09:27:46Z
The substantive claim is temporary substitution behind the V4 Pro endpoint at Flash pricing, attributed to DeepSeek staff through reconstructed testimony—not demonstrated withdrawal of V4 Pro weights or all provider access. Refreshed comments raise task-specific regression concerns but supply no independent confirmation of routing or measured regressions.
2026-09-09T09:27:20Z
grounded: known/low — Scott’s Model Perishability page already argues that rapid model replacement requires swappable dependencies; this report offers only an unverified example, not
2026-09-09T09:24:34Z
origin walked (codex/luna, conf 0.88): anchor reddit.post.1wbfrut -> echo.x.b6f987baca by Tianyi Cui
2026-09-09T09:22:37Z
case created — The reported retirement is a bounded availability episode distinct from the Flash releases, but the title and linked image alone do not establish its scope, cause, or first-party confirmation.