DeepSeek services down nearly 5 hours; 'DeepSeekHarness' account surfaces
Starting at 08:11 Beijing time on October 15, DeepSeek's web, app and API services were partially disrupted, with the official status page showing recovery at 13:04 the same day — a total of 4 hours 52 minutes. Affected services included DeepSeek chat, the DeepSeek V4 Pro API and the DeepSeek V4.1 Flash API (one report instead named a V4.1 Pro API). Third-party monitor StatusGator said it received 86 related reports within 24 hours, and users in Luxembourg, Poland and New York also reported no response or very slow service. Around the same time a Bilibili account named 'DeepSeekHarness' appeared, prompting speculation about a new model or promotion of DeepSeek's open-source agent runtime, though no official evidence supports that link.
For developers and small firms whose business logic runs on a single model API, hours of downtime can mean lost orders and broken commitments — a reminder to build multi-model fallbacks or self-hosted alternatives.