Vendor reports: degradedResolved · vendor status “resolved”Vendor incident feed · inferred

DeepSeek API 性能下降（DeepSeek API Degraded Performance）

Reported by DeepSeek · AI & ML · source last read 4 min ago

Official source (opens in a new tab)
Vendor posted
Aug 19, 2026, 03:10 UTC
When the vendor's feed dated it
Resolved
Aug 19, 2026, 03:10 UTC
Vendor's clock
First seen by Statuswall
Before tracking began
Statuswall's clock
Duration
Not available
This source does not publish reliable durations

Summary

Built from the facts below, no AI

Potential impact, not a confirmed outage of your systems.

What the vendor confirmed

  • DeepSeek reports degraded: "DeepSeek API 性能下降（DeepSeek API Degraded Performance）".[E1, E2]
  • The vendor marked it resolved at 2026-08-19 03:10 UTC.[E3, E7]

What is unknown

  • Which regions are affected: the vendor did not say.[E5]
  • Which components are affected: the vendor did not say.[E6]
  • Whether your own systems are affected: a vendor report cannot tell you; check your monitoring.

Last update in these facts: 2026-08-19 03:10 UTC · summary s1, evidence 0849c1d497afb069

Evidence (7)
  1. E1DeepSeek reports degraded. (vendor) source (opens in a new tab)
  2. E2Vendor title: "DeepSeek API 性能下降（DeepSeek API Degraded Performance）". (vendor) source (opens in a new tab)
  3. E3Vendor status word: "resolved". (vendor) source (opens in a new tab)
  4. E4Vendor posted it: 2026-08-19 03:10 UTC. (vendor) source (opens in a new tab)
  5. E5The vendor did not state which regions are affected. (Statuswall)
  6. E6The vendor attached no components. (Statuswall)
  7. E7Vendor-reported resolution: 2026-08-19 03:10 UTC. (vendor) source (opens in a new tab)

Affected scope

Not stated by the vendor

Components: not stated by the vendor

The vendor's feed gives no region for this incident. It is not assumed to be global.

Potential relevance

DeepSeek is not in your stack. Follow it to see whether reports like this fall inside the regions you use.

Timeline

Vendor times come from the vendor. “Seen by Statuswall” times are when Statuswall noticed a change, which can lag the vendor by a few minutes. Statuswall does not store the vendor's update text; read it on the official page.

  1. Aug 19, 2026, 03:10 UTCVendor posted this incidentVendor time
  2. Aug 19, 2026, 03:10 UTCVendor-reported resolutionVendor time

No changes observed yet. Statuswall began recording changes on incidents in November 2026.