Live data from Hacker News

Elevated error rate across multiple models

status.claude.com

211–220 of 293 posts

Re: Elevated error rate across multiple models

#211
post #71
post #38

Earlier quoted context omitted.

"curl -fsSL https://pi.dev/install.sh | sh" — seriously? That tells me a lot about the whole project, unfortunately.

it tells you they're just like basically every other CLI targeting project for the last 15 years? I mean is it a big security hole we all accept, yes, it is. But it's not really indicative of much. That's also how I install rust.

We also accepted the security risks of npm and such and we get one supply chain attack after another.

Maybe security should be at a higher position on our priority list.

The careless days are ultimately over but we still don’t act like that.

Re: Elevated error rate across multiple models

#212
post #201
post #27

Earlier quoted context omitted.

for me it's API Error: 529 Overloaded. This is a server-side issue, usually temporary — try again in a moment. If it persists, check https://status.claude.com .

529 and not 429?

429 is if you have been rate limited. 529 is for server overloaded and can't process more.

Re: Elevated error rate across multiple models

#214
post #209

Earlier quoted context omitted.

I keep butting into the question of; why opencode, when you've got codex available? Codex is open source as well, and i can't seem to picture a situation where one would want Opencode over Codex. As far as I can tell, they tick the same boxes- but one has the support of a big boy model provider.

If you care about privacy at all, you can route your Opencode requests through an inference provider that does not retain any logs or data. It is also much cheaper. So if your boxes include `Privacy` and `Affordability`, then no, they don't tick the same boxes.

I think they meant using Codex with non-openai providers?

Re: Elevated error rate across multiple models

#215
post #138

Earlier quoted context omitted.

Is pi better than opencode?

oh-my-pi is a bit of a cross between the two; comes with basically everything OpenCode does, but still easy to customise. OpenCode is nice if you don't want to do a lot of research and just want to get started right away. The OpenCode Go plan for $5 a month for your first month is a great way to do this, with good models to choose from and reasonable usage limits for a beginner.

I use Go plan precisely with Opencode IDE (and also Jetbrains IDE suite), but now also have access Gemini Pro and Claude Pro. And wonder which tooling to invest my time into, especially that MCP servers also potentially come into play here, and I want at least some models/tools to handle private tasks, like handling my increasingly-complex Home Assistant setup. And I also want to start using models according to needs (plan, execution, reviews). This shit gets extremely complicated extremely quickly, not to mention how often this field shifts direction.

Re: Elevated error rate across multiple models

#216

Actual 90d uptime: 97.6838% (calculated by Codex from live data) Computed from the page’s own data for 2026-03-26 through 2026-06-23: - Partial outage: 43h 15m 1s - Major outage: 6h 46m 48s - Total affected time: 50h 1m 49s - Major-only uptime: 99.6861% So, only one 9 for 10x vibes.

I want uptime modulo in my timezone/work hours. I don't give a shit about any 9's earned while I'm sleeping.

Sleeping less nowadays...

Re: Elevated error rate across multiple models

#217
post #209

Earlier quoted context omitted.

I keep butting into the question of; why opencode, when you've got codex available? Codex is open source as well, and i can't seem to picture a situation where one would want Opencode over Codex. As far as I can tell, they tick the same boxes- but one has the support of a big boy model provider.

If you care about privacy at all, you can route your Opencode requests through an inference provider that does not retain any logs or data. It is also much cheaper. So if your boxes include `Privacy` and `Affordability`, then no, they don't tick the same boxes.

You can use the Codex harness with non-openai providers if you want.

Re: Elevated error rate across multiple models

#218
post #181
post #133

Earlier quoted context omitted.

From source: creates much more work for the user. Package managers: ecosystem is fragmented, requiring a long list of distro- and package-manager-specific instructions. Many scripts already install through package managers, they simply make the user’s life easier. Flatpaks: These are clearly designed for desktop applications, with CLIs treated as an afterthought. They may be the best long-term hope, but today they ar…

Bullshit. There's plenty of big projects that don't suggest you curl a script right into your shell. If you have curl, you're probably on Linux. Just use the package manager like an adult.

The "like an adult" is what has and will continue to hold back linux on the desktop. Always gatekeeping less technical users instead of acknowledging adoption and ease of use are critical.

Re: Elevated error rate across multiple models

#219
post #149
post #137

I signed up for paid plan on Claude just 3 hours ago for the first time and was scratching my head on how that thing gets praised so much if I can't even send a question half of the time....

That's just exceptionally unfortunate timing. Anthropic has been getting better at uptime, but they still have the occasional issue.

Yeah it's one of those situations in which you reluctantly check for downtime as a last resort, only to find out you indeed just had a bad luck. Which is good, because I thought it was a beginner's brain type of friction.

Re: Elevated error rate across multiple models

#220
post #59

Earlier quoted context omitted.

I am genuinely curious what it tells you, as "curl https//.. | sh" has long been an enormously popular approach to distribution in the open source world. Homebrew, to name just one example, advertises a similar method. (pi.sh also documents other install methods, like `npm`, on their homepage) If trust and security is the issue, unfortunately "better" ideas like hashpipe [1] never achieved critical mass [1] https://n…

> I am genuinely curious what it tells you, as "curl https//.. | sh" has long been an enormously popular approach to distribution in the open source world. It's plain horrible. You could have, for example, a compromised server serving malware but only one out of every 100 download. The only signature you rely on is TLS. Proper package distribution are using proper signatures schemes, are decentralized, even for some…

[deleted]
Post reply on HN