Live / DeepSeek / Incident
DeepSeek: 【已恢复】DeepSeek 网页不可用([Resolved]DeepSeek Web Service Not Available)
DeepSeek · deepseek.comCritical outageResolved2026-03-05 04:35 UTC
Public — what happened
Summary
DeepSeek reported a critical outage that made its web service unavailable, beginning at 03:50 UTC on 2026-03-05. The company did not say which users were affected or what caused the problem, only that it had pinpointed the issue by 04:23 UTC and started applying a fix. After the fix was in place at 04:32 UTC, DeepSeek watched the results and declared the incident resolved at 04:35 UTC.
Affected
网页对话服务 (Web Chat Service)
Timeline
- Started — 2026-03-05 03:50 UTC
- Investigating — 2026-03-05 03:50 UTC (2 updates)
- Identified — 2026-03-05 04:23 UTC
- Monitoring — 2026-03-05 04:32 UTC
- Resolved — 2026-03-05 04:35 UTC · 45 min 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