# Claude Down on 13 November 2026: Two Outages, the 403 Cloudflare Error and What to Do

> Claude went down twice on 13 November 2026: a sign-in outage on claude.ai and Claude Code from 09:58 to 11:58 UTC, then errors on claude.ai, the Claude API and Claude Code from 13:09 to 15:38 UTC. What failed, what Claude Code's '403 Attention Required! | Cloudflare' error meant, and how to keep working next time.

By Tahir Nazir · Published 2026-11-13 · Updated 2026-11-14
Canonical: https://www.its-tahir.com/blog/claude-ai-outage

**Claude went down twice on 13 November 2026. From 09:58 to 11:58 UTC, signing in to claude.ai and Claude Code failed, often with `403 Attention Required! | Cloudflare`, while the Claude API stayed Operational. From 13:09 to 15:38 UTC, a second incident caused errors on claude.ai, the Claude API, Claude Code, Claude Cowork and connectors. Both are resolved, and Anthropic has not published a cause for either.**

If Claude is down for you now, check [status.claude.com](https://status.claude.com) first; the steps in [What should you do when Claude is down?](#what-should-you-do-when-claude-is-down) work for any outage. The rest of this page is what happened on 13 November and what each error meant.

*Last reviewed 14 November 2026 against status.claude.com, my own Claude Code session during the first incident and reports from Claude Code 2.1.323 users on GitHub and Hacker News. All times are UTC.*

![Claude status page on 13 November 2026: claude.ai Major Outage, Claude Console (platform.claude.com) Partial Outage, Claude API (api.anthropic.com) Operational, Claude Code Partial Outage, Claude Cowork Degraded Performance, Claude for Government Operational, Claude on Cloud Platforms Operational.](https://www.its-tahir.com/blog/claude-ai-outage/claude-status-13-nov-2026.png)

*status.claude.com on 13 November 2026, during the first (sign-in) incident.*

## Was Claude down on 13 November 2026? The timeline

**Yes, twice. Anthropic's status page lists two separate incidents on 13 November 2026: a sign-in outage from 09:58 to 11:58 UTC and a wider outage that included the Claude API from 13:09 to 15:38 UTC. A third, older incident affected only the Microsoft 365 connector.**

| Time (UTC) | What happened |
|---|---|
| 12 Nov, 16:03 | Microsoft 365 connector and Claude for Outlook start failing (Microsoft 365 service incident) |
| 13 Nov, 09:58 | Incident 1 opened: "We are investigating an issue with users authenticating to Claude.ai and Claude Code." |
| about 10:15 | Downdetector shows about 3,800 reports for Claude ([The Sun](https://www.thesun.co.uk/tech/41012746/claude-ai-crashes-worldwide-microsoft-outage/)) |
| about 10:40 | Sign-in works again in my own Claude Code session; others report it coming and going |
| 11:05 | "A fix has been deployed for the issue affecting Claude services and we are monitoring for recovery." |
| 11:58 | Incident 1 resolved: "The issue affecting claude.ai and Claude Cowork has been resolved." |
| 13:09 | Incident 2 opened: degraded performance on claude.ai, the Claude API and Claude Code |
| 13:52 to 14:03 | Incident 2 widens to connectors (including Claude Docs and Claude Sheets), Claude Security and Claude Managed Agents |
| 14:36 | Recovery on claude.ai and the Claude API; connectors still degraded |
| 15:33 | Errors back to normal levels; Claude Managed Agents and Claude in Meetings recovering; scheduled tasks and routines running more than two hours late, some skipped; Claude Security scans delayed |
| 15:38 | Incident 2 resolved |
| 16:40 | Microsoft 365 connector errors end (resolved on the status page at 21:49) |

## What Claude services were down on 13 November 2026, and what still worked?

**In the first Claude outage on 13 November 2026, only services behind the claude.ai sign-in failed: claude.ai was in Major Outage, Claude Code and Claude Console (platform.claude.com) in Partial Outage and Claude Cowork degraded, while the Claude API, Claude for Government and Claude on Cloud Platforms stayed Operational. In the second incident the Claude API was affected too.**

| Service | Incident 1 (09:58 to 11:58) | Incident 2 (13:09 to 15:38) |
|---|---|---|
| claude.ai (web, desktop, mobile) | **Major Outage**, sign-in failing | Affected, errors |
| Claude Code | **Partial Outage**, subscription sign-in failing | Affected, including connector use |
| Claude Console (platform.claude.com) | **Partial Outage** | Not listed |
| Claude Cowork | **Degraded Performance** | Affected |
| Claude API (api.anthropic.com) | **Operational** | Affected |
| Connectors (Claude Docs, Claude Sheets) | Not listed | Degraded until about 15:33 |
| Claude on Cloud Platforms (AWS, Google Cloud, Microsoft Foundry) | **Operational** | Not listed |

Which services were down decides what helps: in a sign-in outage, an API key or a cloud provider gets you around it; in an outage that includes the Claude API, an API key does not.

## What caused the Claude outage on 13 November 2026?

**Anthropic has not published a cause for either 13 November 2026 incident. The [first](https://status.claude.com/incidents/nn11wk485zfn) said it was "investigating an issue with users authenticating to Claude.ai and Claude Code", deployed a fix at 11:05 UTC and resolved it at 11:58. The [second](https://status.claude.com/incidents/34wq7gxnxvvm), from 13:09 to 15:38 UTC, was described only as degraded performance. Anthropic has not linked either one to the Microsoft 365 outage.**

### Was Claude down because of Microsoft?

**Not according to Anthropic's status page. It ties the Microsoft 365 outage only to the Microsoft 365 connector and Claude for Outlook, in a [separate incident](https://status.claude.com/incidents/sqn3fg1l96dl) that ran from 16:03 UTC on 12 November to 16:40 UTC on 13 November, and gives no cause for the two 13 November outages. The one overlap: a Claude login code sent to a Microsoft 365 mailbox may not have arrived.**

Anthropic said that incident was "caused by a Microsoft 365 service incident": mail, calendar and search tools in the Microsoft 365 connector failed for many requests, and Claude for Outlook was affected. [The Times of India's report](https://timesofindia.indiatimes.com/technology/tech-news/microsoft-outage-hits-ai-tools-of-anthropic-and-openai-companies-status-page-give-details/articleshow/135797316.cms) from the same day notes that Claude's API, Claude Code and Console were still listed as operational while it was the only incident.

Some headlines said Claude went down "due to" the Microsoft outage; Anthropic has not said that, and one developer on [Hacker News](https://news.ycombinator.com/item?id=50480936) who does no Microsoft Office work at all was logged out of Claude Code the same way. Microsoft's outage could still keep you out of Claude in one way: **if your Claude login code goes to an Outlook or Microsoft 365 work address, it may never arrive.** A post on [r/claude](https://www.reddit.com/r/claude/) titled "Microsoft outage means I can't get into Claude" described the same problem. That is your mailbox, not Claude.

| Incident | Time (UTC) | Affected | Cause given |
|---|---|---|---|
| Elevated errors on claude.ai, Claude Code, and platform.claude.com | 13 Nov, 09:58 to 11:58 | claude.ai, Console, Claude Code, Cowork | None ("an issue with users authenticating") |
| Elevated errors on claude.ai, the Claude API, and Claude Code | 13 Nov, 13:09 to 15:38 | claude.ai, Claude API, Claude Code, Cowork, connectors | None ("degraded performance") |
| Elevated errors affecting the Microsoft 365 connector | 12 Nov 16:03 to 13 Nov 16:40 | Microsoft 365 connector, Claude for Outlook | "a Microsoft 365 service incident" |

## What does "Failed to authenticate. API Error: 403 Attention Required! | Cloudflare" mean in Claude Code?

**In Claude Code, "Failed to authenticate. API Error: 403 Attention Required! | Cloudflare" means a request to Anthropic got Cloudflare's challenge page (HTTP 403) instead of a token or a reply. On 13 November 2026 it was part of Anthropic's sign-in incident, at sign-in and mid-session. When status.claude.com shows everything Operational, a common cause is Cloudflare challenging your network, for example through a VPN, proxy or shared IP.**

This is what Claude Code printed for me on 13 November when it tried to sign in with my claude.ai account:

```text
Failed to authenticate. API Error: 403 Attention Required! | Cloudflare
```

![Claude Code terminal: Failed to authenticate. API Error: 403 Attention Required! | Cloudflare](https://www.its-tahir.com/blog/claude-ai-outage/claude-code-403-attention-required-cloudflare.png)

*Claude Code on 13 November 2026, trying to sign in with a claude.ai account during the first incident.*

"Attention Required! | Cloudflare" is the title of Cloudflare's challenge page. Claude Code sent a request to Anthropic and got that page back with HTTP 403 instead of a token or a reply. A command-line tool cannot solve a browser challenge, so it reports the request as an authentication failure.

### The 403 in the middle of a session

It did not only happen at sign-in. I was in the middle of a task in Claude Code when a session-expired login prompt appeared. I cancelled it and asked it to continue; it worked for a second or two, then the 403 appeared and it asked me to log in again. I then tried Claude Code in the terminal and it was much the same: a few seconds of work, then another error.

Developers on Claude Code 2.1.323, on macOS, Linux and Windows, reported the same thing on [GitHub](https://github.com/anthropics/claude-code/issues/109508) and [Hacker News](https://news.ycombinator.com/item?id=50480936) that morning, from Europe to India and Malaysia, usually in this form:

```text
Please run /login · API Error: 403 Attention Required! | Cloudflare
```

What they described, none of which Anthropic has confirmed:

- **It struck between tool calls.** One request succeeded, the tool ran locally, and the next request, sending the tool result back, got the 403.
- **It came and went.** Sending the message again sometimes worked without a new login; another developer had it work for about ten minutes and then fail again.
- **Cancelling the login prompt bought a few turns.** [One Hacker News commenter](https://news.ycombinator.com/item?id=50480936): "Clicking on cancel in Claude Code will throw you back into the session for another couple of turns." That matches what I saw, though for me each retry lasted only seconds.
- **Logging in again did not stick.** Several people got back in, worked for about five minutes, and were kicked out again. Others saw `OAuth request failed`, or a login page at claude.com/cai/oauth/authorize that just kept spinning.
- **It could log you out.** One developer was signed out twice in a row and had to run `/login` each time ([#109515](https://github.com/anthropics/claude-code/issues/109515)); another said the repeated 403s used up tokens ([#109516](https://github.com/anthropics/claude-code/issues/109516)).
- **For some, it was not their network.** One report came from a residential connection with no VPN or proxy and reproduced on a second machine. Another found that connecting through a VPN got around it, which suggests (unconfirmed) that the block depended on where the request came from.

If it hits you mid-task, cancel the login prompt and send your message once more; use the turns you get to let the agent finish its current step or note where it got to. If it keeps failing, stop the task rather than letting it retry and spend tokens, and switch to an API key (below) until the incident is resolved.

### What to do about the 403

It depends on whether an incident is open:

- **During a sign-in incident like the first one on 13 November:** it is most likely part of the incident rather than anything on your machine. Retry once, then wait for the incident to clear or switch to an API key (below).
- **When status.claude.com shows everything Operational:** Cloudflare may be challenging your network. Common triggers are a VPN, a corporate proxy or a shared IP with a poor reputation. Turn the VPN off, try another network (a phone hotspot is the quickest test), then run `/login` again.

If the error is "Not logged in · Please run /login" or an OAuth token that expired, that is a different problem with its own fix: see [Claude Code not logged in](/blog/claude-code-not-logged-in-login-expired).

## What should you do when Claude is down?

**Check status.claude.com to see which components are down, keep any session that still works signed in, and if only the claude.ai sign-in is failing, switch Claude Code to an Anthropic API key, Amazon Bedrock or Google Vertex AI. If the Claude API is down too, an API key will not help; switch tools or wait.**

### 1. Confirm it is not just you

Open [status.claude.com](https://status.claude.com). If a component you use is not Operational, it is not your setup. User-report trackers such as Downdetector, StatusGator and [uptime.com](https://uptime.com/claude.ai) help when the status page has not caught up yet. In Claude Code, `/status` shows which account and sign-in method the session uses.

### 2. Stay signed in

In a sign-in outage, a claude.ai tab or Claude Code session that still works has already passed the step that is failing. Logging out to "reset" things puts you back at that step, so leave working sessions alone until the incident is resolved. Staying signed in is not a guarantee: on 13 November some Claude Code users were logged out by the 403 mid-session. But logging out yourself only makes it certain.

### 3. Use Claude Code with an API key, Bedrock or Vertex AI

Claude Code does not need the claude.ai sign-in if you give it another credential. On 13 November this got around the first incident, when the API and Claude on Cloud Platforms stayed Operational; it did not help during the second, when the Claude API was affected too.

```bash
# Anthropic API key (pay-as-you-go, billed to your Console account, not your Pro/Max plan)
export ANTHROPIC_API_KEY=sk-ant-...
claude
```

Or, if you already pay for a cloud provider, pick one of these (not both):

```bash
# Amazon Bedrock, with your AWS credentials
export CLAUDE_CODE_USE_BEDROCK=1
export AWS_REGION=us-east-1

# Google Vertex AI, with your Google Cloud credentials
export CLAUDE_CODE_USE_VERTEX=1
export CLOUD_ML_REGION=us-east5
export ANTHROPIC_VERTEX_PROJECT_ID=your-project-id
```

Use a region where your account has Claude models enabled; the [Bedrock](https://code.claude.com/docs/en/amazon-bedrock) and [Vertex AI](https://code.claude.com/docs/en/google-vertex-ai) setup pages list the rest.

On Windows PowerShell, use `$env:ANTHROPIC_API_KEY = "sk-ant-..."` instead of `export`. Two things to know before you rely on this:

- **You need the key already.** Creating a new key happens in the Console, which was in Partial Outage during the first incident. The time to make a spare key is before the next outage.
- **API usage costs money per token.** It does not draw on your subscription's usage limits. Unset the variable when the incident is over so Claude Code goes back to your plan.

### 4. Which Claude Code error is it, and is it an outage?

**Not every Claude Code error is an outage. "403 Attention Required! | Cloudflare" and "OAuth request failed" point to a sign-in incident or your network, "API Error: 529" is capacity on one model, and "You've hit your weekly limit" is a usage limit.**

| What you see | What it is | Fix |
|---|---|---|
| `Failed to authenticate. API Error: 403 Attention Required! \| Cloudflare` | Request challenged by Cloudflare (a sign-in incident, or your network) | Retry once; then wait, use an API key, or change network if no incident is open |
| `Please run /login · API Error: 403 Attention Required! \| Cloudflare` | The same 403 in a running session | Cancel the login prompt and send the message again once; if it repeats, stop the task and use an API key |
| `OAuth request failed`, or the claude.com login page spins forever | Sign-in itself failing during an incident | Don't keep retrying; use an API key or wait for status.claude.com to show the incident resolved |
| `Not logged in · Please run /login` | Your saved login is missing or expired | `/login`; if sign-in itself is down, use an API key until it is back ([details](/blog/claude-code-not-logged-in-login-expired)) |
| `API Error: 529` with an overloaded message | Capacity on one model, not an outage | Retry or switch model with `/model` ([details](/blog/claude-code-529-overloaded-retry-behaviour)) |
| `You've hit your weekly limit` | Usage limit, not an outage | A [limit reset](/blog/claude-limit-reset) or wait for your reset time |

For every other Claude Code message, the [Claude Code troubleshooting](/blog/claude-code-troubleshooting) hub has the full lookup table.

## What can you use instead of Claude when it is down?

**For chat and writing, use ChatGPT or Google Gemini. For coding in the terminal, use OpenCode, or Claude Code itself with an API key, Amazon Bedrock or Google Vertex AI when only the claude.ai sign-in is down. For work that must not depend on any provider, run a local model through Ollama or LM Studio.**

| Task | Alternative | Note |
|---|---|---|
| Chat and writing | **ChatGPT** or **Google Gemini** | At the time of the Times of India report on 13 November, OpenAI's status page listed only its Microsoft 365 connector incident |
| Coding agent in the terminal | **Claude Code with an API key, Bedrock or Vertex AI** | Same tool, same project files; works when only the claude.ai sign-in is down |
| Another terminal agent | **OpenCode** | Works with several providers; see [OpenCode's free tier](/blog/opencode-free-tier-can-only-be-used-from-within-opencode) and its limits |
| Work that must not depend on any provider | **A local model through Ollama or LM Studio** | Weaker than Claude for large coding tasks, but nothing upstream can take it down |

The [Reddit thread](https://www.reddit.com/r/ClaudeAI/comments/1xuzlpu/what_would_you_do_if_theres_a_claude_outage/) asking "What would you do if there's a Claude outage?" landed in the same place: several replies said they would switch to ChatGPT, Gemini or a local model for the day.

## How big was the 13 November outage?

**During the first Claude outage on 13 November 2026, Downdetector showed about 3,800 reports for Claude at 10:15 UTC, according to [The Sun](https://www.thesun.co.uk/tech/41012746/claude-ai-crashes-worldwide-microsoft-outage/), falling to around 270 by 10:30. Developers reported the sign-in errors from Austria, Germany, Italy, Poland, India and Malaysia on [Hacker News](https://news.ycombinator.com/item?id=50480936).** Downdetector counts are user reports, not Anthropic figures. The second incident reached further into paid features: scheduled tasks and routines ran more than two hours late, some runs were skipped, and adding a new connector on claude.ai was briefly unavailable.

## How often does Claude go down?

**Short incidents are common and long ones are rare. Selected incidents on status.claude.com from September to November 2026 range from four minutes of overloaded errors on 10 November to the two 13 November outages of about two and two and a half hours, and a 24.5-hour Microsoft 365 connector incident.**

Selected recent incidents, in UTC, from status.claude.com:

| Date | Incident | How long |
|---|---|---|
| 14 Nov 2026 | Elevated errors on purchases, plan upgrades and cancellations on claude.ai (core use not affected) | About 1.5 hours, 02:34 to 04:03 |
| 13 Nov 2026 | Elevated errors on claude.ai, the Claude API and Claude Code (plus connectors) | About 2.5 hours, 13:09 to 15:38 |
| 13 Nov 2026 | Elevated errors on claude.ai, Claude Code and platform.claude.com (sign-in) | 2 hours, 09:58 to 11:58; fix deployed 11:05 |
| 12 to 13 Nov 2026 | Elevated errors affecting the Microsoft 365 connector (Microsoft 365 service incident) | About 24.5 hours, 16:03 on 12 Nov to 16:40 on 13 Nov |
| 10 Nov 2026 | Overloaded errors on Claude Fable 5.2 and Claude Mythos 5.2 | Four minutes |
| 8 Nov 2026 | Degraded performance for Claude Fable 5.1 (claude.ai, API, Claude Code, Cowork) | 14 minutes, 08:18 to 08:32 |
| 29 Sep 2026 | Elevated errors on claude.ai, Claude Code, Claude Cowork and the Claude API (also reported by [The Next Web](https://thenextweb.com/news/claude-is-down-anthropic-investigates-outage)) | Opened 14:21, resolved 16:27 |

In this list the model incidents were short, the kind a retry gets past. The 13 November incidents were not: a sign-in outage is one a retry does not fix, because the fix is on Anthropic's side.

## How do you keep working through the next Claude outage?

**Set up a spare Anthropic API key, Bedrock or Vertex AI credential before an outage, subscribe to status.claude.com updates, avoid a Claude login that depends on a single mailbox, and commit before long Claude Code runs.**

- **Keep a spare credential ready.** An Anthropic API key, or Bedrock or Vertex access, set up and tested on a quiet day. During an outage the Console you would create it in may be down too.
- **Subscribe to status updates.** status.claude.com sends incident updates by email, SMS, Slack, Microsoft Teams or webhook, so you hear about it before you start debugging your own setup.
- **Don't route your Claude login through a single mailbox you can lose.** If your work email is on Microsoft 365, the 12 to 13 November outage showed that a mail outage can lock you out of Claude too.
- **Check scheduled work afterwards.** After the second incident, scheduled tasks and routines ran late and some runs were skipped; rerun anything that matters.
- **Commit before long runs.** If access drops mid-task, committed work is safe. Files Claude Code changed with its own tools can be rolled back with `/rewind`; see [Claude Code deleted my files](/blog/claude-code-deleted-my-files) for the full recovery steps.

**Key takeaways**

- Claude went down twice on 13 November 2026: a sign-in outage from 09:58 to 11:58 UTC and a wider outage, including the Claude API, from 13:09 to 15:38 UTC. Both were resolved the same day.
- Anthropic has not published a cause for either incident. The Microsoft 365 outage was a separate incident that affected only the Microsoft 365 connector and Claude for Outlook.
- 'Failed to authenticate. API Error: 403 Attention Required! | Cloudflare' meant Claude Code got Cloudflare's challenge page instead of a token. During an incident, wait or use an API key; when nothing is down, check your VPN or network.
- The same 403 also hit running sessions as 'Please run /login · API Error: 403 Attention Required! | Cloudflare'. Retry once, then stop the task rather than let it spend tokens.
- An API key, Bedrock or Vertex AI gets Claude Code around a claude.ai sign-in outage, but not an outage that includes the Claude API.
- Check status.claude.com first; only Anthropic can say when an incident is resolved.

## FAQ

If your terminal shows a capacity error rather than a sign-in failure, [Claude Code 529 Overloaded](/blog/claude-code-529-overloaded-retry-behaviour) covers retries and switching models. If you ran out of usage rather than access, [Claude limit reset](/blog/claude-limit-reset) explains the free full reset that is usable until 10 December 2026. Every other Claude Code error is in the [Claude Code troubleshooting](/blog/claude-code-troubleshooting) hub.

## FAQ

### Is Claude down right now?

Check status.claude.com for the current status; this answer describes 13 November 2026. That day Claude had two separate outages. From 09:58 to 11:58 UTC, signing in to claude.ai and Claude Code failed while the Claude API stayed Operational. From 13:09 to 15:38 UTC, a second incident caused errors on claude.ai, the Claude API, Claude Code, Claude Cowork and connectors such as Claude Docs and Claude Sheets. Both were resolved the same day.

### What caused the Claude outage on 13 November 2026?

Anthropic has not published a cause for either incident. The first, opened at 09:58 UTC, said: 'We are investigating an issue with users authenticating to Claude.ai and Claude Code.' A fix was deployed at 11:05 UTC and it was resolved at 11:58 UTC. The second, from 13:09 to 15:38 UTC, was described as degraded performance across claude.ai, the Claude API, Claude Code and connectors. A separate Microsoft 365 incident affected only the Microsoft 365 connector and Claude for Outlook.

### Was Claude down because of the Microsoft outage?

Not according to Anthropic's status page. The Microsoft 365 outage broke the Microsoft 365 connector (mail, calendar and search tools) and Claude for Outlook from 16:03 UTC on 12 November to 16:40 UTC on 13 November. The two 13 November outages on claude.ai, Claude Code and the API were listed as separate incidents with no cause given. The two could overlap for you if your Claude login code goes to an Outlook or Microsoft 365 work address, because that email may not arrive.

### What does 'Failed to authenticate. API Error: 403 Attention Required! | Cloudflare' mean in Claude Code?

Claude Code's request was answered by a Cloudflare challenge page instead of Anthropic's service, so it never got a token or a reply. On 13 November 2026 it was part of Anthropic's sign-in incident. During an incident, wait for it to resolve or use an API key. Outside an incident, a common cause is Cloudflare challenging your network, for example through a VPN, proxy or shared IP; try another network.

### Why does Claude Code say 'Please run /login · API Error: 403 Attention Required! | Cloudflare' in the middle of a session?

On 13 November 2026 developers on Claude Code 2.1.323 reported this 403 in running sessions during Anthropic's sign-in incident: a request sending a tool result back was answered by Cloudflare's challenge page. Cancelling the login prompt and sending the message again usually bought a few more turns, but the error came back and some people were logged out. Retry once; if it repeats, stop the task so it does not keep spending tokens, and use an API key until the incident is resolved.

### Did the Claude API work during the 13 November outage?

During the first incident, yes: the Claude API at api.anthropic.com and Claude on AWS, Google Cloud and Microsoft Foundry stayed Operational from 09:58 to 11:58 UTC, so API keys and cloud providers got around the failing sign-in. During the second incident, from 13:09 to 15:38 UTC, Anthropic listed the Claude API as affected too, so an API key did not help then.

### Does Claude Code work during a claude.ai outage?

It depends on what is down and how Claude Code signs in. If only the claude.ai sign-in is failing, as in the first 13 November incident, Claude Code with an Anthropic API key, Amazon Bedrock or Google Vertex AI keeps working. If the Claude API is affected too, as in the second incident, an API key does not help, though Bedrock or Vertex AI may, if their components stay Operational. Run /status inside Claude Code to see which sign-in you use.

### Should I log out of Claude during an outage?

No. In a sign-in outage like the one on 13 November, a session that still works is the one thing you have. Logging out to 'fix' it puts you back at the step that is failing. Wait for Anthropic to mark the incident resolved, then sign in again if you need to.

### What can I use instead of Claude when it is down?

For chat and writing, ChatGPT or Google Gemini. For a coding agent in the terminal, OpenCode, or Claude Code itself with an API key, Bedrock or Vertex AI when only the claude.ai sign-in is down. For work that must not depend on any provider, a local model through Ollama or LM Studio.

### Where can I track the Claude outage status?

The official source is status.claude.com, where Anthropic posts timestamped updates and a 90-day uptime bar per service. You can subscribe there by email, SMS, Slack, Microsoft Teams or webhook. Downdetector, StatusGator and uptime.com add user reports, which help show whether it is just you.

### How long did the 13 November 2026 Claude outage last?

There were two outages. The sign-in incident ran from 09:58 to 11:58 UTC, about two hours, with a fix deployed at 11:05. The second incident ran from 13:09 to 15:38 UTC, about two and a half hours. Model incidents earlier that month were much shorter: 14 minutes on 8 November and four minutes on 10 November. The Microsoft 365 connector incident lasted about 24 and a half hours.

## Sources

- [Claude Status: Elevated errors on claude.ai, Claude Code, and platform.claude.com (13 November 2026, 09:58 to 11:58 UTC)](https://status.claude.com/incidents/nn11wk485zfn)
- [Claude Status: Elevated errors on claude.ai, the Claude API, and Claude Code (13 November 2026, 13:09 to 15:38 UTC)](https://status.claude.com/incidents/34wq7gxnxvvm)
- [Claude Status: Elevated errors affecting the Microsoft 365 connector (12 to 13 November 2026)](https://status.claude.com/incidents/sqn3fg1l96dl)
- [Claude down? (anthropics/claude-code issue #109508, with mid-session 403 reports, 13 November 2026)](https://github.com/anthropics/claude-code/issues/109508)
- [Mid-session 403 Cloudflare 'Attention Required' auth error burns tokens (anthropics/claude-code issue #109516)](https://github.com/anthropics/claude-code/issues/109516)
- [Claude OAuth Failures (Hacker News discussion, 13 November 2026)](https://news.ycombinator.com/item?id=50480936)
- [Claude AI goes down for thousands of users worldwide as Microsoft outage drags into second day (The Sun, 13 November 2026)](https://www.thesun.co.uk/tech/41012746/claude-ai-crashes-worldwide-microsoft-outage/)
- [Microsoft outage hits AI tools of Anthropic and OpenAI (Times of India, 13 November 2026)](https://timesofindia.indiatimes.com/technology/tech-news/microsoft-outage-hits-ai-tools-of-anthropic-and-openai-companies-status-page-give-details/articleshow/135797316.cms)
- [What would you do if there's a Claude outage? (Reddit r/ClaudeAI)](https://www.reddit.com/r/ClaudeAI/comments/1xuzlpu/what_would_you_do_if_theres_a_claude_outage/)
- [r/claude (Reddit), including 'Microsoft outage means I can't get into Claude' (13 November 2026)](https://www.reddit.com/r/claude/)
- [Claude is down as Anthropic investigates errors across its services (The Next Web, 29 September 2026)](https://thenextweb.com/news/claude-is-down-anthropic-investigates-outage)
- [Is claude.ai down? (Uptime.com)](https://uptime.com/claude.ai)