This 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.
There was another thread where some people pointed out, Amazon will give you access to Claude with better uptime for the same price (per million tokens up / down), downside is, it does not have the native ability to browse the web, but maybe that's a hidden blessing, since it's less likely to read some random website that has prompt injection embedded into it.<p>For coding its fine, I havent experimented too much with Amazon Bedrock myself, but I just might soon to check for any limitations.
Maybe the best play is to set up a routing system locally so that when claude.ai is down it automatically switches to Amazon billing and switches back when it comes back up
But that's just paying per use right, not with the subscription which is way better value
From an economics perspective, it makes sense to make it more expensive if you're having trouble keeping up with demand for a service. It'll be tough getting used to because it was so nice and cheap
YMMV. I would still be very happy with Claude if it hard failed on 20% of tasks. You can always come back to it.<p>I say this as someone working for a tech company who does not have to foot the bill (in the >$1k per month bracket)<p>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.<p>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.
> If it’s $220 worth of value for $200 - I get it.<p>Wrong comparison. If a competitor gives you $230 of value for $200, of course you shouldn't pick the $220 one
lol i love this post. not 100% sure i agree, but not 100% i don't. but great post, 10/10
or just use codex...
[dead]
We used to describe our startup as having 5 8’s of uptime
Interestingly, yeah, I can see that this would really cut into your subscription usage with the 5 hour rate limit windows...<p>I am an API user, and while it being down is super annoying, it isn't really as big of a hit to my overall usage as I can just prepare a bunch of stuff to run in parallel when it does come back up.
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..<p>Is this just the API and I'm too much of luddite to actually use the API?
Don't say single nine, it sounds ugly and bad.<p>Say five eights of reliability. Maybe six.
Not to mention substantially less open. I've been using an OpenAI subscription in Pi Agent for a couple weeks now and it's great. And from what I can tell, 5.5 is a heck of a model.
Plus, they've dumbed down their models to the point where the value just isn't there like it was. If I have to go in and clean up after it, or constantly wrestle with it through prompts, what's the point? Just spending $200 a month to be frustrated at a machine.
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!
Single nine has good vibes bro. It means when the service is up the results are better. I read about it in a blog. The model hallucinates way less. Even less than grok
Between GitHub and Claude, it seems Eternal December[0][1] is upon us.<p>[0]I say December, because that's around the time the models got good enough that non-AI folks started to notice.<p>[1]<a href="https://en.wikipedia.org/wiki/Eternal_September" rel="nofollow">https://en.wikipedia.org/wiki/Eternal_September</a>
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.<p>I don't really blame Anthropic here.
I use openai team plan whenever its down because its down so much lol
I built a hangout space to chill out in and chat to others while Claude is down (which is happening wayyy more often): <a href="https://clawdpenguin.com" rel="nofollow">https://clawdpenguin.com</a><p>There's a live Claude status board in the corner so you know when it's time to get back to work.
Oh great. My Max account has been borked for days, and now they will never get to it with everything else burning down.<p><a href="https://github.com/anthropics/claude-code/issues/54497" rel="nofollow">https://github.com/anthropics/claude-code/issues/54497</a>
With the TPU deal with Google and their relationship with Amazon they will have access compute coming online.<p>I worked with 4.6 and found some improvements for better planning and sustained us, but agree some posters 4.7 is slower, overthinking.<p>What I expect is frontier models to get bigger and more expensive (especially fast mode like on Cerberus). And most of his get much smaller distillations for the more generous subscription tiers.
Odd time for Claude to go down since it's not peak work hours.
Maybe they target certain types of infra rollouts for non-peak hours?
"But humans do it too as they just cool off and check out for the rest of the day."<p>It's fine for Claude to be unavailable when there is no work at these hours. However, the problem is Claude gave no notice.<p>At this rate, Claude being unavailable every day is no better than a human on a 9 - 5 working day job.
They are about to lose the second 9<p>99.02 % uptime
Yup, major outage on all platforms.<p><a href="https://status.claude.com/" rel="nofollow">https://status.claude.com/</a>
So 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 :).
Anybody else double fist Codex/Claude? They both code, solve problems, and find bugs in unique ways. I find using both is more useful than using either alone. I have them code review each others work, it's great.
This is insane. I have to move to Codex now.
I 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.<p>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.<p>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 work reliably or in an ongoing manner.<p>Maybe it should just be a skill.
switch to Pi.dev or any other multi model harness, you can switch between models every message if you feel like it.<p>Anthropic have blocked usage of your subscription however with third party harnesses.
> Anthropic have blocked usage of your subscription however with third party harnesses.<p>This is the main reason I use different harnesses, but I also expect (could be wrong) codex is better with codex harness (due to training on it's specific tools) than with other harnesses. I use opencode for everything that's not claude/codex.
You might search for a concept like `/handoff` that's in ampcode. I'm sure someone's built a skill for just this.
self hosted honcho (or other memory systems) and an api agnostic harness gets you most the way there.
kilocode allows you to switch between models mid session!
The models are already commoditized; if this affects you, you should probably fix your stack.<p>Still, it's pretty crazy that Claude is down to 1 nine.
But Boris declared coding is solved. How is this possible? Can’t they prompt Mythos to give them better uptime?
When Claude is making "0 mistakes", all of his work is 100% done by Claude, therefore "coding is solved!" and we have more time to go on podcasts to tell everyone about it.<p>However, when there is an incident it is immediately "human error", not Claude.<p>> Can’t they prompt Mythos to give them better uptime?<p>Anthropic is currently "vibe coding" the situation right now.
I'm feeling a bit sorry for Anthropic. This last month must be very tough on them.
So Claude decided to take the rest of the day off without notice or giving a scheduled time off?<p>Many such cases with humans (given that we continue to compare LLMs to humans these days which you cannot)
Working for me now
Humans are unavailable from time to time also.
how can someone run business on top of their APIs
More fuel to get 27b running
I've been on the $200 plan for 3 months, but this will be my last month. I got great use out of 4.5 for a while, but 4.6 felt like a half step back (conflated with all the random hidden config changes during it), and 4.7 is genuinely terrible.<p>It's impossible to tell these days whether 4.7 is stuck because it's thinking and Anthropic suppressed all output (seriously, 4.7 will just start making changes without explaining any reasoning - how is that an upgrade?) or because the underlying infrastructure is having issues.<p>4.5 -> 4.7 feels like going from working with a coach-able, junior engineer that does well with clear guidance to working with a cocky mid-level that will spend too long on pointless tangents and make confidently incorrect changes without any discussion.
Code isn’t working on my app. Chats work fine.
For what it’s worth, I moved to Codex GPT-5.5 Xhigh Fast in the desktop app and it’s been fantastic.
Here is one source that agrees: <a href="https://artificialanalysis.ai/models/capabilities/coding" rel="nofollow">https://artificialanalysis.ai/models/capabilities/coding</a>
I've been a Codex devotee since around last August. I don't know why everyone is so bonkers about Claude Code. It's not the only belle at the ball. Codex is rock solid.
Hoping to get another rest of limits.
Now... I have to cook dinner....
I personally broke it by admonishing it for fucking up its last revision to my project.
wtf all days same shit
[dead]