403 Forbidden: Your storage patterns tripped our internal systems! Please contact us at ``website@huggingface.co`` so we can verify your account and unlock more storage for your use-case

Hello,

I am Abhranil an research masters student at UWaterloo and have an upcoming paper deadline. Any help wold be very apprecaited.

When I try to upload a model be it via a script or on the vebsite itself, I am getting this error since 2 weeks. I have been uploading checkpoints ofr my project since April 2025 and did not face any issues, but recently this started. I have also mailed website@huggingface.co as suggested but no solution yet. Please help:

403 Forbidden: Your storage patterns tripped our internal systems!
Please contact us at ``website@huggingface.co`` so we can verify your account and unlock more storage for your use-case.

  1. My account shows 100 GB private storage available and 0 GB used.
  • My account shows 100 GB private storage available and 0 GB used.

  • I created a new access token with write permissions and logged in with huggingface-cli login, but the issue persists.

  • Moreover all my models are public yet this issue is recently happening

Could you please check why my account is blocked and help me unlock the storage usage?

Thank you!

Similar cases have been reported.
Anyway, it’s best to contact HF by email first… website@huggingface.co

Hi @abhranil14 can you please email website@huggingface.co? We can take a closer look.

Thanks!

Hi @meganariley I faced the same issue with @abhranil14.
I emailed website@huggingface.co two days ago but no reply yet.
can you check again?

Hi @r2911 Please email website@huggingface.co or api-enterprise@huggingface.co once more :slight_smile: We can take a look!

Hi! I’m providing an update here. If you’re seeing this message and you’d like to unlock more storage, share your support of ļø Hugging Face by upgrading your account to PRO, Team, or Enterprise! For more info, check out our documentation on storage limits. A PRO subscription will also includes perks like 20x more inference usage, 8x ZeroGPU quota, 10x private storage capacity and more.

hi, any further information of this issue?

i met the similar one, and i’m 100% sure this is not caused by our organization quota.
and this issue only happens in some repos, even public repos.

so how did you finally solved that problem?

And i found that we cannot make the private repos public anymore, so i guess maybe there is a limit of public repositories now, but just nobody tell us what the limit is, just ā€˜buy PRO/Team/Enterprises’.:melting_face:

the same issue for public repo, and can’t change the model visibility.