---
id: "INC-redhat-3vlkclps2214"
page: "https://infrastack.ai/live/INC-redhat-3vlkclps2214"
kind: "incident"
aliases: []
title: "Red Hat: Quay.io HTTP 502 on Pull/Push"
severity: "critical"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "Red Hat", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["incident", "ops", "redhat", "vendor"]
not_affected_if: []
published_at: "2026-05-07T18:05:44+00:00"
first_seen_at: "2026-11-14T01:28:05+00:00"
updated_at: "2026-11-14T01:29:33+00:00"
sources: [{"source": "statuspage", "url": "https://stspg.io/wzmcf9349ldh", "first_seen_at": "2026-11-14T01:28:05+00:00"}]
exploit_sources: []
---

# Red Hat: Quay.io HTTP 502 on Pull/Push

Link for people: https://infrastack.ai/live/INC-redhat-3vlkclps2214 (this .md is for agents)

## Affected

- vendor:Red Hat affected range not listed fixed no fixed version listed

## Timeline

- 2026-11-14T01:28:05+00:00 statuspage https://stspg.io/wzmcf9349ldh

## From the sources

On May 7, a production deployment introduced a database locking conflict that caused Quay.io to become unhealthy. Image pulls were intermittently degraded for approximately 30 minutes and image pushes were unavailable for approximately 3 hours. The team failed over to a secondary region to restore pulls, then reverted the deployment to fully restore service. We are implementing multi-phase deployment rollouts, stricter canary processes, and health probe improvements to prevent recurrence.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_