CompaniesRed Hat (incl. Quay.io)Incidents
Red Hat (incl. Quay.io): Pull Failures on registry.redhat.io
Timeline of updates
- resolved
On 2024-12-13 an issue was identified that impacted OpenShift clusters configured with proxy settings. During this time there were failures in pulling container images due to a "Forbidden" error. As a part of a backend transition, the image signature verification process was misconfigured to redirect to catalog.redhat.com. This domain is not currently documented as a requirement in the OpenShift firewall configuration guide and as a result proxy configurations that do not explicitly allow access to catalog.redhat.com blocked the request causing image pulls to fail. This configuration has been corrected and pulls to registry.redhat.io 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: critical) posted by Red Hat (incl. Quay.io), started 2024-12-13 19:30 UTC, resolved after 0 min, 1 update(s).
- Title
- Pull Failures on registry.redhat.io
- Vendor
- Red Hat (incl. Quay.io)
- Date
- URL
- https://rewindex.com/company/red-hat/incidents/hdtsvx5lgm7n
Red Hat (incl. Quay.io) profileRecent Red Hat (incl. Quay.io) incidentsAll outages on December 13, 2024Red Hat (incl. Quay.io) in December 2024MarkdownJSON