rewindex

CompaniesRed Hat (incl. Quay.io)Incidents

Red Hat (incl. Quay.io): registry.connect.redhat.com and registry.access.redhat.com 503 Certificate Error

No impact listedStatus: resolvedStarted Resolved (0 min)1 updatestatus.redhat.com (opens in new tab)

Timeline of updates

  1. resolved

    Pulls for registry.connect.redhat.com and registry.access.redhat.com generated 503s due to expired certificate. The certificates have been rotated and pulls have been restored.

From Red Hat (incl. Quay.io)’s published incident history: for incidents before Rewindex began polling this status page, only the final update text is available.

Archive proof

Rewindex commits each version of an incident it captures to a daily checkpoint, chains it to the day before, and has the checkpoint timestamped by FreeTSA and DigiCert.

How the archive is checked, and what it cannot prove.

This incident predates live tracking (October 17, 2026). It came from the vendor’s own published history, which is not covered by checkpoints.

Impact, status and times are the vendor’s own, as last archived. View on status.redhat.com (opens in new tab).

Cite this

Status incident (vendor impact label: none) posted by Red Hat (incl. Quay.io), started 2025-02-01 04:00 UTC, resolved after 0 min, 1 update(s).

Title
registry.connect.redhat.com and registry.access.redhat.com 503 Certificate Error
Vendor
Red Hat (incl. Quay.io)
Date
URL
https://rewindex.com/company/red-hat/incidents/gkg8961t0gv2

Red Hat (incl. Quay.io) profileRecent Red Hat (incl. Quay.io) incidentsAll outages on February 1, 2025Red Hat (incl. Quay.io) in February 2025MarkdownJSON