Claude AI Outage Today: Login Failures Hit Claude.ai and Claude Code — What Happened and Is It Fixed?

The Claude AI outage today left users around the world unable to log in to one of the most popular AI assistants. On Friday, November 13, 2026, Anthropic confirmed that Claude.ai and Claude Code were hit by elevated authentication errors, locking people out of the chatbot, its coding tool and its developer console. The outage began in the early afternoon in India and peaked within the hour, and a fix was deployed later in the day — and the complaints flooded social media within minutes.

Claude AI Outage: What Went Down

Anthropic's own status page logged the incident as starting at 09:58 UTC on November 13, which is 3:28 pm IST. The first update said the company was investigating an issue with users authenticating to Claude.ai and Claude Code, and promised more information as soon as possible. The status page listed claude.ai as facing a major outage, Claude Code and the Claude Console at platform.claude.com as partial outages, and Claude Cowork as degraded. Notably, the Claude API was not listed as affected, which meant that apps built on top of Claude kept working even while the chatbot itself was unreachable for many users.

The timing made the outage hard to miss. It landed on the same day Microsoft's global Outlook and Teams outage dragged into a second day, and many users first assumed the two problems were connected. Anthropic, however, described the Claude login problem as its own incident, separate from Microsoft's troubles — although a separate Microsoft-related problem also appeared on Claude's status page.

What Users Saw: Login Failures, Logouts and Error Screens

Users described a range of symptoms: outright authentication failures, expired credentials, errors tied to credential precedence and expired OAuth sessions, and sudden logouts in the middle of a session. People trying to open the web platform ran into failed sign-in screens and session errors, and Claude Code users could not get their coding tool to authenticate either. On social media, the frustration was loud — posts asking "WTF Claude down again?" spread quickly, and users in the US, India and the UK all reported problems accessing the chatbot and its related services.

The scale of the disruption showed up in the monitoring numbers. Downdetector India recorded a peak of 2,906 reports around 3:20 pm IST, against a normal baseline of just two reports — a spike of more than a thousand times the usual level. In the United States, the largest share of complaints was about Claude Code, while users in the UK reported problems with both Claude Code and the app.

Is Claude Back? Fix Deployed, Recovery Being Monitored

Anthropic moved from investigating to fixing within about an hour. At 11:05 UTC, or 4:35 pm IST, the status page posted a new update: "A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery." That means the underlying problem was addressed, but Anthropic was still watching to make sure logins recovered fully before declaring the incident over. As of the latest update available, the company had not disclosed a root cause for the authentication errors, and had not given a specific time by which every user would be back to normal.

If you are still seeing login errors, recovery can be staggered: a fix being deployed does not mean every session is restored at once. The best place to check is Anthropic's own status page at status.claude.com, which is the source every other tracker is reading from.

A Separate Problem: Claude for Outlook and the Microsoft Outage

Alongside the login outage, Claude's status page carried a second, separate problem tied to Microsoft. Anthropic identified elevated errors on its Microsoft 365 connector at 17:52 UTC on November 12, and wrote plainly: "This issue is caused by a Microsoft 365 service incident." The tools that let Claude read Outlook mail, calendars and files were failing for most requests, and Claude for Outlook was still affected into Friday. That problem is a knock-on effect of Microsoft's global Outlook and Teams outage, which began on Thursday and dragged into a second day — a story we have already covered on this blog. OpenAI reported the same thing on Thursday, saying its Microsoft connectors for ChatGPT were broken too.

• Anthropic logged the Claude login incident at 09:58 UTC on November 13, 2026 (3:28 pm IST): elevated authentication errors on claude.ai, Claude Code and platform.claude.com.
• Claude.ai was listed as a major outage; Claude Code and the Claude Console as partial outages; Claude Cowork as degraded. The Claude API was not listed as affected.
• Users reported login failures, expired credentials, OAuth session errors and sudden logouts. Downdetector India peaked at 2,906 reports around 3:20 pm IST, against a baseline of two.
• A fix was deployed at 11:05 UTC (4:35 pm IST), and Anthropic moved to monitoring recovery. No root cause has been disclosed.
• A separate Microsoft 365 connector problem, caused by Microsoft's own outage, has affected Claude for Outlook since November 12.
• StatusPal counts 14 Claude incidents in the last 30 days, totalling about 34 hours of disruption.

What to Do If You Still Cannot Log In to Claude

First, check status.claude.com to see whether Anthropic still lists an incident. Try signing in again in a fresh browser window, clear cookies for claude.ai, and disable any VPN or browser extension that might interfere with the login. If Claude Code is failing to authenticate, restarting the tool so it picks up a fresh session can help. And as ever, never enter your credentials on a page you reached through a random link — go to claude.ai directly.

The Claude AI outage is a reminder of how quickly a single login problem can take a tool millions of people rely on offline. With the fix deployed and recovery being monitored, most users should be back in soon, but the incident is worth watching: 14 outages in 30 days is a pattern, not a one-off.