Somewhat predictably, I feel strongly about the availability of the Bundler API. As a result of the recent downtime (due to load issues), I've come up with a plan that I think can increase the reliability of the Bundler API while removing the burden of maintaining its infrastructure from the Rubygems.org team.
I would like to create a new project that implements only the Bundler Dependency API. It would, at least initially, implement only the Rubygems dependency API that lives at `/api/v1/dependencies`. I think it would be feasible to keep it up to date with rubygems.org in near-realtime using the existing webhook system.
If desired, we could add a rubygems.org subdomain dedicated to this app, or we could host it at a separate domain. Either way, requests to rubygems.org could be redirected to the new service via 302 redirects. The redirects could even be served by the rubygems.org frontend server, so the Rails app would no longer have to respond to dependency requests.
Heroku has volunteered to provide hosting for this API app, but it should be feasible to host it anywhere. Long term, it could even be possible to host it on multiple services for higher availability.
I'll post here again once I have a working Bundler API hosted on Heroku, but getting this live for everyone to use will obviously require at least a little bit of ops work on rubygems.org. I'm happy to do that work myself, or work with someone who already has access to get things going.