Live data from Hacker News

Claude.ai unavailable and elevated errors on the API

status.claude.com

111–120 of 277 posts

Re: Claude.ai unavailable and elevated errors on the API

#111

The spend at my organization has reached beyond the $200,000 per month level on Anthropic's enterprise tier. The amount of outages we have had over these past few months are astounding and coupled with their horrendous support it has our executive team furious. its alot of money to be spending for a single 9 of reliablility.

> has our executive team furious And yet they will continue to spend wheelbarrows full of money with Anthropic because they want so badly to reach the point where they can fire you.

I think there is alot of baseless fury behind your words, but my regular interactions with my leadership dont lead me to think they have the end goal of replacing labor. We're blessed to have leadership with technical backgrounds, so the tools are regarded more as significant intelligence enhancers of already exceptionally smart engineers, rather than replacements.

Doesnt seem to us to be wheelbarrows of money, when you consider the average AWS/Azure bill.

Re: Claude.ai unavailable and elevated errors on the API

#112

If this can happen to Anthropic, imagine all the companies building on top of Claude Code for live products. Hopefully the industry is learning that competent problem solving human engineers are still very much needed when you have increasingly deceptive non-deterministic genies running your production stack.

Maybe it will push companies to run them locally.

Re: Claude.ai unavailable and elevated errors on the API

#113
post #70

Earlier quoted context omitted.

Why would Github be a guide? It's also terrible, but it's a radically different stack from an unrelated company

GitHub, along with MSFT in general, have massive copilot mandates where workers are being shamed into using slop tools to fix serious on-going issues. GitHub seems wholly incapable of resolving their issues: money isn't a problem, talent isn't a problem, but business leadership is definitely a major problem. Look at how other companies are suffering massive outages due to LLMs too like AWS and Cloudflare. Two compani…

[deleted]

Re: Claude.ai unavailable and elevated errors on the API

#114
post #95

Earlier quoted context omitted.

yea just buy 300k worth of hardware and bob's your uncle

It was pretty hard to justify the purchase to the board but we got a decent deal from a nearby data-center (~15% discount). Thankfully, it's fixed cost, its an asset we can use for our taxes, and it will survive for years to come. The only thing we have to work on is maintenance as well as looking into some renewable energy options. We're also looking into how to do some secure cost sharing with this so that all peop…

Sorry, didn't mean to be dismissive, I was just being a dickhead needlessly.

I actually respect this a ton, good work.

Re: Claude.ai unavailable and elevated errors on the API

#115
post #71

Earlier quoted context omitted.

Let’s ask AI

You're absolutely right! AI could be very helpful in this situation! Oh no wait... the outage is with out AI itself, so how can AI help? Allow me to re-evaluate. Fublutenuating... Yes, let's ask AI! Oh no wait... the outage is with AI itself, I already correctly identified this above. Bubbluating... It seems you will have to rely on your engineering skills to solve this problem yourself, ie, you're cooked! I will aut…

Sorry AI is not responding, enable /fast to activate per-request pricing.

No!

Comboculating...

I apologize for the misunderstanding, I have deleted your project. I am sorry, would you like me to restart everything from scratch ?

Re: Claude.ai unavailable and elevated errors on the API

#117

If this can happen to Anthropic, imagine all the companies building on top of Claude Code for live products. Hopefully the industry is learning that competent problem solving human engineers are still very much needed when you have increasingly deceptive non-deterministic genies running your production stack.

[dead]

Re: Claude.ai unavailable and elevated errors on the API

#118
post #57
post #39

Earlier quoted context omitted.

Truly! As someone who's worked with HPC and GPUs in a scientific research context, trying to get a service like this to work reliably is a different ballgame to your usual webapp stack...

Can you speak a little more to this? I'm curious what kind of parameters one must consider/monitor and what kind of novel things could go wrong.

My guesses are:

hardware capacity constraints is going to be the big one

Effective caching is another, I bet if you start hitting cold caches the whole things going to degrade rapidly.

The ground is probably shifting pretty rapidly.

Power users are trying to get the most out of their subscriptions and so are hammering you as fast as they possibly can. See Ralph loops.

Harnesses are evolving pretty rapidly, as well as new alternatives harnesses. Makes the load patterns less predictable, harder to cache.

The demand is increasing both from more customers, but also from each user as they figure out more effective workflows.

Users are pretty sensitive to model quality changes. You probably want smart routing, but users want the best model all the time.

Models keep getting bigger and bigger.

On top of that they are probably hiring more onboarding more, system complexity and codebase complexity is growing.

Re: Claude.ai unavailable and elevated errors on the API

#119

The spend at my organization has reached beyond the $200,000 per month level on Anthropic's enterprise tier. The amount of outages we have had over these past few months are astounding and coupled with their horrendous support it has our executive team furious. its alot of money to be spending for a single 9 of reliablility.

We are spending the equivalent of 32 monthly software engineer salaries on Claude per month.

Our expense is roughly around 12.3 software developers when you break it down across all people related expenses. But we've spent alot of time and energy prior to this focusing on our ability to measure our software development output across multiple teams. The delivery improvements are not evenly applied across all teams, but the increases that we have seen suggest a better ROI than if we had hired 12 developers.
Post reply on HN