Live / DeepSeek / Incident
DeepSeek: 【已恢复】DeepSeek V3 网页/API不可用([Resolved]DeepSeek V3 Web/API Service Not Available)
DeepSeek · deepseek.comMajor incidentResolved2025-07-01 10:15 UTC
Public — what happened
Summary
DeepSeek reported a major incident on July 1, 2025 in which its DeepSeek V3 web service and API were unavailable. The company said at 10:05 UTC that it had found the problem and was working on a fix, though it did not say what the cause was or which users were affected. DeepSeek marked the incident as resolved at 10:15 UTC, about ten minutes later.
Affected
API 服务 (API Service), 网页对话服务 (Web Chat Service)
Timeline
- Started — 2025-07-01 10:05 UTC
- Identified — 2025-07-01 10:05 UTC
- Resolved — 2025-07-01 10:15 UTC · 10 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