- Level
- confirmed
- Worst impact
- Partial outage
- Components
- pypi.org - Backends
- Down Index
- 33of 100
What to do
Check whether you use PyPI pypi.org - Backends. Check your stack
Drop a package.json, lockfile, Terraform or a list of domains at down.guide to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 2d 13h it lasted.
Anything that failed between 2025-05-24 23:37 UTC and 2025-05-27 12:53 UTC may need a replay.Subscribe to PyPI's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=pypi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from PyPI 6
- investigating
We are working to investigate a partial outage in the PyPI backends.
provider
- identified
We have identified a large increase in CDN cache misses causing excess load on our backends. We are working to determine the reason for this increase.
provider
- identified
We have identified a flood of requests from a cluster using the python-requests/2.32.3 User-Agent, and attempting to hit all JSON project/releasese en masse. This causes excessive cache misses, which are overwhelming our backends. A temporary block has been put in place.
provider
- monitoring
Our block is in place and systems are stable, but we are not satisfied with having to block such a generic user-agent. If you are aware of a system that began a mass crawl of PyPI's JSON release endpoints starting at around 22:05 UTC 2025-05-25, please contact admin@pypi.org.
provider
- monitoring
We have removed the temporary block and are continuing to monitor.
provider
- resolved
We have not seen a return of the traffic that caused this incident after removing the temporary block. We will open a new incident if we need to take action again.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-7f730c5cf4
Is PyPI still down?
No, this incident was resolved 2025-05-27 12:53 UTC. For PyPI's live state, see https://down.guide/providers/pypi.
How long did it last?
2d 13h, from 2025-05-24 23:37 UTC to 2025-05-27 12:53 UTC, by the times PyPI posted.
What was affected?
PyPI named pypi.org - Backends.
What caused it?
PyPI hasn't published a root cause. If it does, it shows here.
Where does this come from?
PyPI's official status page, https://status.python.org, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.