PyPI Legacy Sunsetting!
Scheduled Maintenance Report for Python Infrastructure
The backends for the previous generation PyPI have been taken down. This maintenance is complete.

From everyone on the PyPI team, thank you for working with us through this process.

PyPI is dead, long live PyPI.
Posted Apr 30, 2018 - 15:10 UTC
All work to disable access to PyPI 1.0 has been completed.

All requests to `` will now see a redirect to the appropriate URL for the new service.

We are going to spin down the backends over the next hour.

Any remaining impact can be reported at and we'll work to assist you as best we can.
Posted Apr 30, 2018 - 14:26 UTC
We are deploying our CDN configuration to redirect all traffic to to! This will impact Artifactory users who are not running latest releases from JFrog. Please see and for mitigation steps and discussion.
Posted Apr 30, 2018 - 14:19 UTC
In progress
We're commencing the maintenance! The DNS name `` will be disabled, and DNS should propagate over the next 5-10 minutes.
Posted Apr 30, 2018 - 14:10 UTC
Today we'll be sunsetting the original PyPI service.

## Impacted users include:
- Those using `` directly
- Artifactory users not running the latest releases from JFrog

### `` users

You should use ``! If there is a feature that the new codebase does not support, you should file an issue at as soon as possible!

### Artifactory Users who have not upgraded

Please see the [guidance from JFrog]( and [full discussion of the issue](

### Any other impacted users

Let us know! File an issue with our [issue tracker](
Posted Apr 30, 2018 - 13:42 UTC