Live / DeepSeek / Incident
DeepSeek: 【已恢复】DeepSeek 网页/API不可用([Resolved]DeepSeek Web/API Service Not Available)
DeepSeek · deepseek.comCritical outageResolved2025-01-27 08:43 UTC
Public — what happened
Summary
DeepSeek reported a critical outage on January 27, 2025, saying its web service and API were unavailable. The company began looking into the problem at 06:37 UTC and said two minutes later that a fix was in place, but it resumed investigating at 08:07 UTC. DeepSeek said another fix was applied at 08:33 UTC and marked the incident resolved at 08:43 UTC, without naming a cause.
Affected
API 服务 (API Service), 网页对话服务 (Web Chat Service)
Timeline
- Started — 2025-01-27 06:37 UTC
- Investigating — 2025-01-27 06:37 UTC (2 updates)
- Monitoring — 2025-01-27 06:39 UTC
- Investigating — 2025-01-27 08:07 UTC
- Monitoring — 2025-01-27 08:33 UTC
- Resolved — 2025-01-27 08:43 UTC · 2h 06m 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