Python and PyPI infrastructure status
Python infrastructure, including PyPI and package-file delivery. A package-specific install error is not automatically an infrastructure incident.
Live Domain Check
Is PyPI Down? Check pypi.org Status and Outages
Run a live reachability check for pypi.org. Compare the regional responses with the problem you see in PyPI.
Find PyPI help and reporting links, specific checks, and step-by-step guidance below the live result.
Ready
Running automatic check…
Checking reachability from multiple regions.
Checked
-
Verdict
-
Response Time
-
Final URL
-
Regional checks
Is PyPI working for you?
Share a quick update and see what other visitors are experiencing.
What’s happening? Choose one to send your report.
Loading community reports…
—problem reports
—working reports
Past 24 hours15-minute totals · current interval in progress
Most reported problems
No problems reported in this period.
Visitor reports are separate from our automated checks and don’t confirm an outage. How reports work · Privacy
Understanding PyPI connection and service problems
PyPI website access, package downloads and uploading a release are separate operations.
The checker above requests pypi.org from eight configured locations and shows the responses and measurement times. Compare those observations with the actual PyPI action that failed. A homepage response alone cannot verify an account, app workflow or transaction.
Looking for another service? Browse developer service checks.
PyPI status information and official help
PyPI help and reporting
Use PyPI's documented support path for publishing/account issues; project code bugs go to its maintainer.
Open pypi.org
Open the website in your browser and compare it with the result above.
Where to report problems with PyPI
Open PyPI help / reporting. Use the provider's customer-service or account-help route for the affected product. Sign-in may be required for private account questions.
Details to include in your report
Project/version, pip or upload-tool version, command and error without publishing tokens.
Attach the checker’s downloaded JSON if it helps show the hostname, regional responses and original timestamps. Describe what happened in your browser or app as well. A report sent to WebsiteDown.org is not automatically forwarded to PyPI.
What to check when PyPI is not working
These are troubleshooting comparisons, not claims that PyPI is currently experiencing a particular incident.
Start with the action that failed
Record the package/version and index URL and distinguish resolution, transfer and authentication errors.
Narrow down the affected service
Check the official Python infrastructure status/support information before publishing another release or changing package indexes.
Read the actual checker response
A 403 Forbidden or 429 Too Many Requests means the host answered but refused or limited that request. A timeout gives no HTTP response. Keep those outcomes separate and check the available-region count before treating the result as broad evidence.
How to check if PyPI is down
- Save the error. Note what you were doing and when it failed. Save unfinished work before refreshing.
- Run the pypi.org check. Look at the regional results and when they were checked. Checking again may return a cached result.
- Check for a service notice. Open PyPI status and check whether the named service and incident time fit your error.
- Try another browser or network. Use the specific checks above to narrow down the problem. If it continues, send the error and time through the official help link.
If PyPI Is Not Working Only For You, Start Here
Use these local troubleshooting steps after the down-check workflow when PyPI seems broken only for you. This section focuses on app, browser, account, and network fixes.
1. Compare browser sessions
Open pypi.org in your current browser, then test in a private window or second browser. If only one session fails, compare its account, cookie and extension context before assuming the entire service is unavailable.
2. Preserve a working account session
Keep an existing working session and preserve unsaved work. For a sign-in failure, use the official account-help route. Avoid repeated password or security resets until you confirm this is not a broader PyPI issue.
3. Try another network
If possible, compare Wi-Fi with mobile data and note which one fails. Leave any required work VPN or security settings in place.
4. Capture support-ready evidence
Save timestamp, device, network type, exact error, final URL, and status code. Use the check workflow above before contacting PyPI support.
Frequently asked questions about PyPI problems
Is PyPI down, or is the problem limited to one feature?
Run the pypi.org check and compare its original timestamps and responses with your actual error. PyPI website access, package downloads and uploading a release are separate operations.
Where can I report a problem with PyPI?
Use the community buttons on this page to share whether the service works for you. For help from PyPI, use the official help/reporting resource linked above. Use PyPI's documented support path for publishing/account issues; project code bugs go to its maintainer.
What should I check first when PyPI is not working?
Record the package/version and index URL and distinguish resolution, transfer and authentication errors. Check the official Python infrastructure status/support information before publishing another release or changing package indexes.
What information helps PyPI support investigate?
Project/version, pip or upload-tool version, command and error without publishing tokens.