Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Elevated errors on Claude.ai, API, Claude Code

claudestatus.com

Post reply on HN
Print view View original

211–220 of 241 posts

Re: Elevated errors on Claude.ai, API, Claude Code

#211

Post by iainmerrick »

darkwater wrote: post #89
xnorswap wrote: post #79

Earlier quoted context omitted.

500-series errors are server-side, 400 series are client side. A 500 error is almost never "just you". ( 404 is a client error, because it's the client requesting a file that does not exist, a problem with the client, not the server, who is _obviously_ blameless in the file not existing. )

> A 500 error is almost never "just you". I know you added the defensive "almost" but if I had a dollar each time I saw a 500 due to the session cookies being sent by the client that made the backend explode - for whatever root cause - well, I would have a fatter wallet.

Depending on what you mean by "made the backend explode", that is a server error, so 500 is correct!

Bad input should be a 4xx, but if the server can't cope with it, that's still a 5xx.

Re: Elevated errors on Claude.ai, API, Claude Code

#213

Post by paulddraper »

jjcm wrote: post #115
walthamstow wrote: post #84

Earlier quoted context omitted.

US Pacific comes online while London is still working and they can't handle it. $380bn valuation btw.

No amount of valuation can fix global supply issues for GPUs for inference unfortunately. I suspect they're highly oversubscribed, thus the reason why we're seeing them do other things to cut down on inference cost (ie changing their default thinking length).

A. These aren’t rate limit errors from the API.

B. Everything is down, even auth.

Re: Elevated errors on Claude.ai, API, Claude Code

#214

Post by anonyfox »

boredtofears wrote: post #190
mchusma wrote: post #183

Anthropic has been avoiding the hard thing, but they just need to do SOME kind of pricing thing here to shift demand. I expect there is just no amount of tricks that can handle the few hours at peak load. They need "surge pricing". This seems reasonable surge pricing approach to me: 1. Implement surge pricing for everyone for the peak 2 hours of the day if possible. 2 hours you can work around, 5 hours is too hard. 2…

Only on HN will your customers not only tolerate your product once you’ve reached market saturation and started enshittifying it, they’ll write you a whole guide on how to do it!

its more like the people with the highest disposable money want other users that interrupt their experience to back off so its not bothering them.

Re: Elevated errors on Claude.ai, API, Claude Code

#215

Post by blueline »

ai-x wrote: post #158
AndroTux wrote: post #139

Earlier quoted context omitted.

I can't sign in. We're not at capacity for OAuth servers or relational databases. This proves that vibe coding your infrastructure is a bad idea.

If you have this view in 2026 April, you are going to have a bad time

If only the energy posting the 5 trillionth "ngmi" meme could be applied to achieving one 9 of uptime for claude

Re: Elevated errors on Claude.ai, API, Claude Code

#216

Post by bigbadfeline »

dsr_ wrote: post #160
ai-x wrote: post #101

Earlier quoted context omitted.

This precisely justifies Anthropic's market cap to be higher.

Demand at an unsustainably low price does not imply demand at a sustainable price.

I'm pretty sure ai-x writes sarcasm and skips the /s for pure fun. Personally, I'm amused and I like what he's doing. Others have done it before him though, it's not a new trick.

Re: Elevated errors on Claude.ai, API, Claude Code

#217

Post by bruckie »

hirako2000 wrote: post #138
andai wrote: post #124

Earlier quoted context omitted.

Wouldn't that be good? I remember back in the day you could only get Gmail thru an invite, it was an awesome strategy. "Currently closed for applications" creates FOMO. They'd just need to actually get the GPUs in relatively short supply. They could do it in bursts though, right? "Now accepting applications for a short time." I'm not an internet marketer but that sounds like a win win to me. People feel special, they…

In the case of Gmail that was fake scarcity. In the case of Anthropic is fake availability. Sam Altman explained the idea is to scale the thing up, and see what happens. He hadn't claimed to offer a solution to the supply problem that would unfold.

Are you sure it was fake scarcity for Gmail? IIRC they did it because they were worried about systems falling over if it grew too fast, and discovered the marketing benefits as a side effect.

Re: Elevated errors on Claude.ai, API, Claude Code

#218

Post by bulbar »

hirako2000 wrote: post #135
scratchyone wrote: post #132

Earlier quoted context omitted.

maybe, but the response to GPU shortages being increased error rates is the concern imo. they could implement queuing or delayed response times. it's been long enough that they've had plenty of time to implement things like this, at least on their web-ui where they have full control. instead it still just errors with no further information.

Coding is a problem solved. Claud writes the code. I edit it. I code around it. Engineer roles dead in 6 months.

Because of the context I would think this is sarcasm, but I am not sure.

Re: Elevated errors on Claude.ai, API, Claude Code

#219

Post by malfist »

arcanemachiner wrote: post #186
pixel_popping wrote: post #159

Earlier quoted context omitted.

2 days to fix a major issue where we can't login from any sort of web terminal? (even typing manually doesn't work as `n` char auto-exit the frame). All kind of CI/CD pipelines are broken if you were delogged for any reason.

Did you try downgrading?

That....that doesn't make sense. Why is the response to someone complaining that anthropic takes too long to fix major bugs _in their software_ be "well, did you fix it yourself?"

Re: Elevated errors on Claude.ai, API, Claude Code

#220

Post by AlecSchueler »

jjcm wrote: post #115
walthamstow wrote: post #84

Earlier quoted context omitted.

US Pacific comes online while London is still working and they can't handle it. $380bn valuation btw.

No amount of valuation can fix global supply issues for GPUs for inference unfortunately. I suspect they're highly oversubscribed, thus the reason why we're seeing them do other things to cut down on inference cost (ie changing their default thinking length).

> thus the reason why we're seeing them do other things to cut down on inference cost (ie changing their default thinking length).

The dynamic thinking and response length is funny enough the best upgrade I've experienced with the service for more than a year. I really appreciate that when I say or ask something simple the answer now just comes back as a single sentence without having to manually toggle "concise" mode on and off again.

Post reply on HN