# Dedicated endpoint getting 429 errors

**URL:** <https://discuss.huggingface.co/t/dedicated-endpoint-getting-429-errors/155707>\
**Category:** Intermediate\
**Created:** [May 18, 2025, 2:06am UTC](https://discuss.huggingface.co/t/dedicated-endpoint-getting-429-errors/155707 "2025-05-18T02:06:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Kevinger](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/kevinger/32/29985_2.png) [@Kevinger](https://discuss.huggingface.co/u/Kevinger)\
**Post date:** [May 18, 2025, 2:06am UTC](https://discuss.huggingface.co/t/dedicated-endpoint-getting-429-errors/155707/1 "2025-05-18T02:06:15Z")

</div>

I’m getting these errors which I don’t understand given I’m a ‘pro’ subscriber and these are dedicated endpoints. What can I do to either diagnose or work with these errors appropriately?

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [May 18, 2025, 2:23am UTC](https://discuss.huggingface.co/t/dedicated-endpoint-getting-429-errors/155707/2 "2025-05-18T02:23:10Z")

</div>

I’ve heard that this tends to happen in IPv6 environments, but I think it’s basically a bad error. Paid service issue. @meganariley

> [@Getting 429 Error for sentence-transformers/all-mpnet-base-v2](https://discuss.huggingface.co/t/getting-429-error-for-sentence-transformers-all-mpnet-base-v2/107670):
>
> Hi Everyone, I faced this rate limit error for the first time for sentence-transformers. 429 Client Error: Too Many Requests for url: [https://api-inference.huggingface.co/pipeline/feature-extraction/sentence-transformers/all-mpnet-base-v2](https://api-inference.huggingface.co/pipeline/feature-extraction/sentence-transformers/all-mpnet-base-v2) Anyone else faced this? How we can avoid this error?

> [@How does the hub handles http error 429?](https://discuss.huggingface.co/t/how-does-the-hub-handles-http-error-429/147346):
>
> Hi ! I have trouble trying to experiment with [mistralai/Mistral-Small-3.1-24B-Instruct-2503](https://huggingface.co/mistralai/Mistral-Small-3.1-24B-Instruct-2503) because any attempt to use it in python code or downloading, either with git clone or huggingface hub CLI throws error codes 429. I had the issue last thursday, friday, and this monday. I do not face the same issues with other models. I’m really scrapping my head there so I would like a complete explanation about how and when does HF hub returns that code : Here are a few questions that came to my mi…

---

<div class="post-metadata">

**Author:** ![Kevinger](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/kevinger/32/29985_2.png) [@Kevinger](https://discuss.huggingface.co/u/Kevinger)\
**Post date:** [May 18, 2025, 11:33am UTC](https://discuss.huggingface.co/t/dedicated-endpoint-getting-429-errors/155707/3 "2025-05-18T11:33:14Z")

</div>

Thanks for those references; the piece that has me scratching my head is that all the similar messages I’ve found similar to those are either using free accounts/access or not on the dedicated endpoints. In my case these are dedicated endpoints that I’ve set up and I’m on a “pro” account, both used in the attempt to not hit any errors like these.

I’m not seeing any way to reach out to “pro” account support to see if these are bad errors or accurate ones…not sure what to do.

---

<div class="post-metadata">

**Author:** ![Kevinger](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/kevinger/32/29985_2.png) [@Kevinger](https://discuss.huggingface.co/u/Kevinger)\
**Post date:** [May 21, 2025, 12:08am UTC](https://discuss.huggingface.co/t/dedicated-endpoint-getting-429-errors/155707/4 "2025-05-21T00:08:22Z")

</div>

I’ve been working on these endpoints for different functional reasons and with noticed the 429 dissipated quite a bit while tuning and tweaking. Now that they’re functioning as expected, the errors are back. Is there really no way to get some support or attention to what’s causing these?

I’m a paying customer/subscriber with dedicated endpoints (so paying for those as well) so this is frustrating…I’ve introduced some random `wait` times and am trying other hacky things to somehow work around these opaque problems.

Is there any guidance from anyone at HF to try?

---

<div class="post-metadata">

**Author:** ![John6666](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/john6666/32/27664_2.png) [@John6666](https://discuss.huggingface.co/u/John6666)\
**Post date:** [May 21, 2025, 5:19am UTC](https://discuss.huggingface.co/t/dedicated-endpoint-getting-429-errors/155707/5 "2025-05-21T05:19:57Z")

</div>

> **[Expert Support – Hugging Face](https://huggingface.co/support)**
>
> We’re on a journey to advance and democratize artificial intelligence through open source and open science.

If you use Hugging Face’s paid service, I think it’s best to use Expert Support as well. I haven’t been told anything in particular. I’m just a user.
