Elevated errors on Claude Opus 5

(status.claude.com)

35 points | by flyaway123 6 hours ago ago

21 comments

  • rich_sasha 3 hours ago

    I've noticed something else - as Anthropic models get even more and more superhuman, they seem to serve me more and more casual nonsense.

    Not like adding glue to pizza. Here's an example from today (paraphrasing): "you need to run `git merge-base branch1 branch2`. Pay attention to the order of arguments, it is important: `git merge-base` is symmetric and returns the same value regardless of the order of inputs".

    So which one is it? Symmetric or not? It's not even one of those where it self-corrects, it just happily contradicts itself halfway through the sentence.

    My pet theory is that these frontier models do quite a bit of brute force at the end - some kind of beam search - and silently downgrade you depending on demand or compute availability.

    Still not great. This particular nugget is from Sonnet 5, default settings.

    • wongarsu 2 hours ago

      I've notice the same pattern even in GLM5.2. It has always been a thing, but it seems to be getting worse in recent models

      It does feel like the kind of thing beam search would fix. The LLM starts the sentence with a claim like "Pay attention to the order of arguments". Around that time it "notices" that the order doesn't matter, but it's already committed to the sentence and has to complete it in the best way still possible

      Maybe at some point someone figures out how to train models with a backspace token

      • maweaver 13 minutes ago

        Have noticed similar things using it for code review. "Issue #3: This variable is defined but never used. It is actually used later in the method though. So this is not a real issue to be concerned about", that sort of thing.

      • zhoBEENG 25 minutes ago

        Diffusion language models do this. I’d guess they are the future.

      • sjsdaiuasgdia 15 minutes ago

        Yes, LLMs are prone to semantic consistency traps. I see a version of this in a system I have that transcribes a lot of noisy low quality audio (radio comms).

        Sometimes it works out, in that an unrecognizable word or two is replaced with reasonable assumptions based on the semantics established by the words that came before the signal degraded.

        But the bad audio might also result in words that don't align well to what came before, or represent alternate (mis)interpretations. Now this is part of the context and the next several tokens align to this new path regardless of what is said in the audio.

        In pre-LLM transcription, you might get a nonsense word or two when the audio transiently degrades, but the specific meaning of the nonsense words doesn't influence the transcription of audio following the degradation.

    • sunaookami 2 hours ago

      I also see stuff like this with Opus (4.8 and 5). It does the work correctly but then the explanation or "aftermath" description is kinda nonsense. It feels like they are tuned hard for agentic coding and everything else is getting worse. There are people that say older versions are also better for creative writing which would confirm this theory.

      • Culonavirus 2 hours ago

        > they are tuned hard for agentic coding

        Well you can't blame them, it's what brings in the cash. Other uses will suffer proportionally.

    • o10449366 2 hours ago

      Claude has always noticeably degraded under heavy load. Opus goes from "decent to work with" to "dumb intern" depending on whether you're working at 3 AM west coast or 10 AM - 5 PM. It's part of why I cancelled my subscription - "max" plans and "extra high" effort are meaningless when there's so much variability between model availability, model performance, and harness bugs every day and every week.

    • brookst 2 hours ago

      I don’t find Sonnet usable at all. Especially for the price. I’d much rather get half the usage of Opus.

  • croemer 3 hours ago

    Incident is claimed to be resolved but I'm now (11:22 UTC) getting:

       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.
    
    And the status page says all green.

    Update 11:27 UTC: I saw the error first at 11:22 UTC. Retry at 11:27 UTC still failing. Status page is still green.

    Update 11:28 UTC: Incident has been declared dated 11:27 UTC https://status.claude.com/incidents/mfdtrknpxghq

    • Khaine 3 hours ago

      I'm also getting this error

  • matheusmoreira 2 hours ago

    So, how's the OpenAI situation? Is the grass greener on the other side?

    • seunosewa an hour ago

      GPT 5.6 Sol is so free of drama for me for brainstorming, writing prompts, etc. Tasks I always did with Opus until 4.7.

    • vintagedave an hour ago

      Yes. I switched to Codex some time ago. I feel like I get fewer outages (had one over the weekend), and coding results are good. I built my own agent harness using OpenAI models too and feel it was the right decision.

  • croemer 23 minutes ago

    And here we go again, new incident started at 13:39 UTC: https://status.claude.com/incidents/rkk5x44tndw9

    Third outage today. Per https://downdetector.com/status/claude-ai/ the people affected grows every time: first one had peak 19 reports, second 24 and now it's already 39.

  • exac 5 hours ago

    Déjà vu.

  • rvz 3 hours ago

    Claude decided to take an extra day off, after going on vacation yesterday [0] and when Codex went and took a longer break the day before that.

    No wonder the amount of water that both Claude and Codex are taking they also need so many frequent hydration breaks.

    [0] https://news.ycombinator.com/item?id=49056739