Isitreallydown?
// Incident Post-MortemDRN-2FC38729

PyPI outage on May 27, 2025

Major severityResolved45 minPackage Registry
Started · UTC
May 27, 12:53 PM
350d ago
Resolved · UTC
May 27, 01:38 PM
350d ago
Duration
45 min
End-to-end
Peak confidence
80.00
0 snapshots
// What happened

May 27, 12:53 UTCResolved - We have not seen a return of the traffic that caused this incident after removing the temporary block. We will open a new incident if we need to take action again.May 25, 12:16 UTCUpdate - We have removed the temporary block and are continuing to monitor.May 24, 23:54 UTCMonitoring - Our block is in place and systems are stable, but we are not satisfied with having to block such a generic user-agent. If you are aware of a system that began a mass crawl of PyPI's JSON release endpoints starting at around 22:05 UTC 2025-05-25, please contact admin@pypi.org.May 24

Deterministic readout · awaiting AI summary pass

// Timeline
  1. Incident detected

    Major confidence crossed the incident threshold for PyPI Partial 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 Tue, May 27, 2025, 01:38 PM 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.