- Level
- confirmed
- Worst impact
- Partial outage
- Components
- API, Registry, Security Scanning
- Down Index
- 45of 100
What to do
Check whether you use Red Hat Quay.io API, Registry, Security Scanning. Check your stack
Paste a package.json, lockfile, Terraform or a list of domains at down.guide/stack to see every provider you depend on.Confirm your retries, queues and scheduled jobs caught up after the 19h 41m it lasted.
Anything that failed between 2026-09-14 13:34 UTC and 2026-09-15 09:15 UTC may need a replay.Subscribe to Red Hat Quay.io's feed to hear about the next one first. RSS feed
https://down.guide/feed?provider=quay works in Slack (/feed subscribe), Discord feed bots and any RSS reader.
Updates from Red Hat Quay.io 12
- investigating
We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
provider
- investigating
We have identified the cause of the image pull failures and are implementing a fix. Image pushes may continue to fail while remediation is in progress
provider
- identified
We have identified the cause of the image pull failures and are implementing a fix. Image pushes may continue to fail while remediation is in progress
provider
- identified
We have identified the cause of the image push failures and are implementing a fix. Image pushes may continue to fail while remediation is in progress
provider
- identified
Quay is in read-only mode. Only pulls are being served while we implement the fix.
provider
- identified
We are continuing to apply the fix. Quay.io remains in read-only mode. Image pulls continue to work, but pushes and other write operations are temporarily unavailable. We will provide another update once the fix is complete.
provider
- identified
We are continuing to apply the fix. 2 out of 3 affected tables have been updated. The final one is currently running. Quay.io remains in read-only mode. Image pulls continue to work, but pushes and other write operations are temporarily unavailable.
provider
- identified
The affected database tables have been updated. We are working to restoring full read/write traffic. Quay.io remains in read-only mode.
provider
- monitoring
The fix has been deployed. Quay.io is serving read/write requests. We are continuing to monitor the service
provider
- monitoring
Image push and pull operations are functioning normally. We continue to monitor service health. Clair vulnerability scanning is temporarily disabled.
provider
- monitoring
Registry is operational, security scanning is under maintenance.
provider
- resolved
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.
provider
Reports count in aggregate; nothing about you is shown.
Corrections
None so far.
Something wrong on this page? Report an error or send us a note. Every fix is listed here.
Questions about DWN-e00b6de344
Is Red Hat Quay.io still down?
No, this incident was resolved 2026-09-15 09:15 UTC. For Red Hat Quay.io's live state, see https://down.guide/quay.
How long did it last?
19h 41m, from 2026-09-14 13:34 UTC to 2026-09-15 09:15 UTC, by the times Red Hat Quay.io posted.
What was affected?
Red Hat Quay.io named API, Registry, Security Scanning.
What caused it?
Red Hat Quay.io hasn't published a root cause. If it does, it shows here.
Where does this come from?
Red Hat Quay.io's official status page, https://status.redhat.com, quoted verbatim. down.guide's own probes, reports and social counts are labeled as ours.