codex was working fine until I installed the update and now getting the same error. Gemini and claude are fine but there is an update for both and I'm not taking a chance.
Claude outage – Resolved
151–160 of 167 posts
Re: Claude outage – Resolved
#152honestly boggles my mind that actual companies put load-bearing (lol) work behind 3rd party api's like claude or gpt.. also its really funny because some of these companies fired actual humans to put said 3rd party api to work in place of humans... like what happens when ur boy claude stops showing up for work huh!?
Re: Claude outage – Resolved
#153Re: Claude outage – Resolved
#154A 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 lot of the output as I create a large data…
The other bizarre word I've now noticed and can't understand is "pathological". As in "bug has turned pathological"
In old school ML a pathological solution is often a collapse of some kind due to an underspecified objective. Maybe one parameter explodes or the model predicts "0" for everything
I read this as "the code is working as intended but the bug is an artifact of the original design"
Re: Claude outage – Resolved
#155A 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 lot of the output as I create a large data…
While you're in there, it may be worth a pass.
Re: Claude outage – Resolved
#156Demand > 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.
If a meaningful chunk of customers moves to some other service, that service will get swamped and fall down.
Re: Claude outage – Resolved
#157Cost 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 c…
We just use bedrock in prod
That's a good point. Seems like Bedrock offers the same pricing while also providing an uptime SLA.
Re: Claude outage – Resolved
#158Earlier quoted context omitted.
Or just their own models locally, since 8x GPU pods fit under a desk (makes a nice foot heater too)
It's been a while since I messed with serious hardware, what's the cooling noise level? I guess they have to be water cooled or the rack format 8u ones would be about 100db
My 4x 15k rpm 1U fans I use to cool my twin AMD V620s make a horrible racket, especially how they resonate with the rest of the workstation's case fans. Similar in volume and annoyance to running an 8" circular saw. I can only imagine it would probably be as bad or worse than that.
Re: Claude outage – Resolved
#159A 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 lot of the output as I create a large data…
this is like poetry
Re: Claude outage – Resolved
#160A 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 lot of the output as I create a large data…
That definitely reframes it