Observed incident recordDetected by RELIASTRA probes

Official status page failure window - PyPI

Incident 2debc294-9ce8-454f-9a3a-a9efcd728066 - endpoint status.python.org, measured from us-east. Confirming rule: 2 consecutive failed observations counted 2 of them.

ResolvedSeverity: MajorStatus: ResolvedAttribution: OBSERVED by RELIASTRA

Observed window

Every timestamp is a stored field of this record, printed in UTC. The window begins at the first failure the rule counted and ends, for a resolved record, at the observation run whose consecutive successes closed it.

Opened: 03 Oct 2026 19:07:10 UTC
Confirmed: 03 Oct 2026 19:12:30 UTC - the run that made the failure count reach the threshold; this record did not exist before it
Recovered: 03 Oct 2026 19:17:59 UTC
Duration: 10m (from the stored window)

What was measured

The record is a summary of an observation run set. The referenced observation ids resolve to stored probe entries inside the retention window; the detector keeps no second, narrative version of them.

Endpoint observed: Official status page - https://status.python.org
Measured from: us-east - the only observation region named in this record; nothing about other regions is claimed or inferred
Failed observations: 2, consecutive through the trigger set
Failure shape: mixed failure modes - status codes recorded: 503
Observation references: first 06fa2b65-cde4-4dc3-8057-ec7662a49db4 last 3e1ed3f0-ec42-4aaf-9f88-e100db275ce1

The claim, in full

Between 2026-10-03T19:07:10.190175+00:00 and 2026-10-03T19:12:30.361466+00:00, RELIASTRA probes in us-east recorded 2 consecutive failed observations against https://status.python.org (the observed PyPI target). Failure class: mixed; observed status: 503. This record describes the observed endpoint only and is not a statement about the vendor's services as a whole. That is all of it. Nothing about the vendor as a whole, nothing about other regions, nothing about your requests - the record you are reading is the measurement, not a narration of it.

Evidence artifact

A frozen, hashed document of this record's window: the claim, the detection rule, and every observation row it rests on. Deterministic, reproducible from stored data, immutable once written.

Artifact: /api/v1/public/incidents/2debc294-9ce8-454f-9a3a-a9efcd728066/evidence - JSON, served byte-for-byte as stored
Content hash: sha256: eca08e1d91730e72afc5b341723fef864a1344b95264ae58d44794292754ba13
Freeze: version 2, taken while the incident was resolved (03 Oct 2026 19:23:13 UTC); later freezes supersede, never edit, and each stays at its own versioned URL
Coverage: 6 observations in the window
Verification: Remove the "verification" key from the document, re-serialise with sorted keys and compact separators, and SHA-256 the UTF-8 bytes: the digest must equal the hash above. The recipe ships inside every artifact.

What this record does not establish

The boundaries are part of the record, not a disclaimer under it.

Causation: Not established. A 5xx can be the vendor, a shared middle path, or the probe's own egress - the record reports what came back, not why.
Vendor acknowledgement: PyPI may have recorded this window differently, later, or not at all. RELIASTRA does not ingest vendor-reported status, so no reconciliation is offered either way.
Global reach: This window is named for us-east. A record from one observation region never settles the question in another.
Customer impact: Whether your requests were affected is your measurement to make - this record carries only RELIASTRA's own probes.

Where this fits

PyPI - current recordLive observatory
All observed incidents - pypiIncident search
Cross-vendor observed incident searchIncident search
How RELIASTRA measures vendor reliabilityMethodology