alt Hacker NewsElevated errors on claude.ai, Claude Code, and platform.claude.com
Comments
The odd thing about these outages is that when they become so big that everyone is impacted then the severity almost drops, since everyone is impacted and thus just shrugs their shoulders.
Many Claude session suddenly require a re-login, which first worked but now gives
OAuth request failed Temporarily unable to authenticate. Please retry.
Can this be fall-out from the Microsoft outage?
Let the weekend start! Tech sabbatical is kinda enforced now =D
Is Claude on Azure? GitHub also seems affected, could seem like all of this is related to the huge Microsoft outage
Notably this brought MCPs down, which they call Connectors on the status page. Which impacts business customers using claude to access SaaS apps, not just coders.
Reminds me of when we built Facebook apps and were at the whim of the platform.
Is there indication this is really a separate issue or just Claude not being able to reach Microsoft Entra for whatever periodic requests confirm the user is authenticated (and maybe this page even simply being automatic reflection that those requests are errorring frequently)?
Are people who don't use M365 experiencing issues here?
By "elevated errors", do they mean the system returns an error code, or the AI makes more mistakes?
I didn't realized that, i'm lucky this happened during my sleep time. Thanks for sharing!
Previous outages of GitHub, AWS and so on didn't get that much traction.
I guess anecdotal but people nowadays are incredibly addicted to LLMs, to the point where they cant or dont want to work when there's an outage
Yep, one instance can't connect, and one instance seems to have crashed but is pretending to keep working (Toulouse, France)
3 minutes later... I can reconnect, and the "crashed" instance woke up.
> A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery. > Nov 13, 09:58 UTC
Our application logs show zero errors from their API today
Yeah got 403 cloudflare attention required, but was able to finish session. Switching to Codex for a while
It is back now
Maybe Cloudflare related? There were some (possibly unrelated) outages on CF around the same minutes
Apparently it was resolved in 2 hours.
That seems faster than usual, compare to Outlook (down for a day) and GitHub. It's still embarrassing for a heavily-relied service, but better, and I wonder if Claude (or another LLM) helped diagnose and fix the outage?
Seeing the same errors. Might be linked to Microsoft.
I looked at the outage notice
https://status.claude.com/incidents/nn11wk485zfn to be clear
I was using Claude Code Friday morning, and I wanted to know what the issue was and how I might have been effected
I do not know, after reading their notice
All the more reason to hurry up our move away from Anthropic.
Claude Code is good. But if when it has problems it issues notices like this, being good is not enough
If they expect to be as valuable as they seem to feel entitled to, they must do better
What a shame
Still down (Italy) from about 30mins ago.
it happened right after the upgrade of the desktop app. Same for anyone, or was it coincidence?
AGI is here
Yep Dubai/Germany
do they have infrastructure on azure?
This stuff is so new and wild west at the moment that in our company everyone is using it completely differently. 20% of the devs have 30x output and are doing everything with Claude, 10% won't touch it, the rest are in some weird in between where they use it for some things and not other things which it is perfect for. We have managers that suggest just going back to doing it by hand when there are outages, which is the most laughable thing in the world to me now. It is incredible to watch this miracle tech hit so fast and have everyone's understanding of it be so different across the board.
Well...
what a friday, huh?
currently running a Claude model through github copilot CLI. Pretty odd given the two ongoing outages.
faaaaahhhh
works now!
[flagged]
[flagged]
[flagged]
[dead]
[dead]
[dead]
I used claude for the first time in months yesterday (have been using codex, ran out of resets this week). I had picked up from general consensus comments that 5.5 had fixed the opus 5 issues, but that's far from the case. Its "personality" is still smartass, know it all, and whiny. It disregards specifications in tickets if it thinks it knows better. It complains about the size of tasks when it reads task descriptions. I've gotten used to codex, which just jumps in and does stuff (which of course carries its own set of issues). I have no love for Altman, but their product is still better at the moment.
If Claude is down and can't be used to debug outages in Claude, is it recursive self-sabotage?
And this company, about to start its IPO, wants to make the majority of the world's office workforce dependent on them when they can't even handle their current load.
This explains why I was logged out forcefully. Funnily enough, due to the Microsoft outtage, I also cannot log back in.
Well, it was my employers wish that we devs incorporate more AI, and we did. It's their misfortune now.
It's catch 22 now. This is related to MS outage, and MS can't fix it now since all their Claude Code agents aren't working. Long weekend!
Going the other way, Claude duet has just gone into invite beta, people get 3 invites and inviting someone else gives them a month of pro, I saw on Twitter a link every minute about 3 hours ago (can't use because I'm Australian) I wonder if they are just getting DDoSed from their own invite spam?
Claude, Outlook. Need GitHub to join in for the trifecta.
if you want to keep working, Grokbot offers which feels like half the intelligence and half the quota for the same price.
Looks like when people said "If you don't get on the AI train you'll be left behind" they were right. They're all getting a day off and I'm not.
(I know CC =/= AI, but put that aside for the sake of the joke)
Trillion dollar company going public next week ladies and gentleman!
Depending on what your job is, this is either the adult equivalent of a snow day or some of the greatest stress in a long time.
I have experienced, half a decade ago during some more frequent but less lengthy O365 errors that there are some higher ups who get when this is not something you can fix and some you very much can't. Wishing strength to any "but it's our mail" and "but we bought the Claude" meetings that happen today.