Anthropic’s newly launched AI chatbot Claude faced a widespread outage today, leaving many users unable to access the service. The problem affected the Claude website, mobile apps, and several API-based services. Several users reported seeing error messages and connection failures, with many turning to social media to check if others were facing the same issue.
What happened?
According to Anthropic, the outage was caused by a technical issue that disrupted normal operations. The company confirmed the problem on its official status page and said its engineering team was working to fix it. However, it did not provide a clear timeline for when services would be fully restored.
Anthropic confirmed that its AI chatbot Claude is facing a service disruption. The issue was first flagged at 11:49 UTC. A follow-up update at 12:06 UTC said the investigation is ongoing. There is no ETA on when Claude will be back up.
Many developers and businesses that depend on Claude’s API for coding, writing, and other automated tasks were affected. For some, the disruption slowed down ongoing projects and workflows.
What error is it showing?
Users report HTTP 500 and 529 errors, failed login attempts, authentication issues with Claude Code, frozen prompts, and timeouts across web, mobile, and API platforms during the disruption.
Why it matters?
AI tools like Claude have become an important part of daily work for many users. When such platforms go down, even for a few hours, it can cause delays and frustration. The outage also shows how much people now rely on AI tools for regular tasks.
What did Claude comment?
Anthropic developed Claude on its status page, displayed that they have discovered that some API methods are not working and they are investigating.
They said “We have identified that the Claude API is working as intended. The issues we are seeing are related to Claude.ai and with the login/logout paths. The issue has been identified and a fix is being implemented.”
Anthropic assured users that it was investigating the issue and working to restore normal service as quickly as possible. While the company did not share detailed technical reasons, it acknowledged the inconvenience caused to users.