# How does the hub handles http error 429?

**URL:** </static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhow-does-the-hub-handles-http-error-429%2F147346%3E%5C
**Category:** 🤗Hub\
**Created:** [March 25, 2025, 1:17pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhow-does-the-hub-handles-http-error-429%2F147346 "2025-03-25T13:17:32Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![vchalmel-naomis](https://avatars.discourse-cdn.com/v4/letter/v/b487fb/32.png) [@vchalmel-naomis](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Fu%2Fvchalmel-naomis)%5C
**Post date:** [March 25, 2025, 3:18pm UTC](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhow-does-the-hub-handles-http-error-429%2F147346%2F3 "2025-03-25T15:18:59Z")

</div>

Thanks for your answer ! It was in fact linked to my 6th question… And IPV6

I got the same error with a docker pull which led me in a rabbit hole where I found that some services (including docker hub and hugging face hub) are using rate limit methods intended only for IPv4 and so, are de facto blocking / only checking the first half of IPv6 adresses so it is entire ranges that are blocked at a time…

So as a workaround I can just disable IPV6 in ubuntu /etc/sysctl.conf…

---

_[View the full topic](/static-proxy?url=https%3A%2F%2Fdiscuss.huggingface.co%2Ft%2Fhow-does-the-hub-handles-http-error-429%2F147346)._