# Rate limited for no reason?

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frate-limited-for-no-reason%2F158263%3E%5C
**Category:** 🤗Hub\
**Created:** [June 6, 2025, 2:32pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frate-limited-for-no-reason%2F158263 "2025-06-06T14:32:26Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![sleeping4cat](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/sleeping4cat/32/29463_2.png) [@sleeping4cat](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fsleeping4cat)%5C
**Post date:** [June 6, 2025, 2:32pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frate-limited-for-no-reason%2F158263%2F1 "2025-06-06T14:32:26Z")

</div>

I had been running some evals and during that time, I was hitting HF conncection error and then when I checked to access the HF website I realised, HF had rate limited me for no apparent reason. Can this be resolved?

@ArthurZ

**email:** [sleeping4cat@gmail.com](mailto:sleeping4cat@gmail.com)

---

<div class="post-metadata">

**Author:** ![sleeping4cat](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/sleeping4cat/32/29463_2.png) [@sleeping4cat](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fsleeping4cat)%5C
**Post date:** [June 6, 2025, 2:33pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frate-limited-for-no-reason%2F158263%2F2 "2025-06-06T14:33:22Z")

</div>

I can access the website now but I still am seeing errors with my API

---

<div class="post-metadata">

**Author:** ![meganariley](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/meganariley/32/56966_2.png) [@meganariley](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fmeganariley)%5C
**Post date:** [June 6, 2025, 2:35pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frate-limited-for-no-reason%2F158263%2F3 "2025-06-06T14:35:12Z")

</div>

Thanks for reporting, we’re looking into it!

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2FJohn6666)%5C
**Post date:** [June 6, 2025, 2:57pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Frate-limited-for-no-reason%2F158263%2F4 "2025-06-06T14:57:30Z")

</div>

![429ratelimited](https://us1.discourse-cdn.com/hellohellohello/original/3X/b/8/b8a461b23a90a1c04f7bfe55321b978d580e5ea1.png)  
There may be other possibilities, but I think it was probably because the hub crashed. I was surprised when I encountered this too.

Everything is fine now.

> **[Hugging Face status](/static-proxy?url=https%3A%2F%2Fstatus.huggingface.co%2F)**
>
> Welcome to Hugging Face status page for real-time and historical data on system performance.