Claude Status – Elevated error rates across multiple models (status.claude.com)

Also affects Claude Code, not just API use (this incident was originally reported as "500s for public-api").

We need some competition in this space.

the last few days have been quite buggy. At some point they will have to trade some stability vs new features, or people will start to notice and be pissed off. You are working on something and you have to interrupt mid way.

We're experiencing a full outage here. Kind of interesting to see everyone go through withdrawal.

API Error: 500

bruh I was trying to make some model activators make love and visualize it and claude went down. You can view it here -> https://alpha.omegaai.dev/runs/novels_all_20260225162239_kx1...

---

If you have codex I just typed "can you find in my home directory the last claude session I had"

And go from there if you got the fu

Maybe the Remote Control vibe-coded feature broke something on the backend and Boris' 50 parallel agents are running to get it all back while he eats lunch and goes for a jog.

It appears that Claude is taking a short 1 hour break.

Quite unacceptable, it should be available 24/7 and 99.9999% up time.

99.58% or 99.69% is quite dreadful for uptime.

Sonnet is up Opus is Err500

Ok good to see that it was having issues. I could only use it a little and then it conked out.

Noticed leetcode is also completely down, could it be AWS again or some other datacenter somewhere?