DeepSeek
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.
Products
DeepSeek Chat · DeepSeek API · DeepSeek-V / DeepSeek-R / DeepSeek-Coder models
Reliability — last 14d
Composite score
Uptime
Incidents
Median MTTR
What's breaking (last 14d)
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 |
|---|---|---|---|---|
API 服务 (API Service) | 1 | 1h 3m | 1h 3m | 10d ago |
网页对话服务 (Web Chat Service) | 1 | 3h 28m | 3h 28m | 12d ago |
Type of failure
Categorised from the public incident headlines (outage / latency / auth / etc.). Click a category to drill in.
When it breaks
Incident starts by weekday × hour, UTC. Hover a cell for incident detail.
Hour of day · UTC
Score breakdown
SLA compliance
How often does this provider clear their stated availability target?
Incident history
showing 4 of 50 · 4 of 41 days
How fast they fix things
Distribution of incident resolution times.
Typical fix
1h 3m
half of incidents resolve faster
On a bad day
3h 28m
9 in 10 resolve faster than this
Distribution
DeepSeek — incidents by day (last 14d)
Worst incidents
Ranked by severity-weighted duration (impact × wall-clock). Click any incident for the full update timeline.
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.
* No public SLA — using common enterprise target (99.9%) for comparison.