CompaniesPyPI (Python Infrastructure)Incidents
PyPI (Python Infrastructure): PyPI Search Errors
Timeline of updates
- resolved
Between 04:30 and 09:15 UTC, PyPI experienced elevated errors when performing search operations via the website and XMLRPC search function, affecting users of the website, as well as clients such as pip that call the XMLRPC search function. Logs indicate that the Elasticsearch cluster powering PyPI experienced an internal issue causing latency for requests to elevate. This latency was higher than PyPI is configured to tolerate. As a result, rather than allowing increased latency to overrun our backend capacity PyPI search endpoints returned an error. When the Elasticsearch cluster's health resolved, search functionality returned without intervention. This elevation in error rates was just under our threshold to page a PyPI administrator. We've opened a ticket with our Elasticsearch hosting vendor to determine if there's something that needs to be addressed and will double check our monitoring and alerting to determine if our thresholds for paging need to be updated.
From PyPI (Python Infrastructure)’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.
Archive proof
Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.
How the archive is checked, and what it cannot prove.
This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.
Impact, status and times are the vendor’s own, as last archived. View on status.python.org (opens in new tab).
PyPI (Python Infrastructure) profileRecent PyPI (Python Infrastructure) incidentsMarkdownJSON