Sigh, who can handle this?
On August 24, Claude crashed three times in a row.
Anthropic's status page lit up with three glaring red lights that day, and the official account jumped out three times to announce that service had been fully restored.
But each time the page just turned green, cries of agony were still all over X, with a large number of users still shouting that they couldn't open it on their end.
This was the 13th day in August that Anthropic left an incident record.
Goodness, only 24 days have passed this month.
And you're telling me Claude has been lying in bed for more than half of them.
One Reddit user even complained that he had an automated process that ran hard for nine hours, only to be completely cut off during this major outage, rendering all the work wasted.
529, the Kitchen Caught Fire
When the failure fully erupted, the error code 529 Overloaded popped up on users' screens in unison.
Those familiar with APIs know 429, which is rate limiting, akin to a restaurant telling you to order slower, please wait.
Whereas 529 represents the entire system being completely overloaded, equivalent to the restaurant directly coming out to notify you, "Sorry, our kitchen is on fire."
According to the status page records, this fire burned from 12:50 PM Beijing Time on August 24 all the way to 3:36 PM, tormenting for nearly three hours.
Twenty-one minutes after the alarm sounded, the officials were still quite confident, saying the root cause had been identified.
And then? Then there was no more. Anthropic neither disclosed the technical reason nor provided an estimated time for full recovery.
The list of affected victims stretched long.
Mythos 5, Fable 5, Opus 5, and Opus 4.8 all went down together; claude.ai, API, Claude Code, and Cowork all sounded the alarm.
In the end, only Console and Claude for Government managed to escape unscathed.
Basically, the entire Claude tech stack was breached in this wave.
Repeated Sit-ups, Red Then Green Then Red
The more absurd plot was still to come. Each time the official announcement said repairs were complete, it could turn around and die on you again.
The model-wide errors lasted for nearly three hours, then recovered.
But holding on until just past midnight on the 25th, the login system crashed again, claude.ai and Claude Code subscriptions were all severely affected, struggling for six minutes before catching their breath.
Before things could quiet down for a few hours, it crashed again at 4 AM sharp, this time for a solid eight minutes.
A monitoring bot specifically watching Claude's login status, isclaudedownbot, posted a tweet at 4:11 AM. The entire tweet had no nonsense, just one word.
Yes.
You really can't say this emotionless broadcast wasn't precise to the extreme.
Anthropic's official statement was written with the usual grace, saying service had been fully restored on Claude.ai, Claude Code, and Claude API, that the company knew how much everyone relied on Claude, and thanked everyone for their patience while the team investigated.
Despite such words, a green status page absolutely does not mean your account is usable.
The tweet posted by user elstar that day, reading between the lines, no longer sounded like a complaint, but more like a cry for help.
But the actual situation was that the official status did indeed show everything was normal at that moment, yet residual authentication and frontend issues were causing some unlucky users' settings, usage, and skills pages to turn directly into glaring white screens.
Everything normal and white-screened pages, these two contradictory things, coexisted at this very moment.
Until late at night, there were still unlucky souls roaring online, "Claude down again."
Outages Are Clocking In Like Crazy
And this day was not at all lonely.
Third-party monitoring service StatusGator shows that from January 2026 to now, Claude has accumulated 184 outage records.
Keep in mind, it's only August.
And scrolling back through the status page, the outage logs for the entire month of August are densely packed like a schedule.
Two incidents exploded on the 20th, one each day without fail from the 19th to the 16th, Fable 5 directly crashed for about four hours on the 15th, and on the 14th, it went completely wild with three incidents in one day, followed unsurprisingly by one each on the 13th and 12th.
The most severe among these was the one on August 5th, crashing for a pitch-dark 7.5 hours.
The error message users saw on their screens at that time read: "Due to unexpected capacity constraints."
Compute Depletion, Who Took My Reasoning IQ
The phrase "capacity constraints" appeared in error messages more than once this month.
And on X, another phrase was repeatedly mentioned: "ran out of compute."
One developer put it bluntly: Opus 4.6 used to be so smart it made your scalp tingle. Later, it seemed they completely ran out of compute power and then nerfed everything.
User Eason also felt that Claude was experiencing an unprecedented, most severe intellectual degradation. Opus 5 was basically unusable, and they had even reverted to using Opus 4.8.
Actively reverting to an older version—such an operation is indeed rare in the fiercely competitive AI circle.
Of course, these are at best just users' metaphysical feelings, lacking ironclad proof.
So someone ran a comparative test pitting the two against each other.
For the same challenging task, Opus 5 on xHigh setting took a full hour to slog through, while switching to another company's comparable model on the same setting finished in 15 minutes.
A whole 4x difference, making one gasp in shock.
Even AMD's AI Director, Stella Laurenzo, personally got involved, pulling out all 6,852 Claude Code sessions from her team.
The resulting chart revealed a cliff-like drop in the curve.
In late January, the model's thinking depth was still about 2,200 characters. By early March, it had dwindled to a pitiful 560 characters, a plunge of 75%.
An even more thought-provoking coincidence was that during this same period, Claude Code's thinking content began to be quietly hidden from users. Within just one week, the proportion hidden went from 1.5% all the way to 100%.
In other words, while the model visibly became dumber, you couldn't even see how exactly it became dumber anymore.
Agent Burned Nine Hours, Status Page Logged a Few Minutes
Anthropic's own 90-day availability rates posted on its official website read: claude.ai 99.33%, API 99.43%, Claude Code 99.35%.
At first glance, it looks like a perfect report card. But the passing grade for enterprise-level services is 99.9%.
What's more, in the classical internet era when the metric of availability was born, a service interruption only meant a webpage wouldn't open; you could just refresh and get back to work, losing only those few seconds of refreshing.
However, for an Agent, once a long task is interrupted, what's lost is never just the minutes of the interruption itself, but also all the time, context, and compute it had already burned through before. This ledger, the status page simply cannot record, nor can it.
To this day, Anthropic still hasn't explained what exactly happened during those three hours on August 24.
And this August, which has been red for 13 days, still has seven days left.
References:
https://x.com/ns123abc/status/2091784366519193852
This article is from the WeChat public account "新智元", author: ASI启示录, editor: 摩西
