I think there’s really two answers here. Firstly, this specific issue turned out to be due to misconfiguration of our rsync server, which was causing ridiculous levels of bandwidth. That’s on us, and credit to @evgeni for finding it and fixing it.
More generally though, on Red Hat contribution - Red Hat does contribute greatly to the project, in a lot of ways. It so happens that the website & mirrors aren’t one of those, that sponsorship comes from Rackspace (and we’re grateful for that, very much so). We also have numerous other sponsors that provide hardware, CDN coverage and more, and that’s a good thing. I don’t think it’s healthy to be solely dependant on one company (this actually almost happened when Rackspace considered puling the plug on it’s Open Source discount program and all our hosting was there).
However, the corollary is that it’s on us as a community to make the best use of the resources these organisations (and individuals) provide. While the end result here was a misconfiguration, and no one had to lose out, that doesn’t negate the future possibility that we may have to drop something else (for an example, consider @tbrisker’s thread on ARM packages). Everything has cost, no budget is infinite, and sometimes you have to make hard choices.