Live / DeepSeek / Incident
DeepSeek: DeepSeek 网页/API 性能异常(DeepSeek Web/API Degraded Performance)
DeepSeek · deepseek.comMajor incidentResolved2025-02-08 06:49 UTC
Public — what happened
Summary
DeepSeek reported degraded performance on its web service and API, rating the incident as major, with its first updates posted on January 27, 2025 at 13:33 UTC. Later that day, DeepSeek said its services were under large-scale malicious attacks and that it was temporarily restricting new sign-ups, while people who already had accounts could still log in. Over the following days the company posted several rounds of identifying the problem, applying fixes and monitoring. DeepSeek marked the incident resolved on February 8 at 06:49 UTC.
Affected
API 服务 (API Service), 网页对话服务 (Web Chat Service)
Timeline
- Started — 2025-01-27 15:15 UTC
- Investigating — 2025-01-27 13:33 UTC (2 updates)
- Monitoring — 2025-01-27 15:15 UTC (4 updates)
- Identified — 2025-01-28 09:03 UTC
- Monitoring — 2025-01-28 09:06 UTC (3 updates)
- Identified — 2025-01-29 12:57 UTC
- Investigating — 2025-01-30 15:59 UTC
- Monitoring — 2025-01-30 17:19 UTC
- Identified — 2025-01-31 14:10 UTC
- Monitoring — 2025-01-31 16:17 UTC (2 updates)
- Resolved — 2025-02-08 06:49 UTC · 12 days after it started
With SquidGrid — where it starts on the route
Independent path health
The status page is the symptom. SquidGrid measures the paths that reach DeepSeek against their own baselines — whether the routes carrying your traffic degraded, at which handoff, and who owns that stretch.
🔒 Sign in to seeCustomers get the live Provider Assessment Report for DeepSeek: its full incident track record, what tends to break, and recent public reports of problems.
Included with any paid plan.
Open the DeepSeek report →
More from DeepSeek