[BUG] Appeal Form Redirect Loop After Account Restriction

Open 💬 37 comments Opened May 26, 2026 by ianbandrade

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

After my account restriction, the appeal form link provided by Anthropic does not open correctly. Instead of loading the appeal page, it redirects me to claude.ai/new, making it impossible to submit an appeal request.

The issue appears to be a redirect loop or broken authentication/session handling related to restricted accounts.

https://github.com/user-attachments/assets/47b040a5-a4e1-489d-bc4a-9bcb9570a0f5

What Should Happen?

The appeal link should open the appeal submission form normally so restricted users can request a manual review.

Error Messages/Logs

400 - This organization has been disabled.

Observed behavior:

- Clicking the appeal form link
- Browser redirects to claude.ai/new
- Appeal form never loads

Additional context:

- Restriction occurred shortly after using the /compact command
- Account had been used for approximately 1 hour before the restriction
- Usage was for a personal autonomous video generation project

Steps to Reproduce

  1. Receive account restriction email from Anthropic
  2. Click the provided appeal form link
  3. Get redirected to claude.ai/new
  4. Appeal form never appears
  5. Repeating the process results in the same redirect behavior

https://github.com/user-attachments/assets/47b040a5-a4e1-489d-bc4a-9bcb9570a0f5

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

_No response_

Claude Code Version

2.1.150

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

_No response_

View original on GitHub ↗

37 Comments

kewedom · 1 month ago

I have the same problem

CHOCH2R · 1 month ago

I ran into the same problem too; how did you solve it?

ianbandrade · 1 month ago
I ran into the same problem too; how did you solve it?

Still haven't :(

Kusdianta · 1 month ago

Same issue here.

Clicked the appeal form link in the suspension email → redirects to claude.ai, no form, no way to appeal.

This broken appeal path means there is literally no recourse for users who believe their suspension is a false positive.
Requesting a working appeal channel or direct human review.

AnliC24 · 1 month ago

me too, why? i‘m developer

CHOCH2R · 1 month ago
> I ran into the same problem too; how did you solve it? Still haven't :(

I might have found a useful link: https://docs.google.com/forms/d/e/1FAIpQLSdtyS8ONgH8vi6NrUpQ2lfsjSPGTZ1bW_i-E7XtGDcDZxbKeQ/viewform

CHOCH2R · 1 month ago
CHOCH2R · 1 month ago
Same issue here. Clicked the appeal form link in the suspension email → redirects to claude.ai, no form, no way to appeal. This broken appeal path means there is literally no recourse for users who believe their suspension is a false positive. Requesting a working appeal channel or direct human review.

This link may help: https://docs.google.com/forms/d/e/1FAIpQLSdtyS8ONgH8vi6NrUpQ2lfsjSPGTZ1bW_i-E7XtGDcDZxbKeQ/viewform

martinmarquez · 1 month ago

I'm Having the same issue, my account was suspended, no way to appeals, the email I sent is automatic responses, as a developer is super useful to count with claude code, not being able to use it means not having the same power as others. It's a relly upsetting situation, happy to avoid any problem in the future, but I didn't even get a warn first.

douglascorrea · 1 month ago

I have the same issue

douglascorrea · 1 month ago

This is an official page and they have they appeal form link there, I only trust on that one:

https://support.claude.com/en/articles/14328960-identity-verification-on-claude#h_436ca483e1

asakurayoh · 24 days ago
This is an official page and they have they appeal form link there, I only trust on that one: https://support.claude.com/en/articles/14328960-identity-verification-on-claude#h_436ca483e1

It's that link that is not working...

ishaanman7898 · 23 days ago

I've been having the same issue, thank you @CHOCH2R for the appeal link.

lukeask · 20 days ago

I was investigating this bug and I will share more info if Anthropic responds to my email requesting permission to do so. I can confirm that the form intended to be accessed at /restricted is not a google form, so it is in my opinion unlikely that the google form mentioned in this thread is sending your data to Anthropic.

dipnangle · 18 days ago

I have the same problem like video shared

BUAA-David · 17 days ago
I was investigating this bug and I will share more info if Anthropic responds to my email requesting permission to do so. I can confirm that the form intended to be accessed at /restricted is not a google form, so it is in my opinion unlikely that the google form mentioned in this thread is sending your data to Anthropic.

So did Anthropic reply to your email?

KyleLenout · 16 days ago

Same issue. I tried the google doc here without any response. https://x.com/KYLEN_OUT/status/2071949035683115357?s=20

BENZOOgataga · 16 days ago
MisterCalvinB · 16 days ago

The same thing happened to me this morning. My account was upgraded to Max during the night without my permission; 30 minutes later my account was suspended. And now I cannot appeal the suspension because I'm stuck with the redirect to claude.ai/new !

BENZOOgataga · 15 days ago

I did a bit more debugging on my end in case it helps.

  • I captured multiple HAR files, including one while refreshing directly on https://claude.ai/restricted.
  • I don't see any HTTP redirect from /restricted. The navigation appears to happen client-side.
  • The first bootstrap request (/edge-api/bootstrap/.../app_start) returns 200 OK, not a 403 or another restricted-account response.
  • After the app initializes, it consistently ends up on https://claude.ai/new.
  • The bootstrap response includes api_disabled_reason: "trust_and_safety" and capabilities: ["chat"].
  • When I try to send a message on claude.ai/new, the API returns 400 Bad Request with:
{
    "type": "error",
    "error": {
        "type": "invalid_request_error",
        "message": "This organization has been disabled.",
        "details": {
            "error_code": "organization_disabled",
            "error_visibility": "user_facing"
        }
    },
    "request_id": "req_ABC"
}
  • Local Storage and Session Storage are empty, and I couldn't find any obvious cookie indicating a restricted/banned state.

From what I can tell, this looks like the frontend isn't recognizing my current account state as one that should stay on /restricted, so it falls back to /new instead. I'm not sure whether that's expected or a bug, but I figured these observations might help narrow it down.

I also captured several HAR files while reproducing the issue. They contain authentication/session information, so I haven't attached them publicly, but I'm happy to provide redacted versions or share them privately if they'd help investigate.

Edit: Small follow-up: I also checked current_user_access. It reports chat as available, along with several org/API permissions as available, even though the completion endpoint returns organization_disabled.

So the frontend seems to receive an "available" access state during initialization, but the chat API later rejects the org as disabled. This may explain why the app loads /new instead of keeping me on /restricted.

KyleLenout · 15 days ago
I did a bit more debugging on my end in case it helps. I captured multiple HAR files, including one while refreshing directly on https://claude.ai/restricted. I don't see any HTTP redirect from /restricted. The navigation appears to happen client-side. The first bootstrap request (/edge-api/bootstrap/.../app_start) returns 200 OK, not a 403 or another restricted-account response. After the app initializes, it consistently ends up on https://claude.ai/new. The bootstrap response includes api_disabled_reason: "trust_and_safety" and capabilities: ["chat"]. When I try to send a message on claude.ai/new, the API returns 400 Bad Request with: { "type": "error", "error": { "type": "invalid_request_error", "message": "This organization has been disabled.", "details": { "error_code": "organization_disabled", "error_visibility": "user_facing" } }, "request_id": "req_ABC" } * Local Storage and Session Storage are empty, and I couldn't find any obvious cookie indicating a restricted/banned state. From what I can tell, this looks like the frontend isn't recognizing my current account state as one that should stay on /restricted, so it falls back to /new instead. I'm not sure whether that's expected or a bug, but I figured these observations might help narrow it down. I also captured several HAR files while reproducing the issue. They contain authentication/session information, so I haven't attached them publicly, but I'm happy to provide redacted versions or share them privately if they'd help investigate.

You should be working for Anthropic.

BENZOOgataga · 15 days ago
You should be working for Anthropic.

Would love to, but I only want to be unbanned 😭

dipnangle · 14 days ago

Is that Google form is from anthropic side or just collecting our data ?

KyleLenout · 14 days ago
Is that Google form is from anthropic side or just collecting our data ?

Honestly there's a solid chance that it didn't come from Anthropic at all. It seems weird that a tech company like Anthropic would rely on a Google form as a backup. They don't acknowledge or deny the presence of this discussion, so, it's free roam for potential scammers and data collectors.

BENZOOgataga · 14 days ago
> Is that Google form is from anthropic side or just collecting our data ? Honestly there's a solid chance that it didn't come from Anthropic at all. It seems weird that a tech company like Anthropic would rely on a Google form as a backup. They don't acknowledge or deny the presence of this discussion, so, it's free roam for potential scammers and data collectors.

I have not seen Anthropic redirect to that form in any way, and the google form has been originally shared by a random user on Reddit claiming they've got it from Anthropic support which we have no confirmation. I think it's not from Anthropic at all.

dipnangle · 13 days ago
> > Is that Google form is from anthropic side or just collecting our data ? > > Honestly there's a solid chance that it didn't come from Anthropic at all. It seems weird that a tech company like Anthropic would rely on a Google form as a backup. They don't acknowledge or deny the presence of this discussion, so, it's free roam for potential scammers and data collectors. I have not seen Anthropic redirect to that form in any way, and the google form has been originally shared by a random user on Reddit claiming they've got it from Anthropic support which we have no confirmation. I think it's not from Anthropic at all.

Then how we can unbanned our accounts now

BENZOOgataga · 13 days ago
> > > Is that Google form is from anthropic side or just collecting our data ? > > > > > > Honestly there's a solid chance that it didn't come from Anthropic at all. It seems weird that a tech company like Anthropic would rely on a Google form as a backup. They don't acknowledge or deny the presence of this discussion, so, it's free roam for potential scammers and data collectors. > > > I have not seen Anthropic redirect to that form in any way, and the google form has been originally shared by a random user on Reddit claiming they've got it from Anthropic support which we have no confirmation. I think it's not from Anthropic at all. Then how we can unbanned our accounts now

Wait until they fix the /restricted link I guess

nutza13pks · 12 days ago

Same issue. My organization was disabled ("This organization has been
disabled."), and claude.ai/restricted immediately redirects to
claude.ai/new while logged in with the affected account, so the appeal
form is unreachable.

Emailing usersafety@anthropic.com only triggers an auto-reply linking
back to the same inaccessible form, and the thread is then auto-closed
as "no longer monitored." So there is currently no working path to
submit an appeal for org-disabled accounts.

Org ID: 39ab0767-18f7-44f4-8d93-0e3b8f000204

KyleLenout · 12 days ago
Same issue. My organization was disabled ("This organization has been disabled."), and claude.ai/restricted immediately redirects to claude.ai/new while logged in with the affected account, so the appeal form is unreachable. Emailing [usersafety@anthropic.com](mailto:usersafety@anthropic.com) only triggers an auto-reply linking back to the same inaccessible form, and the thread is then auto-closed as "no longer monitored." So there is currently no working path to submit an appeal for org-disabled accounts. Org ID: 39ab0767-18f7-44f4-8d93-0e3b8f000204

R.I.P. Anthropic customer service

GMobinit · 11 days ago

I’ve encountered the same issue, and there appears to be no way to submit an appeal. This is quite disappointing for a company of this level.

leutds · 9 days ago

+1 — same issue.

  • Account: personal Claude Max (l**********a@gmail.com)
  • Error: 400 "This organization has been disabled" on /login and claude.ai
  • Console API still works (same email) — consumer org disabled, API org active
  • Likely false positive: one login from Dominican Republic; normal usage from US Mac
  • Appeal form redirects to claude.ai/new; usersafety@ returns only Fin auto-replies
  • No human support path found yet

Workaround: Claude Code via Console API key.

BENZOOgataga · 9 days ago
+1 — same issue. Account: personal Claude Max ([leu.tejeda@gmail.com](mailto:leu.tejeda@gmail.com)) Error: 400 "This organization has been disabled" on /login and claude.ai Console API still works (same email) — consumer org disabled, API org active Likely false positive: one login from Dominican Republic; normal usage from US Mac Appeal form redirects to claude.ai/new; usersafety@ returns only Fin auto-replies No human support path found yet Workaround: Claude Code via Console API key.

I've noticed that it's mostly people with organisations that are getting this issue. I'm deleting my organisation to try again the appeal link in a few days and will update you if it works.

BENZOOgataga · 9 days ago

<img width="742" height="546" alt="Image" src="https://github.com/user-attachments/assets/b903e4ab-9162-4441-9611-00e51deaa312" />
Appeal page seems to be back for me!

leutds · 9 days ago
<img alt="Image" width="742" height="546" src="https://private-user-images.githubusercontent.com/50145143/618416753-b903e4ab-9162-4441-9611-00e51deaa312.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODM0NTM3NzUsIm5iZiI6MTc4MzQ1MzQ3NSwicGF0aCI6Ii81MDE0NTE0My82MTg0MTY3NTMtYjkwM2U0YWItOTE2Mi00NDQxLTk2MTEtMDBlNTFkZWFhMzEyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNjA3MDclMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjYwNzA3VDE5NDQzNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTZkMDA3NDdjMTcyYmYwZTMzODgzMDBjOGFjZWZlZGNiNmU2NjM3ZmQzMWZmY2JkOGRiZWIwNzU3ZjQwMDEyOTUmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JnJlc3BvbnNlLWNvbnRlbnQtdHlwZT1pbWFnZSUyRnBuZyJ9.wrOPfI_f_kjliM0UspHi3ZxRcKarP7K9iH_nE3v7DiU"> Appeal page seems to be back for me!

Excellent!! i already sent the review resquest this morning too.

KyleLenout · 8 days ago

Yes and for anyone commenting, don't log in the normal way, go back to the email and click the link or go to claude.ai/restricted .

Going to claude.ai normally did not help (the redirect is still broken).

BENZOOgataga · 8 days ago
Yes and for anyone commenting, don't log in the normal way, go back to the email and click the link or go to claude.ai/restricted . Going to claude.ai normally did not help (the redirect is still broken).

I've directly gone for writing "claude.ai/restricted" link and it works fine

leutds · 1 day ago

+1 — appeal denied after what I believe was an easily verifiable accident. Adding my full timeline for Trust & Safety / engineering visibility.

Account: leu.tejeda@gmail.com (personal Claude Max)

Timeline:

  • ~June 27, 2026: Suspension email (Safeguards — "suspicious signals" / Usage Policy)
  • Same day: API tier upgrade emails — Console API still works; only consumer org disabled
  • Submitted appeal via claude.ai/restricted (two-field "Request a review" form) — status showed "Review requested"
  • July 13, 2026: Appeal denied — "cannot reinstate your account at this time due to a violation of our Usage Policy" (no specific detail provided)

What I believe triggered it:
I left a Claude Code agent session running without a stop/time limit — an accidental runaway loop that spiked token usage. I stopped it once I noticed. This was not scraping, account sharing, or intentional automation — solo development on my own internal business CRM (Node.js). The usage pattern should be distinguishable from malicious abuse in your logs.

Why this feels disproportionate:

  • The root cause was a beginner operational mistake (unbounded agent session), not deliberate policy evasion
  • Safeguards appeal process was broken for many users (/restricted → /new redirect); I eventually got the in-product form to work
  • Console API org remains active — same email, higher tier — while consumer Max is permanently denied
  • I was still billed for Max during the suspension period
  • Refund request via support has not been resolved

Current workaround: Claude Code via pay-as-you-go API — materially more expensive than Max for the same development workflow.

<img width="740" height="594" alt="Image" src="https://github.com/user-attachments/assets/3bd71c21-d91a-41e6-96ed-32ededc65f3c" />

Ask for Anthropic:

  1. Manual re-review of usage logs for the June spike — accident vs abuse
  2. Clear policy guidance: is an accidental unbounded agent loop a permanent ban with no reinstatement path?
  3. Refund/credit for Max subscription during enforced downtime
  4. Fix appeal + billing sync so paying subscribers aren't charged while consumer access is revoked

Happy to provide redacted screenshots (suspension email, appeal denied, "Review requested" status, billing) privately to Anthropic staff.

This isn't about evading rules — it's about proportionality and a broken appeal/refund path for paying customers.