Isitreallydown?
// Incident Post-MortemDRN-077A42EF

PyPI outage on February 26, 2026

Major severityResolved45 minPackage Registry
Started · UTC
Feb 26, 11:26 PM
75d ago
Resolved · UTC
Feb 27, 12:11 AM
75d ago
Duration
45 min
End-to-end
Peak confidence
80.00
0 snapshots
// What happened

Feb 26, 23:26 UTCResolved - The incident has been resolved.Feb 26, 20:40 UTCUpdate - 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.Feb 26, 20:04 UTCInvestigating - We are currently investigating this issue

Deterministic readout · awaiting AI summary pass

// Timeline
  1. Incident detected

    Major confidence crossed the incident threshold for Python Infrastructure Outage.

  2. Marked resolved

    The incident was closed after 45 min of observed impact.

// Signals by source0 sources

No per-source signal payloads were preserved in this incident's snapshot window.

// Aggregate evidence

Confidence scoring

80.00

The incident reached 80.00 peak confidence across available stored status snapshots.

User reports

0 / 15m

No elevated user-report volume was preserved in the incident window snapshots.

Status samples

0 affected

The incident row exists, but the bounded snapshot window does not include affected status samples.

Recovery signal

Resolved

Recovery was recorded at Fri, Feb 27, 2026, 12:11 AM UTC.

// User impact

PyPI users likely saw failed connections, degraded availability, or session instability for this Package Registry service. The incident reached Major severity and lasted 45 min. The stored report window does not show a preserved user-report spike.