Is DeepSeek down?
Right now
No. DeepSeek is operational.
No incidents reported.
Read from status.deepseek.com · every 120s
For agents
proceed
Proceed.
GET upbutler.com/status/deepseek/status.agent.json
MCP: upstream_status {"service":"deepseek"}
The DeepSeek chat and reasoning model API.
What DeepSeek reports
Operational
Taken as is from DeepSeek's own incident feed. Incident titles and component names below are theirs.
Open status.deepseek.comUpButler's independent probe
API edge is answeringHTTP 401 · 275 ms
One request without credentials to api.deepseek.com every two minutes. An answer (the expected "not authenticated") shows the edge, TLS and routing work. It does not prove that authenticated calls succeed.
Checked · up since 2026-10-10 01:23 UTC
DeepSeek incidents, last 90 days
2 finished incidents seen since UpButler started tracking on 2026-10-10.
| Started (UTC) | Incident | Impact | Lasted |
|---|---|---|---|
| DeepSeek 网页/API 性能下降（DeepSeek Web/API Degraded Performance） | minor | under a minute | |
| DeepSeek 网页/API 性能下降（DeepSeek Web/API Degraded Performance） | minor | under a minute |
Tell your outage from DeepSeek's
Declare that your project depends on DeepSeek. When one of your monitors fails while DeepSeek has an incident that began around the same time, UpButler tags your incident "likely upstream" with their incident linked, says so in the alert and the AI report, and tells your on-call agent not to change code.
npx upbutler init finds the dependency from your env var names and packages. The catalog, dependencies and upstream-aware incidents are on every plan, including Free.
# upbutler.yaml
dependencies:
- deepseekcurl -s https://upbutler.com/status/deepseek/status.agent.json{
"schema": "upbutler.upstream-status/v1",
"service": "deepseek",
"verdict": "proceed",
"status": "operational",
"reason": "No incidents reported",
"retryAfterSec": null,
"incident": null,
"probe": {
"state": "up",
"statusCode": 401
}
}Questions
- Is DeepSeek down right now?
- No. As of 2026-10-10 05:09 UTC, DeepSeek is operational. This page reads the status again every 2 minutes.
- Where does this status come from?
- From DeepSeek's own incident feed at https://status.deepseek.com. UpButler reads it once for everyone (not once per visitor) every 120 seconds with conditional requests, and shows it unchanged: incident titles and component names are DeepSeek's words.
- What does UpButler's own DeepSeek check prove?
- Every two minutes UpButler sends one request without credentials to the DeepSeek API edge (api.deepseek.com). Any answer from the edge, usually HTTP 401, shows that DNS, TLS and routing work. It does not prove that authenticated requests succeed, so it can say "reachable" while DeepSeek reports degraded service. It is useful the other way round: when the probe fails before their status page changes.
- How can my agent or app check DeepSeek status?
- Fetch https://upbutler.com/status/deepseek/status.agent.json: a small JSON document with a verdict (proceed, retry, fallback or pause) and retryAfterSec. No key is needed. The same answer is an MCP tool, upstream_status {"service":"deepseek"}, on https://upbutler.com/mcp/public.
- How do I know whether an outage is mine or DeepSeek's?
- Add "deepseek" to the dependencies of your UpButler workspace. When one of your monitors fails while DeepSeek has an incident that began around the same time, your incident is tagged "likely upstream" with their incident linked, and your on-call agent is told not to change code.
More in ai models and tooling
UpButler is not affiliated with DeepSeek. Status and incident text belong to DeepSeek and are read from their public status source; the probe result is UpButler's own measurement.