Maintenance Quay.io status
quay.io · Official status page (Statuspage-compatible JSON)
FROM ALL SOURCES
Quay.io's status page shows “Maintenance” in API and Registry; the vendor is resolved. User reports haven't spiked, so wide impact isn't visible yet.
confidence: low Vendor: minor issue · users: normal · routing: no data.
- Vendor status page Maintenance · 2 open incidents
- User reports 0 in 15 min vs ~0 typical
- Routing / BGP no ASN mapped, so no routing view
- News & network weather no recent mentions
- Providers it may run on (inferred) no mapped dependencies
- CISA KEV (context) no recent entries for this vendor
Regions mentioned: API, Registry, Security Scanning
| Clock | Started | Running |
|---|---|---|
| Vendor clock when the vendor's open incident started | 68 days | |
| Crowd clock when user reports began rising above normal | not seen | n/a |
| Network clock when routing anomaly data first flagged it | not seen | n/a |
| ORBIT clock when our checker first recorded the change | 2 h 23 min |
Evidence
- Official page: Maintenance (“Service Under Maintenance”). evidence confidence: high
- Vendor stage: resolved on “Initial: Quay.io Push/Pull Degraded”. evidence confidence: high
- User reports are within normal range (0 in 15 min). evidence confidence: low
What we don't know: what is happening inside Quay.io's own systems, how many users are actually affected (reports are self-selected and unverified), and anything from routing / bgp, providers it may run on (inferred). Routing data shows reachability, not whether the app works.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Generated .
Cloudy_Day's take
Stage vs. health
The vendor's stage is “resolved”. Stage tells you where they are in their process; health is what users experience. Right now vendor: minor issue · users: normal · routing: no data. Vendor reports an issue we don't see in crowd or routing data (it may be partial or internal).
Who depends on whom
We don't map other services that depend on Quay.io. Dependency chains are where single points of failure hide.
Identity & trust lens
Even without an identity system involved, outages push people toward workarounds: password resets, unofficial apps and “status” links in DMs. Each one is a trust decision. Use official channels.
For users
Check the official status page before changing settings or reinstalling. If you must act, use known-good bookmarks. Reporting what's broken on ORBIT helps everyone see the real footprint.
For security teams
Treat this as an availability event unless an official source says otherwise. Check which of your systems sit on Quay.io, watch for outage-themed phishing aimed at your users, and log what you see with timestamps (all four clocks).
What to watch next
The vendor stage moving to “monitoring”, then “resolved”; the user-report curve falling back under baseline; and whether dependents start reporting issues.
Automated analysis by Cloudy_Day NetWeather; not a personal statement. Independent researcher; not affiliated with Quay.io. No blame or attack claims without an official source. Generated .
INCIDENT REPLAY
Initial: Quay.io Push/Pull Degraded
major resolved · started · resolved
12 updates
- investigating
We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.
- 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
- 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
- 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
- identified
Quay is in read-only mode. Only pulls are being served while we implement the fix.
- 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.
- 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.
- identified
The affected database tables have been updated. We are working to restoring full read/write traffic. Quay.io remains in read-only mode.
- monitoring
The fix has been deployed. Quay.io is serving read/write requests. We are continuing to monitor the service
- monitoring
Image push and pull operations are functioning normally. We continue to monitor service health. Clair vulnerability scanning is temporarily disabled.
- monitoring
Registry is operational, security scanning is under maintenance.
- 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.
Community comments (0)
Comments are opinions of visitors, not statements by Cloudy_Day. Every comment is held for review before it appears. Links are removed, and personal data is redacted. Community guidelines.
No approved comments yet.
How to read this: official status comes from each provider's own public status page. User reports are unverified visitor reports. Things that happen at the same time are coincidence, not causation. Cloudy_Day is independent and not an official status source for any company listed.