← Back to PyPI History
major✓ Resolved

PyPI Partial Outage

PyPI•
Status
resolved
Duration
2d 13h
Updates
6
Coverage
0 articles

INCIDENT TIMELINE

✓ Resolved
This incident has been resolved.
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.
monitoring
We have removed the temporary block and are continuing to monitor.
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.
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.
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.
investigating
We are working to investigate a partial outage in the PyPI backends.

📊 TECHNICAL DETAILS

Internal ID
ee6d8599-f5fa-43b2-89a0-38c68b138fe2
External ID
wtqw8mxcg3j1
🕐 Started
🔄 Last Updated
✓ Resolved
MAJOR
Impact Level
2d 13h
Total Duration
6
Status Updates
Affected Components
pypi.org - Backends
REQUEST COVERAGE
No article has been written for this incident yet. When 100 people request coverage, we request generation of one.
0 / 100 requests100 more needed