Live / DeepSeek / Incident
DeepSeek: 【已恢复】DeepSeek 网页/API性能下降([Resolved] DeepSeek Web/API Performance Degradation)
DeepSeek · deepseek.comMinor incidentResolved2025-07-30 04:19 UTC
Public — what happened
Summary
DeepSeek said its website and API were running slower than normal, beginning around 02:01 UTC on July 30, 2025, and rated the problem as minor. By 02:29 UTC the company reported that requests could take longer to complete and that it had pinpointed the problem, though it did not say what the cause was. DeepSeek marked the incident as resolved at 04:19 UTC the same day.
Affected
API 服务 (API Service), 网页对话服务 (Web Chat Service)
Timeline
- Started — 2025-07-30 02:01 UTC
- Investigating — 2025-07-30 02:01 UTC
- Identified — 2025-07-30 02:29 UTC
- Resolved — 2025-07-30 04:19 UTC · 2h 19m 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