The outage and its duration
On the afternoon of November 7, DeepSeek experienced a partial interruption of its web and API services. According to a report by IT之家, several users reported the problem through the platform, receiving the message "server temporarily unavailable" in their conversations. The outage lasted from 15:11 to 15:56, for a total duration of 45 minutes.
The nature of the interruption is described as partial: the source material indicates that web and API services were involved, without specifying which functionalities remained operational and which did not. No technical causes behind the blockage are indicated, nor is the number of users or requests affected.
Restoration according to the status page
According to IT之家, DeepSeek's official status page indicates that the problem has been resolved and that service has returned to normal. The company's communication, as reported by the source, does not contain further details on the measures taken for restoration.
The most concrete data available is the time window of the interruption, derived from the status page itself: 45 minutes in total. This information makes it possible to measure the extent of the outage, but not to reconstruct its evolution minute by minute or to know whether the restoration was gradual or immediate.
What remains to be verified
The material does not clarify the cause of the outage, does not specify whether the interruption affected the web version and the APIs differently, and does not report direct statements from DeepSeek beyond what was published on the status page. No elements are available to assess the impact on enterprise customers or on third-party applications that depend on the APIs.
It is also not indicated whether similar episodes have occurred previously or whether measures have been announced to prevent further interruptions. These aspects remain outside the scope of the available information and would require verification with the company or through additional sources.
The news has a limited informational value: it documents a short but officially declared interruption, with defined times, and its subsequent restoration. Further analysis would require technical communication from the company on the causes and any corrective actions.
