---
id: "INC-redhat-0g8rsg3tbjpz"
page: "https://infrastack.ai/live/INC-redhat-0g8rsg3tbjpz"
kind: "incident"
aliases: []
title: "Red Hat: Initial: Quay.io Push/Pull Degraded"
severity: "high"
cvss: null
epss: null
exploited: false
status: "resolved"
category: "vendor"
products: [{"name": "Red Hat", "fixed": [], "affected": "", "ecosystem": "vendor"}]
ecosystems: ["vendor"]
tags: ["containers", "incident", "quay.io", "red-hat", "redhat", "security", "vendor"]
not_affected_if: ["no-quay-usage", "self-hosted-quay"]
published_at: "2026-09-14T13:34:09+00:00"
first_seen_at: "2026-11-14T01:28:03+00:00"
updated_at: "2026-11-14T01:29:36+00:00"
sources: [{"source": "statuspage", "url": "https://stspg.io/gbz3yybkwswc", "first_seen_at": "2026-11-14T01:28:03+00:00"}]
exploit_sources: []
---

# Red Hat: Initial: Quay.io Push/Pull Degraded

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

Quay.io, Red Hat's hosted container registry, had a degraded period in which some write operations failed and the registry went read-only to protect data. The sources say the cause was database scaling, and that it was resolved with no data loss; security scanning remained under maintenance afterward.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

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

## Timeline

- 2026-11-14T01:28:03+00:00 statuspage https://stspg.io/gbz3yybkwswc

## From the sources

Quay.io registry is operational since 15 Sep 2026, 5:00 AM UTC. Security scanning remains on maintenance until further notice.

During the incident, some write operations were failing. The registry was put into read-only mode to preserve data integrity. The underlying issue was related to database scaling and was resolved successfully without any data loss.

---

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