Vendor Status Watch

← all vendors

Quay status history

Current state: operational — “All Systems Operational” per https://status.quay.io (Atlassian Statuspage), checked 2026-09-16 12:28 UTC.

7incidents, last 30 days
21incidents, last 90 days
55incidents on record
Incidents per week, last 12 weeks:

How long do Quay incidents last?

3.1 hmedian incident duration51 measured
19.7 h90th percentile1 in 10 ran longer
3.0 hmedian, major/critical only40 incidents

From 51 incidents with a vendor-posted start and resolve time. Longest on record: Subscription threshold exceeded notifications for non-Pay as you go products are showing misleading values — 13.0 days (2026-04-03 14:04 UTC). Excluded, never estimated: 2 scheduled maintenance, 1 still open / no resolve time, 1 resolution inferred by us. Duration is the gap between the vendor's own posted timestamps — it is not measured downtime, uptime or an SLA figure, and a vendor that posts every blip will look worse here than one that posts nothing. Same rule as the outage-duration dataset.

Incidents on record (55)

StartedIncidentStatusImpactDuration
2026-09-15 04:20 UTCQuay.io Security Scanning on maintenancemaintenanceminor32 h 08 min (approx.)
2026-09-14 22:10 UTCcatalog.redhat.com - Partial Outageresolvedmajor10 h 39 min
2026-09-14 13:34 UTCInitial: Quay.io Push/Pull Degradedresolvedmajor19 h 41 min
2026-09-12 12:00 UTCOpenShift Cluster Manager Database Maintenance 2026-09-12maintenancemajor24 h 30 min (approx.)
2026-08-31 17:31 UTCAsk Red Hat - Outageresolvedmajor15 min
2026-08-18 22:33 UTCSearch Degradationresolvedmajor4 h 40 min
2026-08-18 15:45 UTCSearch Degradationresolvedmajor2 h 46 min
2026-08-12 13:12 UTCsso.redhat.com Offline Token Issueresolvedmajor2 h 58 min
2026-07-28 12:47 UTCRed Hat 3scale API Management SaaS APIs are currently experiencing a service disruptionresolvedminor19 h 32 min
2026-07-28 12:47 UTCRed Hat 3scale API Management SaaS APIs are currently experiencing a service disruptionresolvedminor19 h 33 min
2026-07-22 03:55 UTCSearch Outage - Developers.redhat.com and www.redhat.comresolvedcritical45 min
2026-07-18 00:17 UTCMultiple Site Partial Outageresolvedmajor2 h 51 min
2026-07-17 17:47 UTCIntermittent HTTP 504 for registry.redhat.io and registry.connect.redhat.comresolvedminor3 d 6 h
2026-07-17 13:29 UTCAsk Red Hat - Outageresolvedcritical26 min
2026-07-17 12:44 UTCMultiple Site Outageresolvedmajor37 min
2026-07-16 19:26 UTCDocs.redhat.com - Outage Identifiedresolvedmajor3 h 21 min
2026-07-10 23:22 UTCEcosystem Catalog Partial Outageresolvedminor15 h 26 min
2026-07-10 14:18 UTCEcosystem Catalog Partial Outageresolvedminor3 h 15 min
2026-07-09 22:18 UTCPartner Portal Outageresolvedmajor4 h 07 min
2026-07-07 15:18 UTCapi.openshift.com is downresolvedcritical28 min
2026-07-06 17:07 UTCNotification Service Disruptionresolvedmajor24 min
2026-06-12 08:56 UTCSupport Cases Access.redhat.com Outageresolvedcritical0 min
2026-06-09 14:32 UTCcatalog.redhat.com - Outageresolvedminor28 min
2026-06-08 13:32 UTCconnect.redhat.com - Outageresolvedcritical3 h 04 min
2026-06-03 00:28 UTCrepository.jboss.org - Outageresolvedcritical14 h 33 min
2026-06-01 08:34 UTCQuay.io Push/Pull Degradedresolvedmajor17 h 42 min
2026-05-09 19:30 UTCQuay.io Intermittent HTTP 502 on Pull/Pushpostmortemmajor0 min
2026-05-07 18:05 UTCQuay.io HTTP 502 on Pull/Pushpostmortemcritical3 h 04 min
2026-05-05 12:28 UTCcert-api.access.redhat.com outageresolvedmajor3 h 05 min
2026-04-21 22:50 UTCQuay.io Push/Pull Degradedpostmortemmajor1 h 19 min
2026-04-09 17:10 UTCErraneous Advisory email notificationsresolvedmajor0 min
2026-04-03 14:04 UTCSubscription threshold exceeded notifications for non-Pay as you go products are showing misleading valuesresolvednone13 d 0 h
2026-03-30 20:11 UTCquay.io API failurespostmortemmajor3 h 04 min
2026-03-12 20:16 UTCaccess.redhat.com - SSO Timeoutsresolvedminor22 min
2026-03-10 17:03 UTCIntermittent issues with RHEL 9 and RHUI downloadsresolvedmajor7 d 21 h
2026-03-06 19:25 UTCIntermittent issues with RHEL 9 and RHUI downloadsresolvedmajor2 d 19 h
2026-03-02 07:22 UTCAWS Outage: me-southidentifiednone193 d 5 h (approx.)
2026-03-01 14:02 UTCAWS Outage: me-centralidentifiednoneopen
2026-02-18 20:51 UTCquay.io intermittent API failurespostmortemminor49 min
2026-02-10 10:29 UTCHybrid Cloud Console Notifications partial outageresolvedmajor6 h 00 min
2026-02-09 21:43 UTCQuay.io UI Could Not Be Loadedpostmortemcritical41 min
2026-02-05 03:41 UTCROSA [Classic & HCP] Y-Stream Upgrades Blockedresolvedmajor8 h 27 min
2026-02-04 00:13 UTCCustomer Portal Downloads Timeoutsresolvedcritical13 h 13 min
2026-01-30 07:12 UTCDNS issues with registriesresolvedmajor40 min
2026-01-29 18:59 UTCquay.io & registry.redhat logins failing with RHSSOpostmortemmajor52 min
2026-01-28 12:23 UTCEntitlement Network Outageresolvedcritical3 h 01 min
2026-01-22 21:07 UTCCatalog outageresolvedmajor54 min
2026-01-20 22:13 UTCEcosystem Catalog Detail Pagesresolvednone15 h 58 min
2026-01-14 14:30 UTCRed Hat Content Delivery Network (CDN) & Entitlement Network Modernization has begunresolvedmajor6 h 37 min
2026-01-05 18:45 UTCIntermittent Pull & Push Failureresolvedmajor3 h 15 min
2025-12-11 07:10 UTCaccess.redhat.com : Partial User Outageresolvedminor7 h 24 min
2025-12-10 21:00 UTCAccess.redhat.com - Partial Outageresolvedcritical19 min
2025-12-08 04:02 UTCHomepage - Access.redhat.com Outageresolvedcritical1 h 05 min
2025-12-05 06:51 UTCaccess.redhat.com - Homepage Outageresolvedmajor44 min
2025-11-27 10:00 UTCDocs.redhat.com - Partial Outageresolvedmajor21 h 12 min

Titles, statuses and impact levels are the vendor's own words. Durations marked approx. are inferred from the poll that first found the incident gone. Shows the latest 60; the JSON has everything we hold (up to 400 days).

Watch Quay with the template

Put this in config.json of your fork and add a WEBHOOK_URL secret:

{
  "vendors": [
    "quay"
  ],
  "format": "auto",
  "map_url": "https://raw.githubusercontent.com/APVentureEngine/vendor-status-watch/main/vendors.json",
  "unreachable_after": 3,
  "mute_maintenance": false
}