Claude Code 403 "Request blocked" and "Attention Required! | Cloudflare"
Claude Code's 403 from the network edge, not your login: check the server's country, VPN or proxy for "Request blocked"; the Cloudflare page clears on retry.
Both are an HTTP 403 from the network edge in front of Anthropic’s API, before your request reached it, and neither is fixed by signing in again. “Request blocked before it reached Anthropic’s API” means the edge refused the address your request came from: check that the machine running Claude Code is in a country on Anthropic’s supported list (on a server, run curl https://ipinfo.io/country there) and that no VPN or proxy sits in its path. “403 Attention Required! | Cloudflare”, often shown with “Please run /login”, is a Cloudflare block page: users report it comes and goes, and that the same session worked again when resumed later without a new login. Wait, send the message again, and check status.claude.com before touching your credentials.
The two messages
The first is Claude Code’s own explanation of the refusal, and it says most of what there is to know:
API Error: Request blocked before it reached Anthropic's API (HTTP 403) · the network this request came from isn't allowed: usually an unsupported region, or a VPN, proxy or hosting network · signing in again won't change this · check your VPN or network and retry · supported regions: https://anthropic.com/supported-countriesCopiedUsers have reported it on Claude Code 2.1.318 from early November 2026 and since. The second carries the title of a Cloudflare challenge page where Anthropic’s answer would be. In the terminal it reads:
Please run /login · API Error: 403 Attention Required! | CloudflareCopiedand in a headless run (claude -p) or the Agent SDK:
Failed to authenticate. API Error: 403 Attention Required! | CloudflareCopiedwith the error type authentication_failed. Reports of it run from Claude Code 2.1.322 to 2.1.329. Anthropic’s errors reference has no entry for either message as of November 20, 2026.
“The network this request came from isn’t allowed”
The refusal is about where the request came from, not who sent it, so your account and your login are not the problem, as the message itself says. The address it judges is that of the machine running Claude Code: on a server, the server’s, wherever you are sitting. Work through what the message names.
The region. Anthropic’s Supported Regions Policy covers its apps, Claude Code by name, and its API, and lists the countries they serve; China, Hong Kong and Russia are not on it, and Ukraine is, except Crimea, Donetsk, Kherson, Luhansk and Zaporizhzhia. To see the country the server’s traffic appears to come from, run this on the server:
curl https://ipinfo.io/countryCopiedIt prints a code such as DE. It is a check, not Anthropic’s verdict: address databases disagree at the edges, as the region guide covers for the other labs too.
A VPN or a proxy. On a laptop, a VPN client is the usual one. On a server, look for a proxy set in the environment (env | grep -i proxy) or a tunnel the machine’s traffic goes out through, since the address Anthropic sees is then the far end’s.
A hosting network. The message names hosting networks among the usual causes, which matters because a VPS is on one. Anthropic does not say which networks it means, and the message names them as a usual cause rather than a rule, so the refusal is a judgment about that address; it does not say that servers in general are turned away.
Intermittent refusals. Not every report fits the list. The longest thread began with a user in a supported country on a mobile connection, whose message was refused four times in five, with an immediate resend sometimes going through; another came from a phone hotspot in Ukraine. Anthropic has not commented on either issue. If the server’s country is on the list, nothing stands between it and the internet, and the refusal persists, report it with the server’s address: in that thread /feedback was refused too, and Claude Code then points you to its GitHub issues.
The policy also covers where you are. Anthropic lists as unsupported any use by people “while physically located in an unsupported region”, so sending Claude Code’s traffic out through another country is not a way to use it from somewhere the list leaves out. If you are in a supported country and the server is not, the fix is a server in one that is.
“403 Attention Required! | Cloudflare”
“Attention Required!” is the title of a Cloudflare page, returned where an API answer should be; Claude Code shows the title of an HTML page that answers in the API’s place, as its errors reference describes for a proxy’s own 429 page. The “Please run /login” in front of it comes with the error type authentication_failed, which Claude Code gives this block in users’ reports. It is not evidence that your login failed. What users report, and it is their report, since Anthropic has not explained the block:
- It comes and goes. One user on the main thread saw it in two windows of a few minutes on November 13, 2026, while other sessions on the same machine kept working, and the failed ones worked again when resumed later without
/login. A user on a residential connection in Taiwan, with no VPN or proxy, wrote in the issue its duplicates are closed into that resending “works afterwards without re-login.” - It recurs. The November 13 reports fall in the same hours as an incident Anthropic posted on status.claude.com that day, “investigating an issue with users authenticating to Claude.ai and Claude Code”, from 09:58 UTC and resolved at 11:58; the incident does not mention a 403, and a report on 2.1.329 has the same block on November 20.
So send the message again or resume the session after a few minutes, and check the status page. Signing in again does no harm, but if the next request fails the same way the login was never the cause. A real credential problem prints its own message: Not logged in, Login expired or a 401, which the login guide sorts out. If the Cloudflare page appears on every request for hours, treat it as the network question above. Claude Code’s own Remote Control message for an edge refusal names both possibilities, “Anthropic’s CDN enforcing a region or network policy, or a Cloudflare gateway on this network”, so a corporate network that filters traffic through Cloudflare is worth ruling out too.
In a scheduled or unattended run
The Cloudflare 403 is not retried, in users’ reports: the turn ends and the run stops until someone notices. Two things follow for a job on a server.
A headless run reports the Cloudflare block as authentication_failed, the same structured code the errors reference gives for an expired or revoked login. A wrapper that answers that code by asking a person to sign in again will do so for a block that clears on its own; one that also reads the message text can tell the two apart, and retrying a run that ended this way after some minutes is what users found worked. A goal set with /goal is dropped as well:
Goal cleared after an unrecoverable error (authentication failed): "<goal>". Run /goal again to continue.Copiedso a retry has to set it again. The scheduled-run guide covers hearing back when a job fails. And if your organisation forces a login through managed settings, versions before 2.1.326 printed a startup error asking you to sign in again when a network block page (HTTP 403) was the cause; update Claude Code to see the real reason. A request that never connects at all, rather than being refused, is a different failure, with its codes in the connection guide.