← Back to the carnage
PYPI

{ "skip": true } ``` This is scheduled maintenance, which per the instructions should be skipped. (Auto-resolved: no updates in 24h)

⏰ Sep 25, 2026 Fixed (for now) spotted via status_rss

// The official story

Deprecated XML-RPC `browse()` method no longer works

// Status page says

Sep 25 , 15:35 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Sep 25 , 15:34 UTC Scheduled - The deprecated XML-RPC `browse()` method has been removed and turned into an error response. After being abused for multiple days and triggering long outages for all users, this deprecated method has been rem

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

https://status.python.org/incidents/y3pt84s54b50

Pypi's Greatest Hits

🟒 PYPI Oct 01, 2026
πŸ”΄ 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)
🟒 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)