Claude Account Bans, Suspensions and Appeals

A poster relays a V2EX debate over whether Claude bans hinge on network environment or chat content, citing two banned $200 accounts and others doing the same work without issue.

After a Claude account ban, logging out is not enough: the machineID in ~/.claude.json must be cleared, and the new account should avoid resume since old sessions link it to the previous organization UUID.

A commenter notes Claude hit over 200 million users even with harsh account bans, and says fully opening up would likely overload its servers.

The author subscribed to Claude Max 5x using CN KYC, a U card and a Taipei timezone, logging the upgrade from Pro and promising to report back if the account gets banned.

The author argues Claude's mass bans stem from US compliance deadlines and high token costs, not Dario's past at Baidu.

A user asks whether having Claude help configure circumvention proxy settings will get their account banned.

A reply jokes that beyond remote management software, what people need is a remote computer where running Claude won't get the account banned.

After his Claude account was banned, the author tried all major models, still rates Opus 5.5 top, and reopened a Max plan with precautions to see how long it lasts.

A reply notes that daily TikTok use caused no trouble, yet the user's Claude account was banned.

A reply says Anthropic bans blacklist the linked email and phone, so it advises starting over with incognito mode, a clean Google account and a residential IP.

The author says their Claude 5x account was banned, so they now subscribe via the App Store and rotate Plus plans as weekly quotas run out.

A user's newly purchased Claude Pro account was banned after two days of heavy use; the official email cited only a policy violation, and the account was accessed via an unofficial relay.