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

111–120 of 241 posts

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

#111

Post by azalemeth »

xnorswap wrote: post #79
azalemeth wrote: post #24

Earlier quoted context omitted.

I literally just came to HN to ask if I was alone with the acurséd "API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"…"}" greeting me and telling me to get back to using my brain!

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. )

I know that in principle this is true. However, I have seen claude shadow-throttle my ipv4 address (I am behind CGNAT), in line with their "VPN" policy -- so I do not trust it, frankly.

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

#113

Post by fartinmyeyes »

lbriner wrote: post #17

Funny that I just saw this after have "Console temporarily unavailable". I am currently at the stage that: 1) I think Claude Code is very impressive 2) I think pretty much everything else about them is terrible. * Support really poor, raised a ticket last week and have heard nothing back at all * Separation of claude.ai accounts and console accounts is super confusing * Couldn't log into the platform since I had an o…

Of course there's no support, that's like the entire point.

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

#114

Post by jakobloekke »

Fabricio20 wrote: post #90
jakobloekke wrote: post #34

Have anyone found good techniques to get a session out of Claude Code, so that I can point another tool at it and pick up there? This always seems to happen at the worst possible time, after having spent an hour getting deep into something – half finished edits across files, subagents running, etc.

Honest suggestion - ask the agent to figure a compat shim out, the files are jsonl stored at your ~/.claude/sessions you can most likely just reshape it to work on OpenCode or similar, or have a different Claude Code config that points to OpenRouter or other API style endpoint CC supports and then you can swap accounts and it should still work!

I'm trying that out with Cursor now. But it does take some work to get it to the same state with subagents and making sure it understands the state of the progress that was interupted. But it seems worth the time to get a solid skill defined up and running that can do this, given that's it's an almost daily event by now.

Maybe a good candidate for a Claude Routine! "By this time each day, brace for upcoming outage by preparing a comprehensive information package for Cursor to take over your work on active sessions" ...

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

#115

Post by jjcm »

walthamstow wrote: post #84
edf13 wrote: post #7

Seems to be a very regular occurrence starting around this time of day (14:30 UTC)... Claude Code returning: API Error: 500 {"type":"error","error":{"type":"api_error","message":"Internal server error"},"request_id":"---"} Over and over again!

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).

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

#117

Post by SpicyLemonZest »

chollida1 wrote: post #35

Shades of early twitter. Early twitter showed the fail whale as often as it showed tweets and yet it was an unstoppable juggernaut that people kept using.

I can't speak for all CC users, but I genuinely don't care about the downtime as long as it's resolved in an hour or so. It replaces a manual coding workflow that was also prone to random "downtime" when I got annoyed or had a headache, so it's still a net improvement.

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

#118

Post by latentsea »

garff wrote: post #72

Yea, it's peak time. They don't have enough compute. Why do you think they are banning external subscription use. They sell subscriptions. They don't need people to use CC. That doesn't matter. And yet - they won't have people using their service outside of CC. Something is fishy.

Maybe something to do with revenue growth being utterly insane and just not being able to keep up with demand.

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

#119

Post by xnorswap »

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.

Indeed, and also there's a special circle of hell reserved for anyone who dares change the interface on a public API, and forgets about client caching leading to invalid requests but only for one or two confused users in particular.

Bonus points if due to the way that invalid requests are rejected, they are filtered out as invalid traffic and don't even show up as a spike in the application error logs.

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

#120

Post by natpalmer1776 »

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).

Remember when OpenAI wasn’t allowing new subscriptions to their ChatGPT pro plans because they were oversubscribed? Pepperidge Farms remembers.
Post reply on HN