Claude Account Bans, Suspensions and Appeals

A user says they never worried about being banned, and in practice Claude is more tolerant of IP addresses than GPT Pro, though GPT just bans accounts less often.

A user completed KYC and face verification with a Chinese passport, paid for Pro, and stayed unbanned for 24 hours, relaying a follower's tip that the KYC login IP just needs to match Claude's residential IP.

A user who tried Cue says it feels clumsy and falls short of Grok Bot, and warns against using Cue to register a Claude account because it gets banned immediately.

Asked why they haven't moved to Claude, a user replies jokingly that it's because Claude accounts keep getting banned.

A user advises people who keep getting banned to stop fiddling with proxies and instead use Claude's cloud connection to a private GitHub repo.

The poster mocks users who have had seven or eight Claude accounts banned, saying they should first sort out their network environment.

A user asked Manus's Cue to register a Claude account for them, and Claude banned it immediately.

A newly registered Claude account was banned after running a single task, a $20 refund review was rejected, and Codex was used to trace device-linking signals including cookies and persistent CLI identifiers.

The user says they barely open the Claude client after their main account was banned, yet the local cache has still grown to 900M.

The user jokes that Claude's biggest selling point is paying through the Apple Store, since a banned account can still get a full refund.

After looking into how to avoid Claude bans and how refunds work after a ban, the author finds the process extremely troublesome and calls on other model makers to beat Anthropic.

The author sums up Claude ban patterns: normal Pro use is rarely banned, most bans hit 5X/20X accounts reselling quota as API or bought secondhand, proxy choice is irrelevant, and HK card or Google Pay payments tend to get flagged.