<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Quay incidents — Vendor Status Watch</title><link>https://approjects-vendor-status-watch.static.hf.space/v/quay.html</link><description>Incidents from Quay's public status page, polled daily.</description><lastBuildDate>Wed, 16 Sep 2026 12:28:20 +0000</lastBuildDate><item><title>Quay.io Security Scanning on maintenance [maintenance]</title><link>https://stspg.io/dqcy6fsvh87s</link><guid isPermaLink="false">quay:2026-09-15T04:20:00.000Z</guid><pubDate>Tue, 15 Sep 2026 04:20:00 +0000</pubDate><description>Quay.io Security Scanning has been put on maintenance following a quay.io push/pull incident from Sep 14, 2026.</description></item><item><title>catalog.redhat.com - Partial Outage [resolved]</title><link>https://stspg.io/vs3tqyjygcfm</link><guid isPermaLink="false">quay:2026-09-14T22:10:00.159Z</guid><pubDate>Mon, 14 Sep 2026 22:10:00 +0000</pubDate><description>This issue has been resolved, and a fix has been successfully deployed.</description></item><item><title>Initial: Quay.io Push/Pull Degraded [resolved]</title><link>https://stspg.io/gbz3yybkwswc</link><guid isPermaLink="false">quay:2026-09-14T13:34:09.400Z</guid><pubDate>Mon, 14 Sep 2026 13:34:09 +0000</pubDate><description>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.</description></item><item><title>OpenShift Cluster Manager Database Maintenance 2026-09-12 [maintenance]</title><link>https://stspg.io/7pqvl5xh2056</link><guid isPermaLink="false">quay:2026-09-12T12:00:00.000Z</guid><pubDate>Sat, 12 Sep 2026 12:00:00 +0000</pubDate><description>Scheduled maintenance is currently in progress. We will provide updates as necessary.</description></item><item><title>Ask Red Hat - Outage [resolved]</title><link>https://stspg.io/1vnkklf314f3</link><guid isPermaLink="false">quay:2026-08-31T17:31:08.328Z</guid><pubDate>Mon, 31 Aug 2026 17:31:08 +0000</pubDate><description>Resolved outage due to connection issue after database patching.</description></item><item><title>Search Degradation [resolved]</title><link>https://stspg.io/7zt6fv2gqxn5</link><guid isPermaLink="false">quay:2026-08-18T22:33:08.505Z</guid><pubDate>Tue, 18 Aug 2026 22:33:08 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Search Degradation [resolved]</title><link>https://stspg.io/pms2869bypyz</link><guid isPermaLink="false">quay:2026-08-18T15:45:46.202Z</guid><pubDate>Tue, 18 Aug 2026 15:45:46 +0000</pubDate><description>All search functionality has been restored.</description></item><item><title>sso.redhat.com Offline Token Issue [resolved]</title><link>https://stspg.io/zf6rk0mc5r6w</link><guid isPermaLink="false">quay:2026-08-12T13:12:54.221Z</guid><pubDate>Wed, 12 Aug 2026 13:12:54 +0000</pubDate><description>The incident has been mitigated . Our the team will continue working on the root cause analysis (RCA).</description></item><item><title>Red Hat 3scale API Management SaaS APIs are currently experiencing a service disruption [resolved]</title><link>https://stspg.io/166ms87b8g7y</link><guid isPermaLink="false">quay:2026-07-28T12:47:58.666Z</guid><pubDate>Tue, 28 Jul 2026 12:47:58 +0000</pubDate><description>Scheduled database maintenance from 12:47:40 UTC to 12:50:59 UTC.</description></item><item><title>Red Hat 3scale API Management SaaS APIs are currently experiencing a service disruption [resolved]</title><link>https://stspg.io/bqfqfyb8lqp4</link><guid isPermaLink="false">quay:2026-07-28T12:47:56.847Z</guid><pubDate>Tue, 28 Jul 2026 12:47:56 +0000</pubDate><description>Scheduled database maintenance from 12:47:40 UTC to 12:50:59 UTC.</description></item><item><title>Search Outage - Developers.redhat.com and www.redhat.com [resolved]</title><link>https://stspg.io/45rs9tc9s3np</link><guid isPermaLink="false">quay:2026-07-22T03:55:57.852Z</guid><pubDate>Wed, 22 Jul 2026 03:55:57 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Multiple Site Partial Outage [resolved]</title><link>https://stspg.io/vwy10833rlht</link><guid isPermaLink="false">quay:2026-07-18T00:17:11.984Z</guid><pubDate>Sat, 18 Jul 2026 00:17:11 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Intermittent HTTP 504 for registry.redhat.io and registry.connect.redhat.com [resolved]</title><link>https://stspg.io/6l1vz4w9dyry</link><guid isPermaLink="false">quay:2026-07-17T17:47:10.796Z</guid><pubDate>Fri, 17 Jul 2026 17:47:10 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Ask Red Hat - Outage [resolved]</title><link>https://stspg.io/f4krt0s7xp80</link><guid isPermaLink="false">quay:2026-07-17T13:29:52.179Z</guid><pubDate>Fri, 17 Jul 2026 13:29:52 +0000</pubDate><description>The incident is now resolved.</description></item><item><title>Multiple Site Outage [resolved]</title><link>https://stspg.io/8k03tpqbkw54</link><guid isPermaLink="false">quay:2026-07-17T12:44:32.519Z</guid><pubDate>Fri, 17 Jul 2026 12:44:32 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Docs.redhat.com - Outage Identified [resolved]</title><link>https://stspg.io/9qt8bzqfr76v</link><guid isPermaLink="false">quay:2026-07-16T19:26:16.657Z</guid><pubDate>Thu, 16 Jul 2026 19:26:16 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Ecosystem Catalog Partial Outage [resolved]</title><link>https://stspg.io/mmhscccrqk45</link><guid isPermaLink="false">quay:2026-07-10T23:22:07.642Z</guid><pubDate>Fri, 10 Jul 2026 23:22:07 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Ecosystem Catalog Partial Outage [resolved]</title><link>https://stspg.io/znvtr1l05n7p</link><guid isPermaLink="false">quay:2026-07-10T14:18:32.567Z</guid><pubDate>Fri, 10 Jul 2026 14:18:32 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Partner Portal Outage [resolved]</title><link>https://stspg.io/b8cw17n6h70j</link><guid isPermaLink="false">quay:2026-07-09T22:18:13.743Z</guid><pubDate>Thu, 09 Jul 2026 22:18:13 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>api.openshift.com is down [resolved]</title><link>https://stspg.io/chyzbblvyczy</link><guid isPermaLink="false">quay:2026-07-07T15:18:47.303Z</guid><pubDate>Tue, 07 Jul 2026 15:18:47 +0000</pubDate><description>api.openshift.com issue is resolved and is now available.</description></item><item><title>Notification Service Disruption [resolved]</title><link>https://stspg.io/tpsgg97nf5dn</link><guid isPermaLink="false">quay:2026-07-06T17:07:49.117Z</guid><pubDate>Mon, 06 Jul 2026 17:07:49 +0000</pubDate><description>This issue has been resolved. Notifications are now being sent correctly.</description></item><item><title>Support Cases Access.redhat.com Outage [resolved]</title><link>https://stspg.io/45tsk05g9r0r</link><guid isPermaLink="false">quay:2026-06-12T08:56:44.102Z</guid><pubDate>Fri, 12 Jun 2026 08:56:44 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>catalog.redhat.com - Outage [resolved]</title><link>https://stspg.io/cghflw1mxjg7</link><guid isPermaLink="false">quay:2026-06-09T14:32:11.980Z</guid><pubDate>Tue, 09 Jun 2026 14:32:11 +0000</pubDate><description>Service is fully restored. The root cause was identified as an intermittent issue with a backend API serving hardware information.</description></item><item><title>connect.redhat.com - Outage [resolved]</title><link>https://stspg.io/ptdsw1406tys</link><guid isPermaLink="false">quay:2026-06-08T13:32:59.830Z</guid><pubDate>Mon, 08 Jun 2026 13:32:59 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>repository.jboss.org - Outage [resolved]</title><link>https://stspg.io/nxkv277gb02m</link><guid isPermaLink="false">quay:2026-06-03T00:28:20.058Z</guid><pubDate>Wed, 03 Jun 2026 00:28:20 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Quay.io Push/Pull Degraded [resolved]</title><link>https://stspg.io/49zmtnd0z57f</link><guid isPermaLink="false">quay:2026-06-01T08:34:18.249Z</guid><pubDate>Mon, 01 Jun 2026 08:34:18 +0000</pubDate><description>The service has been restored and is operating normally.</description></item><item><title>Quay.io Intermittent HTTP 502 on Pull/Push [postmortem]</title><link>https://stspg.io/rpk5vr4kd3j0</link><guid isPermaLink="false">quay:2026-05-09T19:30:00.000Z</guid><pubDate>Sat, 09 May 2026 19:30:00 +0000</pubDate><description>On May 9, a surge of concurrent automated image pushes caused database lock contention that degraded Quay.io for approximately 18 minutes. Both image pushes and pulls returned errors during this window. The team identified and disabled an internal feature that amplified the contention, restoring service. We are redesigning this feature to operate asynchronously and improving our database locking mechanisms to better handle high-concurrency traffic.</description></item><item><title>Quay.io HTTP 502 on Pull/Push [postmortem]</title><link>https://stspg.io/wzmcf9349ldh</link><guid isPermaLink="false">quay:2026-05-07T18:05:44.230Z</guid><pubDate>Thu, 07 May 2026 18:05:44 +0000</pubDate><description>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.</description></item><item><title>cert-api.access.redhat.com outage [resolved]</title><link>https://stspg.io/klkf3rhvc3bx</link><guid isPermaLink="false">quay:2026-05-05T12:28:06.778Z</guid><pubDate>Tue, 05 May 2026 12:28:06 +0000</pubDate><description>This incident has been resolved.</description></item><item><title>Quay.io Push/Pull Degraded [postmortem]</title><link>https://stspg.io/3hmzxvcjvndl</link><guid isPermaLink="false">quay:2026-04-21T22:50:02.868Z</guid><pubDate>Tue, 21 Apr 2026 22:50:02 +0000</pubDate><description>On April 21, a routine production deployment included a dependency upgrade that exposed a latent incompatibility, causing Quay.io application pods to crash on startup. Image pulls and pushes were fully unavailable for approximately 12 minutes before the team failed over to a secondary region, restoring pulls. Pushes remained unavailable for approximately 70 additional minutes while the deployment was reverted and traffic was incrementally shifted back to the primary region. We are enabling staging parity for all runtime features, improving automated rollback mechanisms, and isolating observability subsystems from the critical request path to prevent recurrence.</description></item></channel></rss>