Claude outage – Resolved
11–20 of 167 posts
Re: Claude outage – Resolved
#12If 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
Re: Claude outage – Resolved
#13A 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…
Good for more precise changes.
Re: Claude outage – Resolved
#14This can't be good for retention numbers. Old-school VCs would've ripped them apart in the air. Where did all the expertise go?
Re: Claude outage – Resolved
#15Looks like trouble in the SpaceX datacenters.
Re: Claude outage – Resolved
#16lol
Re: Claude outage – Resolved
#17Damn, I'll have to think for myself now...
Re: Claude outage – Resolved
#18Not 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
Re: Claude outage – Resolved
#19Not 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
Re: Claude outage – Resolved
#20Demand > 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.