Chinese AI lab spun out of quant fund High-Flyer. Builds open-weight DeepSeek-V and DeepSeek-R reasoning models known for strong benchmarks at low inference cost. Distributes through deepseek.com (chat + API) and Hugging Face.
Components ranked by incident count. Click a row for the incident list. Down-time is attributed proportionally for multi-component incidents.
Component
Incidents
Down (attr.)
Median MTTR
Last
Score Breakdown
Uptime50%
92.1
Frequency20%
98.8
Severity20%
96.8
MTTR10%
90.7
SLA Compliance
How often does this provider clear their stated availability target?
Industry default (99.9%) · 99.90%
✓ last 90d99.97%+0.07%
Met SLA in 12 of 13 weeks (92%)
13 weeks on record
Method: a rolling quarter (13 weeks ≈ 91 days). Each cell is one 7-day slice of Statuspage-standard uptime (1 − (critical + 0.3 × major) / window; minors and maintenance excluded; red when the slice dips below the stated SLA).
DeepSeek — Incidents by Day last 90d
MinorMajorCritical
Total 3 incidents
0
1
1
2
2
05-1005-2206-0306-1506-2707-0907-2108-02
Worst Incidents
Ranked by severity-weighted duration (impact × wall-clock). Click any incident for the full update timeline.
Type of Failure
Categorised from the public incident headlines (outage / latency / auth / etc.).
Degraded
2
67%
Other
1
33%
When It Breaks
Incident starts by weekday × hour, UTC. Hover a cell for incident detail.
S
0
M
0
T
0
W
Wednesday03:00–04:00 UTC
1incident
1 major
【已恢复】DeepSeek 网页/API 性能异常([Resolved]DeepSeek Web/API Service Degraded Performance)May 6
Wednesday07:00–08:00 UTC
1incident
1 minor
【已恢复】DeepSeek 网页/API 性能异常([Resolved]DeepSeek Web/API Service Degraded Performance)May 6
2
T
0
F
Friday09:00–10:00 UTC
1incident
1 critical
【已恢复】DeepSeek 网页/API不可用([Resolved]DeepSeek Web/API Service Not Available)May 8
1
S
0
00
06
12
18
HOUR OF DAY · UTC3 incident starts · hover any cell for detail
Hottest hour
Wednesday 03:00 1
Worst day
Wednesday 2
Worst time of day
03:00–04:00 1
How fast they fix things
Distribution of resolution times alongside the 12-week trend so you can see whether they're getting faster or slower.
Typical fix
11m
half of incidents resolve faster
On a bad day
34m
9 in 10 resolve faster than this
Distribution
<15m
2
15m–1h
1
1–4h
0
4–24h
0
24h+
0
+0 ongoing (not counted above)
MTTR Trend (12 weeks)
Are they recovering faster or slower over time? Lower is better.