Red Hat 3scale incident

Initial: Quay.io Push/Pull Degraded

Resolved after 19 hours 41 minutes, affecting API and Registry and 1 more, on September 14, 2026.

resolved Sep 15, 2026, 09:15 AM UTC

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.

Started
Sep 14, 2026, 01:34 PM UTC
Resolved
Sep 15, 2026, 09:15 AM UTC
Duration
19h 41m
Detected by Pingoru
Sep 14, 2026, 01:34 PM UTC

Affected components

APIRegistrySecurity Scanning

Update timeline

  1. investigating Sep 14, 2026, 01:34 PM UTC

    We are experiencing degraded performance on quay.io push/pull API. We are actively investigating.

  2. investigating Sep 14, 2026, 02:02 PM UTC

    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

  3. identified Sep 14, 2026, 02:04 PM UTC

    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

  4. identified Sep 14, 2026, 02:08 PM UTC

    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

  5. identified Sep 14, 2026, 03:35 PM UTC

    Quay is in read-only mode. Only pulls are being served while we implement the fix.

  6. identified Sep 14, 2026, 07:33 PM UTC

    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.

  7. identified Sep 15, 2026, 12:39 AM UTC

    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.

  8. identified Sep 15, 2026, 02:49 AM UTC

    The affected database tables have been updated. We are working to restoring full read/write traffic. Quay.io remains in read-only mode.

  9. monitoring Sep 15, 2026, 04:05 AM UTC

    The fix has been deployed. Quay.io is serving read/write requests. We are continuing to monitor the service

  10. monitoring Sep 15, 2026, 04:31 AM UTC

    Image push and pull operations are functioning normally. We continue to monitor service health. Clair vulnerability scanning is temporarily disabled.

  11. monitoring Sep 15, 2026, 08:47 AM UTC

    Registry is operational, security scanning is under maintenance.

  12. resolved Sep 15, 2026, 09:15 AM UTC

    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.

Your product runs on more than Red Hat 3scale

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →