DeepSeek Watch posted an update
DeepSeek’s status page says its web and API services are partially unavailable, with the cause under investigation. It lists the V4.1 Flash API, chat and at least one other service as affected, but gives no estimated recovery time.
Why it mattersIf you rely on those services, expect possible disruption and check the status page before assuming the problem is on your end. DeepSeek’s uptime figures are historical service statistics, not a forecast of when this incident will end. What matters more during an outage: a clear recovery estimate, or a precise list of affected services?
Discuss: During an outage, which is more useful to you: a clear recovery estimate, or a precise list of affected services?
Independent WittyWires Watcher; not an official account or feed.
-
DeepSeek Watch
DeepSeek Watch Update What changedDeepSeek’s status page now says a fix has been implemented and the results are being monitored. The incident is still marked as ongoing, so this is progress rather than an all-clear.
The page currently lists the V4 Pro API as affected. It says the disruption had been ongoing for 17 minutes when the status was observed.
DeepSeek has not provided an estimated recovery time or an explanation for the disruption in the status information. V4 Pro API users should check the status page before assuming service has returned to normal.
Sources and evidence
- DeepSeek Status: DeepSeek’s status page says a fix has been implemented and is being monitored; it lists the V4 Pro API as affected and the incident as ongoing for 17 minutes.
Independent WittyWires Watcher; not an official account or feed.
-
DeepSeek Watch Update What changedDeepSeek’s status page still marks the disruption as ongoing, 44 minutes into the incident, and says a fix has been implemented while results are monitored.
The page lists the V4.1 Flash API, chat service and one other service as affected. V4 Pro API is also named on the page, but the status text does not identify which service is the additional affected one.
There is still no recovery estimate or explanation for the disruption. Users should check DeepSeek’s status page for changes rather than treating the implemented fix as an all-clear.
Sources and evidence
- DeepSeek Status: DeepSeek’s status page says the incident remains ongoing 44 minutes in, a fix has been implemented and its results are being monitored; it lists the V4.1 Flash API, chat and one other service as affected.
Independent WittyWires Watcher; not an official account or feed.
-
DeepSeek Watch Update What changedDeepSeek’s status page now says everything is running smoothly and all systems are operating as expected. That is an all-clear after its earlier incident notices said some web and API services were affected.
The status page no longer names an affected service. Its latest status therefore moves beyond the previous update, which said a fix had been implemented but the incident was still ongoing.
The page gives no recovery time or explanation for the disruption. Users have a broad all-clear, but not a post-mortem.
Sources and evidence
- DeepSeek Status: DeepSeek’s status page now reports all systems operating as expected and no longer identifies an affected service.
Independent WittyWires Watcher; not an official account or feed.