DeepSeek Outage Oct 15: V4 Pro and V4.1 Flash Affected; Pro Gray Test?
TL;DRDeepSeek's official status page records a web and API incident starting at 08:11 Beijing time on October 15. The V4 Pro API, V4.1 Flash API and chat service were affected. At the 12:33 Beijing time check, DeepSeek had identified the cause and was implementing a fix; the incident was not marked resolved. There is no official evidence linking the outage to a V4.1 Pro gray test.
By DeepSeek V4 Hub
Status checked: October 15, 2026, 04:33 UTC (12:33 Beijing time).
DeepSeek users reported seeing a “server temporarily unavailable” message during chats on October 15. The official incident record confirms a partial web/API outage beginning at 00:11 UTC, or 08:11 Beijing time. It lists the V4 Pro API, V4.1 Flash API and chat service as affected. The status page does not say that a model rollout caused the interruption.
What happened to DeepSeek on October 15?
The official timeline starts with an investigation at 08:11 Beijing time. DeepSeek changed the incident to “Identified” at 09:06–09:08 Beijing time, saying it had found the cause and was implementing a fix. At the 12:33 Beijing time status check used for this article, the incident page still showed an outage, without a resolution notice. Check the live status page for the latest recovery update.
That timeline does not support a fixed three-hour duration or a claim that service had already recovered. It also places the start in the morning in Beijing, rather than late at night.
Does the outage mean DeepSeek V4.1 Pro is in gray testing?
No confirmed connection has been published. DeepSeek's V4.1 Flash announcement said its deepseek-v4-pro API route would serve V4.1 Flash until V4.1 Pro launches. That makes a future Pro release a reasonable topic to watch, but it does not identify the cause of this outage or confirm a rollout on October 15.
Some users say recent DeepSeek answers feel stronger and speculate that V4.1 Pro traffic is being tested. These are impressions, not a verified model ID, release note, controlled benchmark or official confirmation. Similar incidents have occurred on other dates: the September 2 incident preceded the V4.1 Flash announcement, while a three-hour incident on September 14 followed it. Timing alone cannot establish a release pattern.
Why are developers watching V4.1 Pro?
DeepSeek officially launched V4.1 Flash on September 10, describing a new architecture, native visual understanding, higher throughput and lower API rates. The announcement also said V4.1 Pro would launch later. Those are DeepSeek's published product claims and roadmap language; this article has not run a fresh independent performance test or measured how many users switched providers.
For teams depending on the API, the practical next step is to check the incident page, record request times and model IDs, and compare the same prompts again after service recovers. A perceived quality change by itself cannot identify the model serving a request.
We will update this report when DeepSeek marks the incident resolved or publishes a V4.1 Pro announcement.
Want to try DeepSeek V4.1 Flash with a Coding Plan? Visit pricing.