I'm feeling a bit sorry for Anthropic. This last month must be very tough on them.
Oh no won’t someone please think about the trillion dollar corporation!
Arent they just on the hook for trillion dollars
Claude.ai and API unavailable [fixed]
51–60 of 129 posts
Re: Claude.ai and API unavailable [fixed]
#52Between GitHub and Claude, it seems Eternal December[0][1] is upon us. [0]I say December, because that's around the time the models got good enough that non-AI folks started to notice. [1] https://en.wikipedia.org/wiki/Eternal_September
GitHub is a long running business with a mature software stack running into scaling issues while they move to Azure and becoming Microsoft-ified. Claude is a new company in a new market with an extremely fast growing userbase running relatively novel AI infrastructure with a business model they are still figuring out.
I don't really blame Anthropic here.
Re: Claude.ai and API unavailable [fixed]
#53Re: Claude.ai and API unavailable [fixed]
#54I built a hangout space to chill out in and chat to others while Claude is down (which is happening wayyy more often): https://clawdpenguin.com
There's a live Claude status board in the corner so you know when it's time to get back to work.
Re: Claude.ai and API unavailable [fixed]
#55I don't really mind hopping between claude/codex/glm/kimi except I don't know a good way to resume as session across agent harnesses. Normally I'd just have it write out what it's doing to a file, if I need to transfer context, but if it goes down mid-session that's a no-go. I think people have built tools for this, and of course you could reasonably vibe one yourself, but I don't really trust something like that to…
kilocode allows you to switch between models mid session!
Re: Claude.ai and API unavailable [fixed]
#56This is a tough moment. Claude is simultaneously becoming substantially more expensive, substantially less reliable (single 9 of reliability), and substantially less performant. It's really hard to justify the cost of a subscription over there right now.
It's lazy, does not take ownership and responsibility, wants to defer work, and I have to force it to check reality. It likes to guess and assume it's correct and I am wrong. Agents.md is not helping at all. It's in full enshittification phase, yay!
Re: Claude.ai and API unavailable [fixed]
#57This is a tough moment. Claude is simultaneously becoming substantially more expensive, substantially less reliable (single 9 of reliability), and substantially less performant. It's really hard to justify the cost of a subscription over there right now.
I'm either extremely lucky or Dario ran the direct fiber to my house because I have never had it go down in any meaningful way..
Is this just the API and I'm too much of luddite to actually use the API?
Re: Claude.ai and API unavailable [fixed]
#58This is a tough moment. Claude is simultaneously becoming substantially more expensive, substantially less reliable (single 9 of reliability), and substantially less performant. It's really hard to justify the cost of a subscription over there right now.
YMMV. I would still be very happy with Claude if it hard failed on 20% of tasks. You can always come back to it.
I say this as someone working for a tech company who does not have to foot the bill (in the >$1k per month bracket)
I also experienced and accept the 1990s levels of unreliability, which is my “internet generation”. My first access was lifting a handset and placing on a speaker/mic cradle.
Programmers these days are fucking spoiled. If it’s $220 worth of value for $200 - I get it. But I’m getting $100k of value for $10k and so I’ll put up with some shit.
Re: Claude.ai and API unavailable [fixed]
#59So happy to have diversified my model providers this past couple of weeks. GPT-5.5 has had no trouble slotting into Opus workloads. Will be fun to try out more of the models as time goes on to build some resiliency into my engineering workflows :).
I found GPT 5.4 terrible. I just tested 5.5 and compared with opus its still not great.
Re: Claude.ai and API unavailable [fixed]
#60I don't really mind hopping between claude/codex/glm/kimi except I don't know a good way to resume as session across agent harnesses. Normally I'd just have it write out what it's doing to a file, if I need to transfer context, but if it goes down mid-session that's a no-go. I think people have built tools for this, and of course you could reasonably vibe one yourself, but I don't really trust something like that to…
You might search for a concept like `/handoff` that's in ampcode. I'm sure someone's built a skill for just this.
That's not going to work if the service is down, however.