Live / DeepSeek / Incident
DeepSeek: 【已解决】DeepSeek 网页/APP 性能异常([Resolved]DeepSeek Web/APP Service Performance Agnormal)
DeepSeek · deepseek.comCritical outageResolved2026-03-30 02:33 UTC
Public — what happened
Summary
DeepSeek reported a critical performance problem affecting its web and app services, which it began investigating at 16:20 UTC on March 29, 2026. The company said it put a fix in place by 17:24 UTC, but it returned to investigating at 18:16 UTC. A second fix was reported at 01:13 UTC on March 30, and DeepSeek marked the incident resolved at 02:33 UTC that day without naming a cause.
Affected
网页对话服务 (Web Chat Service)
Timeline
- Started — 2026-03-29 16:20 UTC
- Investigating — 2026-03-29 16:20 UTC (2 updates)
- Monitoring — 2026-03-29 17:24 UTC
- Investigating — 2026-03-29 18:16 UTC
- Monitoring — 2026-03-30 01:13 UTC (2 updates)
- Resolved — 2026-03-30 02:33 UTC · 10h 13m 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