Live data from Hacker News

Elevated errors on Claude.ai, API, Claude Code

claudestatus.com

171–180 of 241 posts

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

#173
A few hours ago I noticed a considerable decline in code quality. It seemed the model got downgraded so I switched to codex. Anybody else noticed this? It starts to switch from deep reasoning and trying to fully grasp architectural changes to trying to solve things on a very adhoc basis. Maybe that's just my imagination or maybe that's Anthropic trying to balance the load before being fully overloaded.

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

#175
post #144

Are they using Claude Code to author all of these systems as well?

Yes, as far as I've been told, they are. I imagine (hope) they run on a completely isolated version of it though.

Well, I suppose that explains things.

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

#177

I think a cheat code here is to route your requests to GCP's Vertex AI, which has stronger uptimes. Can use it as a fallback or main provider. Caveats: 1) May not be economic for those on flat-rate Anthropic subscription plans 2) I work at Google.

does google actually host anthropic models themselves?? surprised anthropic allows that, given how notoriously crazy they are about distillation or weight leaks or any hints of their models being used in the wrong way.

Yes, we host it ourselves, acting as the data processor which can be important for enterprise customers.

From developer experience, hosting them ourselves allows us to take advantage of our unique infra and deliver fastest time to first tokens of the providers.

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

#178
post #68
post #23

91% uptime for Claude Code over the last 30 days. Is that accurate?! I'm not a CC user but that seems awfully low.

I guess it depends on who you ask, Anthropic says 99.26%: https://status.claude.com

They compute as total minutes down as a fraction of total time. What this means is that being down, say, 55min during peak-use counts the same as being down 55min when nobody is trying to use it. And congruently it counts being up when nobody is trying to use it as the same as being up when everyone is trying to use it.
Post reply on HN