Elevated errors on Claude.ai, API, Claude Code
141–150 of 241 posts
Re: Elevated errors on Claude.ai, API, Claude Code
#142- downdetector comment
Re: Elevated errors on Claude.ai, API, Claude Code
#143OpenAI is very good in terms of not having as much outages as Anthropic, but almost all products except Codex and the pro model is unimpressive, anthropic has the opposite situation.
Re: Elevated errors on Claude.ai, API, Claude Code
#144Re: Elevated errors on Claude.ai, API, Claude Code
#145Earlier quoted context omitted.
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).
Their issues seem to extend well beyond inference into services like auth.
Re: Elevated errors on Claude.ai, API, Claude Code
#146Are they using Claude Code to author all of these systems as well?
Re: Elevated errors on Claude.ai, API, Claude Code
#147Re: Elevated errors on Claude.ai, API, Claude Code
#148Earlier quoted context omitted.
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).
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.
Re: Elevated errors on Claude.ai, API, Claude Code
#149Funny how we all come to HN when the status page is lagging behind. HN is truly the real-time status page
Re: Elevated errors on Claude.ai, API, Claude Code
#150Earlier 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.
I've been experiencing a good amount of delays (says it's taking extra time to really think, etc), and I'm using during off-peak time.