TechnologyTracking
How extensive is DeepSeek's service disruption?
DeepSeek's web and API services are partially disrupted and the company says it is investigating; how extensive is the impact on developers and enterprise users relying on its services?
Watching: 官方尚未公布中断的具体原因、受影响用户数量及恢复时间，影响范围存在不确定性。
Current read
On Oct 15, 2026, DeepSeek's web and API services were disrupted for nearly 5 hours, affecting developers and downstream enterprise applications; services recovered at 13:04 that day.
Multiple reports indicate that on the morning of Oct 15, 2026, DeepSeek's web, mobile app, and API services experienced an outage lasting about 4 hours 52 minutes, recovering at 13:04. The disruption affected regular users, developers, and downstream enterprise applications using the API. Official statements confirmed the cause was identified and fixed. Reports do not specify the number of affected users or quantify business losses, so the exact scale remains unclear.
Key developments
- New facts: outage lasted about 4h52m, recovered at 13:04, affecting web, app, and API, impacting developers and downstream apps.
How we read it
The outage began on the morning of Oct 15, lasted about 4h52m, recovered at 13:04, affecting web, app, and API.
Reports state API services were affected, impacting developers and downstream apps, but no user counts or loss figures are given.
Earlier updates
- — Public tracking started; no independent probability estimate yet.; Starting public context: DeepSeek web and API services partially disrupted, company says investigating
- — On Oct 15, 2026, DeepSeek's web and API services were disrupted for nearly 5 hours, affecting developers and downstream enterprise applications; services recovered at 13:04 that day.; Multiple reports indicate that on the morning of Oct 15, 2026, DeepSeek's web, mobile app, and API services experienced an outage lasting about 4 hours 52 minutes, recovering at 13:04. The disruption affected regular users, developers, and downstream enterprise applications using the API. Official statements confirmed the cause was identified and fixed. Reports do not specify the number of affected users or quantify business losses, so the exact scale remains unclear.