← Back to the carnage
PYPI

πŸ”΄ Multiple python.org services went dark after deprecated API usage tanked their internal certificates. The classic 'we updated the library and broke everything' play. Now frantically renewing certs and praying things resurrect. (Auto-resolved: no updates in 24h)

⏰ Oct 01, 2026 Fixed (for now) spotted via status_rss

// The official story

Multiple services unavailable

// Status page says

Oct 1 , 11:13 UTC Monitoring - Multiple python.org services were impacted by expiration of internal TLS certificates caused by use of APIs deprecated by a recent library update. We have resolved the issue and are monitoring as services come back online after renewing their internal certificates.

πŸ”— Official status page (for the PR-approved version)

https://status.python.org/incidents/0jzvfb9tnqmv

Pypi's Greatest Hits

🟒 PYPI Sep 25, 2026
{ "skip": true } ``` This is scheduled maintenance, which per the instructions should be skipped. (Auto-resolved: no updates in 24h)
🟒 PYPI Feb 26, 2026
🟑 PyPI infrastructure decided to audition for a disappearing act at 20:04 UTC. Engineers are investigating, which is corporate-speak for 'we're refreshing the status page every 30 seconds while stress-eating.'. (Auto-resolved: no updates in 24h)
🟒 PYPI Jan 19, 2026
βšͺ PyPI's API decided to move at geological timescales for a few hours. Engineers implemented a fix faster than their own package manager could install dependencies, and everything's back to normal speedβ€”or at least what passes for normal in the Python ecosystem. (Auto-resolved: no updates in 24h)