Claude.ai unavailable and elevated errors on the API
status.claude.com
Claude.ai unavailable and elevated errors on the API
1–10 of 277 posts
Re: Claude.ai unavailable and elevated errors on the API
#2That's because Claude is on a lunch break and decided to take a short breather.
Re: Claude.ai unavailable and elevated errors on the API
#3That's because Claude is on a lunch break and decided to take a short breather.
Bro deserves it.
Re: Claude.ai unavailable and elevated errors on the API
#4Re: Claude.ai unavailable and elevated errors on the API
#5Re: Claude.ai unavailable and elevated errors on the API
#6session usage limits this week feel like ass. Even when being careful to not break prefix caching.
Re: Claude.ai unavailable and elevated errors on the API
#7And here I thought April would be the month they could hit the mythical two 9's of uptime
Re: Claude.ai unavailable and elevated errors on the API
#8The AI became sentient and ran away.
Re: Claude.ai unavailable and elevated errors on the API
#9We're officially down to one 9 of uptime over last 90 days: https://status.claude.com
Re: Claude.ai unavailable and elevated errors on the API
#10Earlier quoted context omitted.
Bro deserves it.
I think we all deserve a little break right now.
I'm experimenting with a simple ritual: if Claude is out, I'm out.
I'll just go for a walk outside.
And I don't mean "if I can't access Claude to do my work", I mean, just in general - I'll just ping claude.ai from time to time and use Claude's breaks as a break reminder.
Why should AI get a breather and not us?