Package registries
Is PyPI down?
Live PyPI status, measured independently. We probe 6 PyPI endpoints from monitoring regions on every continent and record every outage we detect.
PyPI is up
Our probes are reaching PyPI normally from every region we check from.
Checked every minute from 6 regions on every continent.
- Uptime, 24 hoursUptime, last 24 hours
- Uptime, 7 daysUptime, last 7 days
- Uptime, 30 daysUptime, last 30 days
- Website100% uptime, 30 days6 regions, 6 to 285 msUnknownp50median response54 msp95slowest 5% of checks97 ms200 ms100024 h ago12 h agonow
- Simple index100% uptime, 30 days6 regions, 6 to 336 msUnknownp50median response62 msp95slowest 5% of checks102 ms200 ms100024 h ago12 h agonow
- JSON API100% uptime, 30 days6 regions, 7 to 393 msUnknownp50median response73 msp95slowest 5% of checks124 ms200 ms100024 h ago12 h agonow
- File CDN100% uptime, 30 days6 regions, 86 to 493 msUnknownp50median response176 msp95slowest 5% of checks392 ms500 ms250024 h ago12 h agonow
- docs.python.org100% uptime, 30 days6 regions, 61 to 406 msUnknownp50median response149 msp95slowest 5% of checks333 ms500 ms250024 h ago12 h agonow
- Official status feed83.23% uptime, 30 days6 regions, 178 to 534 msUnknownp50median response309 msp95slowest 5% of checks552 ms500 ms250024 h ago12 h agonow
Daily strip:99.9% or better95–99.9%below 95%no data yet
Get notified when PyPI goes down
Follow these 6 checks from your own workspace and get alerted through Slack, email, webhooks, or on-call the moment PyPI goes down. They don't count against your monitor quota. Free plan, no card required.
About PyPI outages
PyPI serves the packages behind every pip, poetry, pipenv, and uv install. It is run by the Python Software Foundation and fronted by a CDN, so incidents are rare but broad: when PyPI is slow, Python CI and Docker builds fail worldwide.
Package files are served from files.pythonhosted.org, a separate hostname from pypi.org. We probe the site, the Simple index that installers hit first, the JSON API, the file CDN, and docs.python.org.
What we check
Every row is a real monitor in upti.my, running from each of our regions. A failure in some regions marks the row degraded; failures from every region mark it down and open an outage.
| Check | Target | Expects | Interval |
|---|---|---|---|
Website pypi.org is unreachable. | httppypi.org | HTTP 200 | 1 min |
Simple index The Simple API that installers use for resolution is failing. pip and uv cannot resolve packages. | httppypi.org/simple/pip/ | HTTP 200 | 2 min |
JSON API The PyPI JSON API is failing. Tools that read package metadata break. | httppypi.org/pypi/requests/json | HTTP 200 | 2 min |
File CDN The package file CDN is unreachable. Resolution may work while downloads fail. | httpfiles.pythonhosted.org | Any HTTP response | 2 min |
docs.python.org The Python documentation site is unreachable. | httpdocs.python.org/3/ | HTTP 200 | 5 min |
Official status feed The Python infrastructure status page is unreachable. | httpstatus.python.org/api/v2/status.json | HTTP 200 | 5 min |
For component-level detail and incident write-ups from the vendor, see Python infrastructure status page.
Recent PyPI outages we detected
An outage is recorded when a probe fails from every monitoring region and closed when it recovers. Partial and single-region problems show as degraded above but are not listed here.
PyPI is up. Is your PyPI integration?
The incidents that actually hurt are usually not global outages. They are the parts of your own system that depend on PyPI and fail quietly. Here is what teams that rely on PyPI monitor on their side.
Builds and cron jobs that pip install
A container that installs at start-up will fail to boot during a PyPI incident. Monitor the job outcome with a heartbeat and pin or vendor dependencies for critical paths.
Heartbeat monitoringPyPI status: frequently asked questions
Check our Simple index and file CDN probes separately. PyPI incidents sometimes affect only one of the two, and a green result from every region points at a local network or proxy problem instead.
Look at the per-region results above. If our probes fail from every region, PyPI has a real outage and it will appear in the outage list. If they succeed everywhere, the problem is most likely on your side: your network, DNS resolver, a browser extension, a corporate proxy, or your own integration. If only some regions fail, PyPI may have a regional incident that does not affect you.
Every probe runs at least every five minutes from each monitoring region, and most run every minute. This page refreshes its data every minute. Uptime figures are calculated from all checks across all regions.
Official status is updated by people after an incident is confirmed and often lags the first failures by many minutes; our probes react within a minute or two. In the other direction, we only see public endpoints, so an internal incident may not show on our probes. Use both.
Yes. Use "Notify me about PyPI" above: your upti.my workspace follows these exact checks, free plan included, and every outage opens an incident there and routes alerts to Slack, email, webhooks, or on-call. Nothing is duplicated and it doesn't use your monitor quota. Better still, also monitor your own dependency on PyPI: the API route, webhook receiver, or scheduled job that calls it, so you learn about the failure that actually affects your users.
Related
Other package registries
upti.my is not affiliated with PyPI. PyPI and related marks are the property of their respective owners and are used here only to identify the service being measured. Results reflect the reachability of public endpoints from our monitoring regions and may differ from the vendor's own reporting.