Live data from Hacker News

Claude outage

status.claude.com

191–200 of 204 posts

Re: Claude outage

#191

I didn't even know they had a status page. Claude (with pro subscription) is often so unreliable with regards to connectivity and performance that I'm looking for something more predictable. It randomly fails halfway through a response, sometimes very slow to start, hangs for long periods during a response, and so on. The Claude chat interface can also slow down with long sessions. I sometimes use Claude code which i…

> I'm looking for something more predictable

Google & Gemini, that's where I went due to Anthropic's inability to run reliable production workloads

Re: Claude outage

#192

It's usually down about at least once a day for me anyway. Previously it used to be down during beginning and end of US work times. Now that they've geographically spread out their servers, it's down at random times instead. TBH I'm not so irritated by this. It keeps me grounded, and saves me from being unconsciously outsourcing all the hard work of thought process to AI.

I spend 10h/day in Claude Code and I don't remember the last time it was unavailable to me, maybe a couple of months ago? I suspect this is highly dependant on location and timezone, but at least from within Central Europe it has been smooth sailing (apart from this morning...)

Same. It used to go down all the time but the past couple of months it’s been very stable.

Re: Claude outage

#193

It's usually down about at least once a day for me anyway. Previously it used to be down during beginning and end of US work times. Now that they've geographically spread out their servers, it's down at random times instead. TBH I'm not so irritated by this. It keeps me grounded, and saves me from being unconsciously outsourcing all the hard work of thought process to AI.

I spend 10h/day in Claude Code and I don't remember the last time it was unavailable to me, maybe a couple of months ago? I suspect this is highly dependant on location and timezone, but at least from within Central Europe it has been smooth sailing (apart from this morning...)

Stability has seen a marked improvement since summer. I used to regularly get 429 error codes multiple times per session. Lately it’s been quite awhile since I’ve had it error out or silently exit the chat with no response. I don’t usually code at the peak times though, when it does go down its usually morning time in USA when all of the Europeans are still using it too.

Re: Claude outage

#194

It's usually down about at least once a day for me anyway. Previously it used to be down during beginning and end of US work times. Now that they've geographically spread out their servers, it's down at random times instead. TBH I'm not so irritated by this. It keeps me grounded, and saves me from being unconsciously outsourcing all the hard work of thought process to AI.

I spend 10h/day in Claude Code and I don't remember the last time it was unavailable to me, maybe a couple of months ago? I suspect this is highly dependant on location and timezone, but at least from within Central Europe it has been smooth sailing (apart from this morning...)

Same, it has been stable mostly. Becsusr of the instability before, we have our own scripts protecting it so it continues after failure, for several different failures.

Re: Claude outage

#195
post #128

Earlier quoted context omitted.

It almost never fails via AI Studio though. Also I doubt fails you see really have anything to do with LLM itself, capacity or backend. It's just Google own UIs and apps are almost comically bad.

My theory, beyond their organizational incentive issues, is that Google’s UIs are so pathetically bad because the company is so gung ho about “web first”. The web is a wonderful thing, but it’s set UI development back by decades.

Can you give some examples?

What would have improved UI development instead?

Re: Claude outage

#196

Pro tip: if you pay for Claude, also subscribe to status updates here: https://status.claude.com . you may want to add a rule to filter these to a tag or folder as they can be quite spammy, but it has helped me lots. It tells you which specific models are down and what platforms are down, such as claude web, app, API, etc.

I signed up for a Claude Teams account last week. File uploads were not working anywhere - web, desktop, Android app. As soon as I switched over to a personal account they worked again. Switch back to Team account, broken again with just a cryptic 404 error popping up.

They were broken for a week, I found several people talking about it on Reddit. But no word from Anthropic, no status page info.

I opened a support request, there was no response until 3 or 4 days later when someone messaged to say that it was fixed, and a status page related to it magically appeared.

Re: Claude outage

#197
post #27
post #7

Claude will return soon Claude is currently experiencing a temporary service disruption. We’re working on it, please check back soon. https://status.claude.com/

Wow, that is a lot of not-green for a 30 day status page.

At least they are honest / transparent about it.

Re: Claude outage

#199
post #50

Earlier quoted context omitted.

I’m having trouble getting the AI to outcode me even 1x

Point me your repo, I want to see if AI can improve it.

I mean I can't give you my company code but my GitHub is not difficult to find. That said, I'm a little confused by your offer, because I feel like this doomed to fail because you don't have my context as to what I want improved?

Re: Claude outage

#200

Earlier quoted context omitted.

My theory, beyond their organizational incentive issues, is that Google’s UIs are so pathetically bad because the company is so gung ho about “web first”. The web is a wonderful thing, but it’s set UI development back by decades.

Can you give some examples? What would have improved UI development instead?

I think the decline in UI quality is real, but I don't think the web takes all of the blame. The blame that it does take is due to a sort of mixed bag of advantages and disadvantages: web technologies make it quicker and easier to get something interactive on the screen, which is helpful in many ways. On the other hand, because it lowers the effort needed to build a UI, it encourages the building of low-effort UIs.

Other forces are to blame as well, though. In the 80s and 90s there were UI research labs in indistry that did structured testing of user interactions, measuring how well untutored users could accomplish assigned tasks with one UI design versus another, and there were UI-design teams that used the quantitative results of such tests to deign UIs that were demonstrably easier to learn and use.

I don't know whether anyone is doing this anymore, for reasons I'll metion below.

Designing for use is one thing. Designing for sales is another. For sales you want a UI to be visually appealing and approachable. You probably also want it to make the brand memorable.

For actual use you want to hit a different set of marks: you want it to be easy to learn. You want it to be easy to gradually discover and adopt more advanced features, and easy to adapt it to your preferred and developing workflow.

None of these qualities is something that you can notice in the first couple of minutes of interacting with a UI. They require extended use and familiarization before you even know whether they exist, much less how well designed they are.

I think that there has been a general movement away from design for use and toward a design for sales. I think that's perfectly understandable, but tragic. Understandable because if something doesn't sell then it doesn't matter what its features are. Tragic because optimizing for sales doesn't necessarily make a product better for use.

Post reply on HN