CompaniesPyPI (Python Infrastructure)Incidents
PyPI (Python Infrastructure): python.org unavailable
Timeline of updates
- resolved
This incident has been resolved. We removed two deprecated service backends recently but failed to update the configuration of the inbound HTTP load balancing infrastructure. As a result, when the services finally aged out of internal service discovery the templates that are rendered to configure the HTTP load balancer were not valid. This caused the load balancers to fail and our backends became unavailable. Additionally caching caused our monitoring to fail to detect this outage until about 20 minutes into the incident. We are working to resolve the template rendering issue and improve the time to alert for outages of python.org.
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