# Rubygems : le problème « Too Many Requests » réapparaît !

**URL:** <https://meta.discourse.org/t/rubygems-too-many-requests-problem-returns/102499>\
**Category:** Product Support\
**Created:** [Novembre 21, 2018, 10:33 UTC](https://meta.discourse.org/t/rubygems-too-many-requests-problem-returns/102499 "2018-11-21T22:33:57Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [Novembre 21, 2018, 10:33 UTC](https://meta.discourse.org/t/rubygems-too-many-requests-problem-returns/102499/1 "2018-11-21T22:33:57Z")

</div>

I’ve got a couple builds failing due to rubygem rate limiting. (One at Digital Ocean, another at a COLO outside Boston).

I thought that there was a recent update to the base Docker image that was supposed to mitigate this. It’s hard to find the error in the output too, since lots of stuff happens after those errors.

If you have a build that failed, you might search for “429 Too Many Requests”.

A year ago, the answer was:

> [@Update failing due to rate limiting by RubyGems](https://meta.discourse.org/t/update-failing-due-to-rate-limiting-by-rubygems/64636/34):
>
> I conferred with the bundler folks about this issue and **they told me it was a known issue with older versions of bundler. If your users update their bundler version, the issue should go away.**
> 
> The errors are actually fastly throttling individual users, which as you might expect means that those versions of bundler are sending A LOT of requests.

Perhaps there has been a regression in `bundler`?

---

_[View the full topic](https://meta.discourse.org/t/rubygems-too-many-requests-problem-returns/102499)._