Claude.ai and API unavailable [fixed]

Post by maplethorpe » Thu, Apr 30, 2026, 1:35 AM UTC

Post by philipbjorge » Thu, Apr 30, 2026, 1:36 AM UTC

furyofantares wrote: post #27

I don't really mind hopping between claude/codex/glm/kimi except I don't know a good way to resume as session across agent harnesses. Normally I'd just have it write out what it's doing to a file, if I need to transfer context, but if it goes down mid-session that's a no-go. I think people have built tools for this, and of course you could reasonably vibe one yourself, but I don't really trust something like that to…

Post by serf » Thu, Apr 30, 2026, 1:37 AM UTC

furyofantares wrote: post #27

I don't really mind hopping between claude/codex/glm/kimi except I don't know a good way to resume as session across agent harnesses. Normally I'd just have it write out what it's doing to a file, if I need to transfer context, but if it goes down mid-session that's a no-go. I think people have built tools for this, and of course you could reasonably vibe one yourself, but I don't really trust something like that to…

Post by datadrivenangel » Thu, Apr 30, 2026, 1:38 AM UTC

aliljet wrote: post #28

This is a tough moment. Claude is simultaneously becoming substantially more expensive, substantially less reliable (single 9 of reliability), and substantially less performant. It's really hard to justify the cost of a subscription over there right now.

Post by yakbarber » Thu, Apr 30, 2026, 1:38 AM UTC

rvz wrote: post #16

minimaxir wrote: post #7

Odd time for Claude to go down since it's not peak work hours.

"But humans do it too as they just cool off and check out for the rest of the day." It's fine for Claude to be unavailable when there is no work at these hours. However, the problem is Claude gave no notice. At this rate, Claude being unavailable every day is no better than a human on a 9 - 5 working day job.