Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Claude outage – Resolved

status.claude.com

Post reply on HN
Print view View original

131–140 of 167 posts

Re: Claude outage – Resolved

#131

Post by lowbloodsugar »

What I find fascinating is that this thread was chock full of people saying “Well this is the last straw: I’ve just signed up for Codex.” And now every single one of them is gone. They felt like marketing shitposts when I read them and their sudden absence now that Codex is down too only confirms it in my mind.

It lols like the timeline is Claude went down, some % migrated to Codex, then Codex went down. So much for the “multiple providers” theory. Wonder how token-based providers are doing.

Re: Claude outage – Resolved

#132

Post by embedding-shape »

kristofferR wrote: post #97
torginus wrote: post #94

Earlier quoted context omitted.

Isn't this the classic blackout scenario? Claude goes down, then people move over to Codex, which is overwhelmed, and crashes, so people move to Grok...

This ain't just slow/at capacity, this is dead down.

When you're dealing with millions of users and response times go up above timeouts, there isn't much difference between "at capacity" and "down" if most users can't reliably use the service.

Re: Claude outage – Resolved

#133

Post by Waterluvian »

martinald wrote: post #81
teekert wrote: post #10

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 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"

This is a term fellow devs have been using for years and years and my brain just cannot come to re-index its meaning. So I am immediately distracted by the context switch to sociopathic liars and related psychology.

Re: Claude outage – Resolved

#134

Post by devin »

martinald wrote: post #81
teekert wrote: post #10

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 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"

"Latent" is another one, as in "latent bug" or in one particularly odd case "latent twin".

Re: Claude outage – Resolved

#135

Post by khalic »

kilroy123 wrote: post #27
stri8ted wrote: post #11

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.

I think a lot of people, like myself, have. Codex paid users have grown a lot in the past few months.

check their status page...

Re: Claude outage – Resolved

#139

Post by Lalabadie »

trjordan wrote: post #15

Grok models are struggling too: https://status.x.ai/ reply Looks like trouble in the SpaceX datacenters.

I'm sure it's not that, but I'm picturing Elon Musk again unplugging random machines in the datacenter, and hiring dudes in a pickup to move them.

Re: Claude outage – Resolved

#140

Post by giancarlostoro »

tartoran wrote: post #114
giancarlostoro wrote: post #4

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

Maybe you triggered a cascade of events that took down a few datacenters.

"Stop all loops you're running" would be one hell of a 0-day for Opus to pull off, but hey, it did crack me up thinking about it.
Post reply on HN