Python Infrastructure Outage

What to do

• Check whether you use PyPI python.org - CDN, python.org - Backends, python.org - Downloads Backends, bugs.python.org and 1 more in us. Check your stack

  Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.

• Confirm your retries, queues and scheduled jobs caught up after the 2h 47m it lasted.

  Anything that failed between 2026-02-26 20:40 UTC and 2026-02-26 23:26 UTC may need a replay.

• Subscribe to PyPI's feed to hear about the next one first. RSS feed

  https://down.guide/feed?provider=pypi works in Slack (/feed subscribe), Discord feed bots and any RSS reader.

Updates from PyPI 4

1. investigatingFeb 26, 2026, 8:04 PM UTC

   We are currently investigating this issue

   provider

2. investigatingFeb 26, 2026, 8:40 PM UTC

   The root cause has been identified as an erroneous scaling operation that affected some application workloads. All services have been restored and are coming back online. We are monitoring to confirm full recovery.

   provider

3. resolvedFeb 26, 2026, 11:26 PM UTC

   The incident has been resolved.

   provider

4. postmortemFeb 26, 2026, 11:26 PM UTC

   The incident has been resolved. ## Incident Report: Cluster-wide service outage **Duration**: ~36 minutes \(20:04–20:40 UTC\) **Impact**: Some PSF-hosted services were unavailable, including [python.org](http://python.org), [us.pycon.org](http://us.pycon.org), PyPI stats, [bugs.python.org](http://bugs.python.org), and related services. What was unaffected was our other cluster that manages [PyPI.org](http://PyPI.org) among other services related to PyPI. **Root Cause**: During local development of kubernetes workloads locally there was an incorrect context switch to one of our production clusters. The scale-down commands ran against the production cluster instead of the local environment, iterating through all deployments and setting them to zero replicas. which created cascading failures. **Recovery**: Services were restored with the help of Ee Durbin by bringing up infrastructure in dependency order, original replica counts were recovered from Kubernetes event history. Action items: * Separate kubeconfig files for production vs local, rather than relying on context switching * Research adding admission control or policies to prevent bulk scale-to-zero operations * Document the infrastructure dependency chain and recovery runbook for future incidents Jacob Coffee, PSF Infrastructure Team

   provider

Corrections

None so far.

Something wrong on this page? Report an error or send us a note. Every fix is listed here.