DeepSeek Outage History
Uptime record, past incidents, and downtime history for DeepSeek.
Checking current status...
90-Day Trend
Monthly Uptime
| Month | Uptime | Days Tracked | Days with Issues |
|---|---|---|---|
| April 2026 | 75% | 4 | 1 |
| March 2026 | 80.6% | 31 | 6 |
| February 2026 | 94.7% | 19 | 1 |
Uptime is calculated from daily worst-status snapshots. A day with any non-operational status counts as a day with issues.
Daily Status (Last 54 Days)
Feb 10
Today
Operational
Degraded
Partial Outage
Major Outage
Maintenance
No Data
Incident History
April 2026
DeepSeek 网页/APP 服务异常（DeepSeek Web/APP Service Abnormal）
Started: Apr 3, 8:36 AM
monitoring
A fix has been implemented and we are monitoring the results.
Apr 3, 8:39 AM
investigating
We are continuing to investigate this issue.
Apr 3, 8:38 AM
investigating
We are currently investigating this issue.
Apr 3, 8:36 AM
March 2026
DeepSeek 网页/API 性能异常（DeepSeek Web/API Service Degraded Performance）
Started: Mar 31, 9:02 AM
investigating
We are continuing to investigate this issue.
Mar 31, 9:35 AM
investigating
We are currently investigating this issue.
Mar 31, 9:02 AM
DeepSeek 网页/APP 性能异常（DeepSeek Web/APP Service Performance Agnormal）
Started: Mar 29, 4:20 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 30, 1:13 AM
investigating
We are currently investigating this issue.
Mar 29, 6:16 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 29, 5:24 PM
investigating
We are continuing to investigate this issue.
Mar 29, 4:36 PM
investigating
We are currently investigating this issue.
Mar 29, 4:20 PM
DeepSeek 网页/APP 服务异常（DeepSeek Web/APP Service Abnormal）
Started: Mar 29, 1:35 PM
monitoring
A fix has been implemented and we are monitoring the results.
Mar 29, 3:08 PM
identified
The issue has been identified and a fix is being implemented.
Mar 29, 2:28 PM
investigating
We are currently investigating this issue.
Mar 29, 1:35 PM
DeepSeek 网页/APP 性能异常（DeepSeek Web/APP Service Degraded Performance）
Started: Mar 18, 12:26 PM
identified
The issue has been identified and a fix is being implemented.
Mar 18, 12:29 PM
investigating
We are currently investigating this issue.
Mar 18, 12:26 PM