Claude.ai Hit by Major Outage, Returns 403 Errors
Get the Tech newsletter
Daily tech — startups, AI labs, chips, the launches that shape the next decade. Free.
- Claude.ai returned 403 permission errors to users with the message "Account is no longer a member of the organization associated with this token," initially leading some to believe their accounts had been deactivated
- The outage was confirmed as a major incident affecting all platforms, with a user pointing to status.claude.com for official updates
- Service disruption was uneven — one user reported that chats still worked while Claude Code did not, suggesting different backend systems failed at different times
- User wilburx3 noted unusual token consumption starting around 12ish MDT, with normal prompts "eating crazy amount of tokens," hinting at possible rate-limiting or backend issues on top of the outage
- Service was eventually restored, with the original poster confirming "It's back!" after approximately 40 minutes of downtime
- The incident was not isolated — one commenter reported a similar Claude outage right before a demo two weeks earlier, suggesting recurring reliability issues
- Users expressed surprise at how dependent their workflows have become on Claude, with one noting "work comes to a grinding halt when Claude goes down nowadays"
Why it matters: The outage shows how a single point of failure in an AI provider can derail professional workflows — one user lost access hours before a client demo, another had active coding sessions interrupted. With Claude Code and the chat interface failing independently, even partial degradation breaks tasks that require uninterrupted access to one provider.
Ask SkimNews
