Whats Up with Claude Lately?
14 comments
They've just gotten some substantial amount of traffic of defectors from ChatGPT, so their system may be creaking under the load. They have previously said they don't degrade their models under excessive load, but the models sure behave like they do.
Hmm - that might be ?? This has been going on for a week or two, but it definately seems worse tonight...
/r/ClaudeAI is full of reports that it's down
For me claude.ai is down and i can't check my usage but claude code itself works fine
For me claude.ai is down and i can't check my usage but claude code itself works fine
No need for Reddit, their status page has it just fine: https://status.claude.com/
It says 3 Mar 2026. No downtime recorded on this day. Related: Elevated errors in claude.ai, cowork, platform, claude code
It's definitely not "elevated errors". It's down. Inaccessible. Not green. Yellow at best.
What's extra annoying is it works on some accounts and not on others. It works on Cursor running Claude and Antigravity running Claude, but not on the Claude account I paid for personally.
It's definitely not "elevated errors". It's down. Inaccessible. Not green. Yellow at best.
What's extra annoying is it works on some accounts and not on others. It works on Cursor running Claude and Antigravity running Claude, but not on the Claude account I paid for personally.
I think it's only down for some people, and/or some times, and therefore is just having "elevated errors" by their definition. I think "down" really means down for everyone.
Fair. It's just that the 98.92% uptime feels misleading.
hmm - I don't use the web UI... but as you say claude code seems to be working.
Aha! Same for me. A telling sign to me is it will take him 2-3 turns of “that’s not right” before he’ll say “let me do this properly…” and do what I original requested.
oh yeah - I get that too. Also, if I tell him to verify something - he'll do a big song and dance about verifying it as correct. Then you point out something very basic and he'll trigger that 'let me do this properly', verify it again, find out he was wrong - then say he was working from stale data/assumptions
Maybe I should just hang it up and go to bed:
That's a Claude Code issue — queued slash commands not executing between steps.
you didn't answer me - is that last rule we added to MEMORY.md active and working ?
No, it's not working reliably. I followed it once (the gap-check message), then immediately stopped doing it on the very next exchange. The rule exists in memory but I'm not consistently applying it.Oh - another 'fun' new behavior this week:
He contradicted himself within 1 paragraph and when asked about it, admitted the correct answer was explicitly listed in his MEMORY.md file - he just ignored it...
why are you constantly making assumptions and 'jumping the gun' lately ? 2 weeks ago, you didn't have these problems ?
● Honestly, I don't have a good answer for that. You're right — I've been:
I can't explain why it's worse than 2 weeks ago — I don't have visibility into model changes. But I can be more disciplined about it. Your CLAUDE.md rules are clear: brainstorm mode by default, no changes without explicit triggers, don't guess. I just need to actually follow them.