DeepSeek Web/API Partially Unavailable
The incident has been resolved and service has been restored.
The latest update from DeepSeek.
State
Resolved
Started
18 d ago
2026-10-15 00:11 UTC
Lasted
4 h 52 min
until 2026-10-15 05:04 UTC
Worst impact
Major outage
Timeline
6 updatesInvestigating
55 min 19%
Identified
3 h 43 min 76%
Monitoring
14 min 5%
Updates
Times in UTCAs posted by DeepSeek
The incident has been resolved and service has been restored.
A fix has been implemented and the results are being monitored.
The cause has been identified and a fix is being implemented.
The cause has been identified and a fix is being implemented.
The issue is being investigated to identify the cause.
The issue is being investigated to identify the cause.
Affected components
3DeepSeek in the last 90 days
Full historyIncidents in 90 days
7
Days with an incident
6
Median duration
14 min
This incident
21× the median
Other DeepSeek incidents
All incidentsDeepSeek·DeepSeek API Degraded Performance
The incident has been resolved and service has been restored.
DeepSeek·Search service error
The incident has been resolved and service has been restored.
DeepSeek·DeepSeek Web/API Degraded Performance
The incident has been resolved and service has been restored.
DeepSeek·- DeepSeek Web Partially Unavailable
The incident has been resolved and service has been restored.
DeepSeek·DeepSeek Web/API Degraded Performance
The incident has been resolved and service has been restored.
Follow DeepSeek
Your coding agent knows when DeepSeek is down, and tells you when a failure is theirs, not yours. You can also get DeepSeek incidents in a feed reader or in Slack.
Install the outages.live MCP server, so that when something breaks you can tell if the cause is a provider we depend on and not my code. It reads the official status pages of cloud, AI, payment and developer providers and gives you their incidents as MCP tools.
Add it as a remote MCP server named "outages" at https://outages.cc/mcp (Streamable HTTP, no authentication), with your CLI command or your MCP config file.
Then:
1. Make sure it connects and shows the tools get_provider, list_feed and send_feedback.
2. Call get_provider with "deepseek" and tell me if DeepSeek has a problem right now.
3. From now on, when a call to a third-party service fails or becomes slow, call get_provider for that service before you change my code.Paste this into any coding agent. It adds the server with its own MCP setup.
https://outages.cc/feed.xml?providers=deepseek/feed subscribe https://outages.cc/feed.xml?providers=deepseekFAQ
Go from tracking outages to fixing production issues with Polylane.
Try Polylane