DeepSeek implemented fixes after partial outages affected chat, V4 Pro API, and V4.1 Flash API services; monitoring continues.

DeepSeek’s official status page, as quoted in the supplied messages, reported partial web and application programming interface (API) disruption beginning at 15:11 on November 7. The messages do not explicitly state the time zone associated with that incident timestamp.

The affected components were Chat Service, DeepSeek V4 Pro API, and DeepSeek V4.1 Flash API. A reporter testing the service encountered unavailable chat functionality and a message reading, “Server busy, please try again later.”

The status initially indicated investigation to identify the cause, followed by an update saying fixes had been implemented and their results were being monitored. That is a remediation-and-monitoring status, not an explicit all-clear; no root cause, affected-user count, or final outage duration is provided.