They have been screwing around in the back-end, for a while. They are doing something and not being transparent, re-routing the models, degrading performance and intelligence and all week post-fable ban the quality was garbage, last day and a half it improved, last half an hour degraded, now it's down.
Claude: Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6
11–20 of 42 posts
Re: Claude: Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6
#12Times like this remind me that despite GLM and Codex and other models being hyped up as Claude Opus 4.8 replacements, I still would not trust them with my most important work. For example, right now I'm working on a huge refactoring project, and even Opus has struggled with it after several days. I cannot even imagine how GLM, Codex, or other models would handle this. So the only option for me is to wait until this o…
Since you cannot imagine how they'd perform, isn't this the perfect opportunity to test your assumption?
Re: Claude: Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6
#13dang et al,
"Service X is down" is not "news". Kinda feels like points-farming.
Anyone caring that X works is gonna know it's down - they can't work! And probably why they are at HN ;)
HN as an "is service X down?" detector is less reliable than trying the actual service :)
If HN is gonna keep letting people post "X is down" no worries. But it seems worth a flag.
Re: Claude: Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6
#14Per their status page, the main product now has one 9 of uptime.
Re: Claude: Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6
#15This happens all the time. Nothing to see here
Re: Claude: Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6
#16Sonnet 5 here we come
Re: Claude: Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6
#17Times like this remind me that despite GLM and Codex and other models being hyped up as Claude Opus 4.8 replacements, I still would not trust them with my most important work. For example, right now I'm working on a huge refactoring project, and even Opus has struggled with it after several days. I cannot even imagine how GLM, Codex, or other models would handle this. So the only option for me is to wait until this o…
Since you cannot imagine how they'd perform, isn't this the perfect opportunity to test your assumption?
yeah and lets not forget codex and glm have subscriptions too, with even more usage per dollar
Re: Claude: Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6
#18Per their status page, the main product now has one 9 of uptime.
Hopefully still in the "tens" digit!
Re: Claude: Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6
#19Earlier quoted context omitted.
Since you cannot imagine how they'd perform, isn't this the perfect opportunity to test your assumption?
yeah and lets not forget codex and glm have subscriptions too, with even more usage per dollar
but they also burn more tokens per task, so in the end, Claude comes out as the more efficient one, despite giving you less tokens.
Re: Claude: Elevated Error Rates for Opus 4.8, Opus 4.7, Opus 4.6, and Sonnet 4.6
#20My speculation is that we'll get fable back tomorrow.
Usually we see messy devops stuff or maybe nerfing(not much these days) around the time they're releasing new models