While I am fully aware that there is no SLA regarding pypi.org, I cannot refrain to observe few problems include:
https://pypi.org/help/#feedback — does not mention anything about who to contact, which issue tracker to use about infrastructure problems. Mainly the entire page is made in such way that the only issues tracker linked is the warehouse one, which is clearly not the right place for tracking operations, stuff specific to pypi.org deployment. I really doubt this was accidental as a lot of effort was spent into writing the about section.
Fastly is mentioned as a sponsor but nothing more than a polite way of saying “if you are not pleased with pypi.org uptime, build your own”.
For the last ~5 hours, openstack seen a huge number of bad results from fastly mirrors which affected our CI, visible on http://status.openstack.org/elastic-recheck/ – fastly does not even report any kind of issue, everything is green on their side! The same happens with status.pypi.org, which also reports everything green.
What happens is that the CDN reports 404 for packages that were published weeks ago.
After checking on irc, I was asked to raised https://github.com/pypa/warehouse/issues/8260 – which was shortly closed in a …questionable manner.
What makes is even more frustrating is the fact that build your own mirror is is suggested as a solution to the problem but there is direct refusal of providing a non CDN endpoint for those that do want to build a mirror. As one would know, using fastly CDN as a source for building a mirror would only produce a mirror that is less reliably than fastly.