Live / DeepSeek / Incident
DeepSeek: DeepSeek 无法登录/注册(Cannot Login/Sign up on DeepSeek)
DeepSeek · deepseek.comCritical outageResolved2025-01-27 13:32 UTC
Public — what happened
Summary
DeepSeek reported a critical problem on January 27, 2025, starting at 12:16 UTC, that stopped people from logging in to or creating accounts on its service. By 12:55 UTC the company said its chat service was working again, but account access was still failing, and it resumed looking into the account problem at 13:11 UTC. DeepSeek did not give a cause and marked the incident resolved at 13:32 UTC.
Affected
API 服务 (API Service), 网页对话服务 (Web Chat Service)
Timeline
- Started — 2025-01-27 12:16 UTC
- Investigating — 2025-01-27 12:16 UTC
- Monitoring — 2025-01-27 12:55 UTC (3 updates)
- Investigating — 2025-01-27 13:11 UTC
- Resolved — 2025-01-27 13:32 UTC · 1h 16m 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