“DeepSeek Crashes” became a hot topic on the evening of March 29th, quickly spreading across social media platforms with news of its widespread service abnormalities.
Starting from 10 p.m. on March 29th until 7 a.m. on the 30th, DeepSeek experienced a large-scale disruption in its services. Users reported frequent occurrences of “server busy” messages and even complete service interruptions on both the website and the app. This issue escalated within half an hour, causing it to trend on social media and sparking discussions across the internet.
As reported by “Tech-Quick”, as of 7 a.m. on the 30th, the platform’s services had not fully recovered. Users continued to encounter “service busy” notifications on both the website and mobile app. Core functions such as deep thinking, long-text reasoning, and code generation were severely restricted or rendered completely unusable.
Many users expressed frustration as ongoing tasks such as writing papers, debugging code, or incomplete projects were severely disrupted due to the service interruption. Some users even reported lost content.
DeepSeek has yet to release an official statement through official channels regarding the cause of the malfunction, progress in fixing the issue, or any potential compensation plans for affected users.
This is not the first time such problems have occurred on the platform. On March 10th of this year, DeepSeek services experienced a similar disruption, with users facing frequent “server busy” messages on both the website and app, causing widespread usability issues. This incident also rapidly climbed the trending charts within half an hour.
An investigation by “The Jiangnan City News” at the time confirmed the issue, where their journalists encountered the same message of “service area busy, please try again later” after inputting information into the app.
In May of last year, DeepSeek also faced server crashes due to a surge in traffic, resulting in not only service unavailability but also the loss of historical data records. Once again, this incident led to related discussions trending on Weibo.