Engineering Room, panning over a bunch of hot Blackwells
"I can't change the laws of physics!"
Elevated errors across many models
71–80 of 170 posts
Re: Elevated errors across many models
#72Hello, I'm one of the engineers who worked on the incident. We have mitigated the incident as of 14:43 PT / 22:43 UTC. Sorry for the trouble.
The one time you desperately need to ask Claude and it isn’t working…
Re: Elevated errors across many models
#73Earlier quoted context omitted.
The nice thing is unlike Cloudflare or AWS you can actually host good LLMs locally. I see a future where a non-trivial percentage of devs have an expensive workstation that runs all of the AI locally.
I'm more and more convinced of the importance of this. There is a very interesting thing happening right now where the "llm over promisers" are incentivized to over promise for all the normal reasons -- but ALSO to create the perception that the "next/soon" breakthrough is only going to be applicable when run on huge cloud infra such that running locally is never going to be all that useful ... I tend to think that w…
Is there any utility in thinking about LLM provision in terms of the electricity grid?
I've often thought that local power generation (via solar or wind) could be (or could have been) a viable alternative to national grid supply.
Re: Elevated errors across many models
#74When vibes coders do the infra
Re: Elevated errors across many models
#75Earlier quoted context omitted.
Can you divulge more on the issue? Only curious as a developer and dev op. It's all quite interesting where and how things go wrong especially with large deployments like Anthropic.
I yearn for the nitty gritty details too
They turned it off and on again.
Re: Elevated errors across many models
#76Re: Elevated errors across many models
#77Earlier quoted context omitted.
I’m fairly sure you can also still run computers locally and connect them to the Internet.
Ah, you need to buy into this dystopia wholesale. The internet is also down because the LLMs fucked up the BGP routing table, which congress agreed (at the time) should run through the LLM interface. Imagination, either the first or last thing to die in 2075.
Congress administrating BGP? Now we’re talking dystopia!
Re: Elevated errors across many models
#78Earlier quoted context omitted.
I use it as much as my brain can handle and I never exceed my Max plan quota.
Just a warning for those not on the max plan; if you pay by the token or have the lower tier plans you can easily blow through $100s or cap your plan in under an hour. The rates for paying by the token are insane and the scaling from pro to max is also pretty crazy. They made pro have many times more value than paying per token and then they made max again have 25x more tokens than pro on the $200 plan. It’s a bit li…
> I hope no one out there’s paying per token!
Some companies are. Yes, for Claude Code. My co used to be like that as it's an easy ramp up instead of giving devs who might not use it that much a $150/mo seat; if you use it enough you can have a seat and save money, but if you're not touching $150 in credits a month just use the API. Oxide also recommends using API pricing. [0]
0: https://gist.github.com/david-crespo/5c5eaf36a2d20be8a3013ba...
Re: Elevated errors across many models
#79Earlier quoted context omitted.
I can stop any time I want, and in fact I am going to stop. Just one more (bug)fix.
This joke is getting old kinda Opus4.5 handles all the bugs in one go and also doesn’t introduce new ones at least for me. Very rarely i get stuck with it like i did with past generations of AI
How long the usual self debugging cycle ? it seems to be around 10 minutes for me (untyped language)
Re: Elevated errors across many models
#80Props to them for actually updating their status page as issues are happening rather than hours later. I was working with claude code and hit an API error, checked the status page and sure enough there was an outage. This should be a given for any service that others rely on, but sadly this is seldom the case.
Thank you! Opening an incident as soon as user impact begins is one of those instincts you develop after handling major incidents for years as an SRE at Google, and now at Anthropic.
I was also fortunate to be using Claude at that exact moment (for personal reasons), which meant I could immediately see the severity of the outage.