Live / DeepSeek / Incident
DeepSeek: 【已恢复】DeepSeek API 异常([Resolved]DeepSeek API Abnormal)
DeepSeek · deepseek.comCritical outageResolved2026-04-22 11:26 UTC
Public — what happened
Summary
DeepSeek reported a critical problem with its API on April 22, 2026, beginning at 10:23 UTC, and did not say which users were affected. The company posted that it was looking into the issue but did not share a cause. DeepSeek marked the incident as resolved at 11:26 UTC the same day.
Affected
API 服务 (API Service)
Timeline
- Started — 2026-04-22 10:23 UTC
- Investigating — 2026-04-22 10:23 UTC
- Resolved — 2026-04-22 11:26 UTC · 1h 03m 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