Damn, I'll have to think for myself now...

Kind of cool how fable 5.1 just worked around these by reassigning subagents to non-failing models with more supervision and now with a hint to Sol and Flash 3.8.

What's funny is I had just told Claude to kill whatever coding loop it had running. Then got a 529 immediately.

Officially signing up for the $200 Codex plan now. I do like CC, but these errors are happening every week now, and if they (Anthropic) gave regular resets that's one thing, but somehow I'm already at 62% weekly usage after the random reset this Tuesday using Fable 5.1 medium. Just not worth it any longer compared to Codex IMO. I already set up my skills and everything to be generic and not CC specific, so it shouldn't be too hard to transition over. I'll run both for a month and decide.

It would be really funny if Anthropic engs run open weight models locally when they need to fix Claude API issues :)

This pushed me off of a cheaper model into a more expensive one :'(

It goes down so often that I've advocated my company create enterprise Codex accounts as backup for devs.

Setting aside annoyance at the downtime, I'm really curious about the reasons for the failures, because I have to imagine there are some novel failure modes when serving these giant models that I haven't experienced with the kind of work I've done.

Anyone out there working in this space who can elucidate us on interesting failure scenarios unique to the space?

A nice chance to try sonnet again, must say, I'm not missing the load bearing assumptions, honest read of the permission matrix, what's genuinely a Django convention and what's a design choice, what's worth my thinking, and what's worth being precise about.

Long story short, it seems to be faster and less vocal but not much dumber (it's just my thinking partner, so I read a of the output as I create a large data model).

Demand > supply. It's impressive that customers have not migrated en masse to other providers, given the frequency of these outages. Perhaps switching costs are greater than some would believe. Or, qualitative differences between models continue to exist, despite matching on public benchmarks.

Not just claude, even grok seems to be down - https://status.x.ai/

If I didn't know any better, I would have said Grok is using Claude behind the hood. But definitely curious now why it’s happening with both these LLM providers around the same time

During each forced workflow interruption I look for alternatives. No matter if I can't use the product due to a server outage or due to their weird quota limitations.

This can't be good for retention numbers. Old-school VCs would've ripped them apart in the air. Where did all the expertise go?

Grok models are struggling too: https://status.x.ai/ reply

Looks like trouble in the SpaceX datacenters.

Every time I see Anthropic ship an issue like this, I'm reminded of Boris Cherny's glorious quote: "At this point it's safe to say that coding is largely solved."

lol

Cost and reliability are the two reasons why we don't use Claude in our product. Getting close to one nine, that's not something one can build a reliable product upon. We now use OpenAI with Gemini fallback (or vice versa depending on use case). Personally I like Claude and have the 20x Max plan but even there I burned through the whole weekly quota with 3 prompts in less than a day using the new Fable 5.1 which is crazy. Now Opus 5 is down. These two issues are really testing my patience.

If y'all could just log off for the day, that would be great!

The interesting thing is they changed default mode for Claude code to auto mode and auto mode uses sonnet to decide whether the command is safe or not. With their Sonnet model outage, the entire thing stopped working.

here is the error it was throwing:

> Error: claude-sonnet-5[1m] is temporarily unavailable (overloaded), so auto mode cannot determine the safety of Edit right now. Wait a moment and then try this action again. If it keeps failing, continue with other tasks that don't require this action and come back to it later. Note: reading files, searching code, and other read-only operations do not require the classifier and can still be used.

[delayed]

HN is not a claude uptime tracker!!