DeepSeek's Four-Hour Outage and V4 Speculation

Episode 1 · DeepSeek Suffers Nearly 4-Hour Full Outage Across Web and APIs (2026-10-15, 5 posts)

On the evening of October 14 (starting around 8:11 AM Beijing time on October 15), DeepSeek suffered a rare large-scale daytime failure: its web/App chat service along with the V4 Pro and V4.1 Flash APIs were partially disrupted or even hit Full Outage. The incident lasted about 3 hours and 52 minutes, and the company said the cause had been identified and fixes were underway. Blogger vista8 was the first to report the web client showing "server temporarily unavailable," with the API seemingly affected as well, while chat history remained intact.

Confirmed

• DeepSeek's official status page posted a red incident notice covering the web chat service, the V4 Pro API, and the V4.1 Flash API, with the fault first occurring at 8:11 AM Beijing time on October 15
• The status page showed the Full Outage lasted about 3 hours and 52 minutes, with officials saying the cause had been located and a fix was in progress
• During the outage, the official status page status.deepseek.com itself returned 502 Bad Gateway at one point, leaving even the monitoring page inaccessible
• According to a report by 量子位, a mysterious account named DeepSeekHarness appeared on Bilibili during the outage

Why it matters

• teortaxesTex noted that the outage made people realize DeepSeek has effectively become part of China's digital infrastructure: huge numbers of users rely on it for work, and many platforms route requests directly to its official API
• Third-party apps depending on DeepSeek (such as the tools mentioned starting with workbu) saw clear knock-on effects during the downtime, highlighting the ecosystem's single-point dependency risk
• This prolonged daytime outage may be the longest since the R1 era, sparking community discussion about the company's service stability and operational capabilities

• DeepSeek web and API appear to be down, users report — vista8 · 2026-10-15
• DeepSeek Suffers Web and API Outage as Mysterious DeepSeekHarness Account Appears on Bilibili — 量子位 · 2026-10-15
• DeepSeek's status page itself returns 502 error amid apparent outage — teortaxesTex · 2026-10-15
• DeepSeek suffers near-4-hour full outage, possibly its longest since R1 — teortaxesTex · 2026-10-15
• DeepSeek's rare daytime outage reveals it has become China's digital infrastructure — teortaxesTex · 2026-10-15

Episode 2 · DeepSeek Full Outage Sparks New Model Launch Speculation (2026-10-15, 2 posts)

DeepSeek suffered a full outage lasting over an hour affecting V4 Pro and V4.1 Flash APIs, prompting community speculation that a new 'whale' model could launch as soon as Thursday.

• DeepSeek outage fuels speculation of a new "Whale" model launch on Thursday — teortaxesTex · 2026-10-15
• DeepSeek Suffers Full Outage, Status Page Exposes V4 Pro Naming and Fuels Release Rumors — teortaxesTex · 2026-10-15

Episode 3 · DeepSeek V4.1 Rumor Debunked After Fingerprint Check (2026-10-15, 2 posts)

A rumored DeepSeek V4.1 screenshot showing 430-460 tok/s self-reported decoding was debunked after model fingerprint matching revealed it was an old model; the poster admitted the mistake and revised the speed to about 240 t/s excluding TTFT.

• DeepSeek new-model rumor retracted: fingerprint matches old model — teortaxesTex · 2026-10-15
• DeepSeek V4.1 measures its own decode speed at 430-460 tok/s — then the claim falls apart — teortaxesTex · 2026-10-15