DeepSeek reported "DeepSeek Web/Chat Degraded Performance" on its status page at 2026-11-14 16:53 UTC. DeepSeek Chat service had degraded performance. DeepSeek reports that the incident is resolved. The outage lasted 22 minutes.

DeepSeek lists these components: Chatservice.

When did the incident start and end?

It started at 2026-11-14 16:53 UTC and ended at 2026-11-14 17:16 UTC. It lasted 22 min.

How do I get alerts for DeepSeek?

Subscribe to the DeepSeek live feed over RSS or in Slack, or add the outages.live MCP server to your coding agent.

Where does this information come from?

From the official status page of DeepSeek. outages.live reads it every few minutes and keeps every update. A language model writes the summary from those updates.

DeepSeekIncident ·

DeepSeek Web/Chat Degraded Performance

ResolvedOfficial update

DeepSeek Chat service had degraded performance. DeepSeek reports that the incident is resolved. The outage lasted 22 minutes.

State

Resolved

Started

Lasted

22 min

Worst impact

Degraded

Timeline

2 updates

16:5316:5917:0517:1017:16

DegradedUpdate postedTimes in UTC

Investigating

22 min 100%

Updates

Times in UTC

As posted by DeepSeek

Resolved

The incident has been resolved and service has been restored.

Investigating

The issue is being investigated to identify the cause.

Affected components

Chatservice

DeepSeek in the last 90 days

Full history

90 days agoToday

Incidents in 90 days

Days with an incident

Median duration

19 min

This incident

1.2× the median

How long each incident lasted, on the day it started. The outlined bar is this incident.

4 h 52 min

median 19 min

90 days agoToday

Other DeepSeek incidents

All incidents

DeepSeek·DeepSeek Web/API Partially Unavailable

DeepSeek reports a partial outage that affects the DeepSeek V4 Pro API Service, DeepSeek V4.1 Flash API Service, Chat Service, and Search Service. DeepSeek implemented a fix and monitored the results. The incident is resolved, and it lasted 45 minutes.

Resolved

DeepSeek·DeepSeek Web/API Partially Unavailable

DeepSeek reported a partial outage on the DeepSeek V4.1 Flash API Service, the Chatservice, and the DeepSeek V4 Pro API Service. DeepSeek reported that the incident is resolved. The outage lasted 110 minutes.

Resolved

DeepSeek·DeepSeek API Degraded Performance

The incident has been resolved and service has been restored.

Resolved

DeepSeek·Search service error

The incident has been resolved and service has been restored.

Resolved

DeepSeek·DeepSeek Web/API Partially Unavailable

The incident has been resolved and service has been restored.

Resolved

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.

Prompt

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.live/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.

RSS

https://outages.live/feed.xml?providers=deepseek

Slack

/feed subscribe https://outages.live/feed.xml?providers=deepseek

FAQ

Go from tracking outages to fixing production issues with Polylane.

Try Polylane