Live / DeepSeek / Incident
DeepSeek: 【已恢复】DeepSeek R1 网页/API不可用([Resolved] DeepSeek R1 Web/API Service Not Available)
DeepSeek · deepseek.comCritical outageResolved2025-03-10 16:38 UTC
Public — what happened
Summary
DeepSeek reported a critical outage in which its R1 model could not be used through either its website or its API. The company began looking into the problem at 16:12 UTC on March 10, 2025. It marked the incident as resolved at 16:38 UTC the same day and did not give a cause.
Affected
API 服务 (API Service), 网页对话服务 (Web Chat Service)
Timeline
- Started — 2025-03-10 16:12 UTC
- Investigating — 2025-03-10 16:12 UTC
- Resolved — 2025-03-10 16:38 UTC · 25 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