Vendor record
DeepSeek
Checked
Front door check counts and DeepSeek’s own incident posts. Use them to investigate a dependency; neither confirms what happened in your app.
Front door checks
We send a request to a documented DeepSeek endpoint and count the checks that got the answer it is documented to give.
Front door reachable in 2,878 of 2,878 checks with a clear answer, last 30 days, checked every 15 minutes from a single CheckUpstream location.
1 more check gave no clear answer and is not counted.
- Endpoint checked
- api.deepseek.com
- Scope
- apiNo vendor region
- First check in this window
- Latest clear answer
Checks 15 minutes apart cannot see disruptions shorter than that. A check that reached the front door does not show that every DeepSeek product, region or your app worked.
How we count front door checksDeepSeek says
Incident posts from DeepSeek’s status page, with its titles, impact levels and times. They say what DeepSeek chose to post, not what reached your app.
A closed record shows when our record closed. Some older records closed when a post left the status page, without a resolution post from the vendor.
0
incidents DeepSeek posted, last 30 days
Most recent records · all dates
DeepSeek 网页/API不可用（DeepSeek Web/API Service Not Available）
CriticalDeepSeek’s postStarted, per DeepSeek
Closed in our record(38m)
【已恢复】DeepSeek 网页/API 性能异常（[Resolved]DeepSeek Web/API Service Degraded Performance）
MinorDeepSeek’s postStarted, per DeepSeek
Closed in our record(16m)
DeepSeek 网页/API 性能异常（DeepSeek Web/API Service Degraded Performance）
MajorDeepSeek’s postStarted, per DeepSeek
Closed in our record(17m)
DeepSeek API 异常（DeepSeek API Abnormal）
CriticalDeepSeek’s postStarted, per DeepSeek
Closed in our record(1h 7m)
DeepSeek Web/APP 快速模式性能异常（DeepSeek Web/APP Instant Mode Performance Abnormal）
MinorDeepSeek’s postStarted, per DeepSeek
Closed in our record(3h 30m)
4 older records
DeepSeek 网页/API 性能异常（DeepSeek Web/API Service Degraded Performance）
MinorDeepSeek’s postStarted, per DeepSeek
Closed in our record(20m)
DeepSeek 网页/API 性能异常（DeepSeek Web/API Service Degraded Performance）
MajorDeepSeek’s postStarted, per DeepSeek
Closed in our record(1h 13m)
DeepSeek 网页/APP 服务异常（DeepSeek Web/APP Service Abnormal）
CriticalDeepSeek’s postStarted, per DeepSeek
Closed in our record(10h 17m)
DeepSeek 网页/APP 服务异常（DeepSeek Web/APP Service Abnormal）
CriticalDeepSeek’s postStarted, per DeepSeek
Closed in our record(1h 50m)
Your code, your dependencies
See which of your code paths call DeepSeek
Connect GitHub or GitLab to find where your public or private repository uses DeepSeek. Review each match and your alert settings.
Free to start. No credit card.
Use this record on your site
Add DeepSeek status to your page.
Choose the format your page supports, then copy the code. Badges show the recorded vendor status; they do not establish impact on your app.
Frequently Asked Questions
Is DeepSeek currently down?
DeepSeek's latest recorded status is Operational. Check the timestamp and linked source at the top of this page. A vendor status report does not establish whether your application was affected.
When did DeepSeek last have an outage?
The most recent closed incident record began 161 days ago and spans 38 minutes. The vendor reported a complete outage. Closure may reflect a disappeared post or an expired tracking period; it does not confirm vendor or application recovery. Check the dated history and source links.
Does CheckUpstream publish an uptime percentage for DeepSeek?
No. CheckUpstream checks DeepSeek’s front door every 15 minutes and publishes how many checks reached it over the last 30 days, with the endpoint checked. Checks 15 minutes apart cannot see disruptions shorter than that. A percentage would claim more than the checks can show.
How do I monitor DeepSeek in production?
Create your account, connect GitHub or GitLab and choose a public or private repository. Review the vendor matches and your alert settings. Available notification channels and history depend on your plan.
How does CheckUpstream track DeepSeek?
This record separates vendor-reported incidents from independent checks. Sources and coverage vary by vendor: review the linked source, check time and measurement scope. Neither kind of evidence establishes SLA credit eligibility.