Update
The XMLRPC Search endpoint is still disabled due to
ongoing request volume. As of this update, there has been no reduction
in inbound traffic to the endpoint from abusive IPs and we are unable to
re-enable the endpoint, as it would immediately cause PyPI service to
degrade again. We are working with the abuse contact at the owner of the
IPs and trying to make contact with the maintainers of whatever tool is
flooding us via other channels.
Monitoring
With the temporary disabling of XMLRPC we are hoping that
the mass consumer that is causing us trouble will make contact. Due to
the huge swath of IPs we were unable to make a more targeted block
without risking more severe disruption, and were not able to receive a
response from their abuse contact or direct outreach in an actionable
time frame.
Update
Due to the overwhelming surges of inbound XMLRPC search
requests (and growing) we will be temporarily disabling the XMLRPC
search endpoint until further notice.
Identified
We've identified that the issue is with excess volume to
our XLMRPC search endpoint that powers `pip search` among other tools.
We are working to try to identify patterns and prohibit abusive clients
to retain service health.
Investigating
PyPI's search backends are experiencing an outage causing
the backends to timeout and fail, leading to degradation of service for
the web app. Uploads and installs are currently unaffected but logged in
actions and search via the web app and API access via XMLRPC are
currently experiencing partial outages.
Comments
Post a Comment
https://gengwg.blogspot.com/