Claude suffers an outage with sign-in failures on claude.ai and Claude Code
IA en un minuto newsroom · Editor: Jon Elgezabal
In 30 seconds
Anthropic had to fix a fault on Friday that kept some people on claude.ai and in Claude Code from signing in. The fix arrived at 12:05 and the incident was closed at 12:58, although in the afternoon the status page opened another incident over errors. Claude Cowork and the console for developers were also listed as affected during the morning.
Claude, Anthropic's assistant, went down this Friday, November 13, and users of claude.ai and Claude Code had trouble getting into their accounts.
According to Anthropic's status page, the company started looking at 10:58 (Madrid time) into a fault that stopped people from authenticating on claude.ai and on Claude Code, its coding tool. In that first notice it listed claude.ai with a major outage; Claude Code and the developer console (platform.claude.com) with a partial outage; and Claude Cowork, the mode for handing off complete tasks, with degraded performance.
At 12:05 Anthropic reported that it had rolled out a fix and was keeping a close eye on the recovery. In that update, Claude Code and the console already showed as operational. At 12:58 it marked as resolved the problem that had hit claude.ai and Claude Cowork.
The afternoon brought another setback. At 14:09, the same page opened a new incident over errors on claude.ai, the Claude API and Claude Code, which it later widened to the connectors, among them those for Claude Docs and Claude Sheets, to Claude Security and to Claude Managed Agents. At 15:03 it was still under investigation.
Separately, an incident with the Microsoft 365 connector has been open since Thursday, November 12, which Anthropic puts down to the outage of that Microsoft service.
Why it matters · analysis and opinion
More and more teams have Claude built into their daily work, and a morning without access shows up in concrete tasks: code that does not move forward, documents left half done. What this Friday leaves behind is that relying on a single assistant has a cost when it fails, and that waiting is not always enough, because the resolved incident was followed by another in the afternoon. Anyone using it for work with deadlines does well to keep an alternative ready and to follow the status page, where Anthropic says which services are failing and when they come back. The fact that the page details, service by service, what is affected helps people decide quickly whether the problem touches what they use.
Official source: Anthropic · Written with the help of AI: how we make the news
What does it mean for your business? · analysis and opinion
The outage mainly affects freelancers and small teams in Spain and Latin America who work every day with claude.ai or with Claude Code. According to Anthropic's status page, the developer console also had a partial outage in the morning, and the afternoon incident includes the Claude API, so those who use it from their own applications have not been spared either. Those who have Claude connected to Microsoft 365 or use the Outlook add-in have been dealing since Thursday with failures in email, calendar and search, which Anthropic puts down to the outage of that Microsoft service.
Our advice is to keep the official status page at hand and check it before spending time reviewing passwords or settings: the first notice described a problem with users authenticating in general, not with particular accounts. It is also worth keeping the instructions and templates used most often outside the tool, so work can carry on with another assistant if needed, and not leaving deliverables that depend on a single service until the last moment.
The main cost is lost working hours. For companies that use the Microsoft 365 connector, the day adds up to two separate problems. Once everything is back to normal, it is wise to check that the email and calendar tasks started during the outage were completed correctly.
