Is Quay down?

Last checked 3m ago
Current status
Quay is having a partial outage

2 active incidents: OpenShift Cluster Manager Database Maintenance 2026-09-19, AWS Outage: me-central

Official status page: https://status.quay.io · Polled every 5 minutes · 119 components tracked

Quay is reporting a partial outage right now (last checked 3m ago). Some components are affected; others remain operational.

Real-time Quay status, recent outages, and incident history — pulled directly from Quay's official status page at https://status.quay.io every 5 minutes. Pingoru tracks 119 Quay services and has captured 41 incidents in the last 90 days (99.04% uptime). Get email, Slack, Discord, or webhook alerts the moment Quay reports a new incident — free for 5 monitors, no credit card.

Users who monitor Quay also follow these Cloud Infrastructure services: Amazon Web Services DigitalOcean Cisco Umbrella Wasabi Vercel Hetzner HashiCorp Egnyte Dyn Genesys Cloud View all 6,000+ providers
Quay uptime 99.04% uptime · past 90 days
Mon Wed Fri
JunJulAugSep
Less More

Active incidents 2

  1. Ongoing ● 3d 15h
    Started Sep 12, 2026, 07:27 PM UTC
    Red Hat OpenShift Service on AWS (ROSA)
    Timeline · 2 updates
    • scheduled · Sep 12, 2026, 07:27 PM UTC

      Database service updates for backend services will be applied.

    • scheduled · Sep 12, 2026, 07:28 PM UTC

      The OpenShift Cluster Manager will undergo maintenance work to make infrastructure improvements. The maintenance will start on Saturday, September 12 at at 12:00 UTC and may last up to 2 hours and 30 minutes with the expected downtime of 1 minute. During the downtime, users may not be able to provision new clusters or manage the lifecycle of their existing clusters. User workloads running on existing clusters will remain unaffected and available during this maintenance window.

    Latest: The OpenShift Cluster Manager will undergo maintenance work to make infrastructure improvements. The maintenance will start on Saturday, September 12 at at 12:00 UTC and may last u…

  2. Ongoing ● 198d 20h
    Started Mar 01, 2026, 02:02 PM UTC
    OpenShift Cluster Manager
    Timeline · 6 updates
    • identified · Mar 01, 2026, 02:02 PM UTC

      ROSA clusters degraded in me-central AWS Status Page: https://health.aws.amazon.com/health/status

    • identified · Mar 01, 2026, 02:26 PM UTC

      An Availability Zone in the ME-CENTRAL-1 Region (mec1-az2) has been impacted by a power outage. Customers are advised to schedule their workloads into another availability zone.

    • identified · Mar 02, 2026, 01:37 PM UTC

      Availability Zones in the ME-CENTRAL-1 Region (mec1-az2, mec1-az3) have been impacted by a power outage. Customers are advised to schedule their workloads into another availability zone.

    • identified · Mar 02, 2026, 05:52 PM UTC

      ROSA clusters deployed in me-central-1 are degraded due to availability zone outages. We recommend customers enact their disaster recovery plans and recover from remote backups into alternate AWS Regions, ideally in Europe. Please refer to AWS Health for more information and recommendations on workload relocation.

    • identified · Mar 03, 2026, 10:21 AM UTC

      The outage is still ongoing on AWS side. The AWS Management Console is now operational, and AWS is recommending to retry operations where possible, although most of the underlying service are still offline.

    • identified · Mar 04, 2026, 04:55 AM UTC

      AWS continues to make progress on recovery efforts across multiple workstreams. From now on, updates will be delivered directly to affected customers through the AWS Personal Health Dashboard. Customers who require assistance with this event are encouraged to contact AWS Support through the AWS Management Console or the AWS Support Center. AWS Status Page: https://health.aws.amazon.com/health/status

    Latest: AWS continues to make progress on recovery efforts across multiple workstreams. From now on, updates will be delivered directly to affected customers through the AWS Personal Healt…

Recent outages & incidents

Past 90 days
  1. Resolved 13h 41m
    Started Sep 15, 2026, 08:55 AM UTC · Resolved Sep 15, 2026, 10:37 PM UTC
    Security Scanning
    Timeline · 1 update
    • in progress · Sep 15, 2026, 08:55 AM UTC

      Quay.io Security Scanning has been put on maintenance following a quay.io push/pull incident from Sep 14, 2026.

    Latest: Quay.io Security Scanning has been put on maintenance following a quay.io push/pull incident from Sep 14, 2026.

  2. Resolved 10h 39m
    Started Sep 14, 2026, 10:10 PM UTC · Resolved Sep 15, 2026, 08:49 AM UTC
    Catalog App
    Timeline · 3 updates
    • investigating · Sep 14, 2026, 10:10 PM UTC

      We are experiencing intermittent performance issues on catalog.redhat.com detail pages. Some users may see slow page loads, timeouts, or pages that fail to load. We are currently investigating the issue.

    • investigating · Sep 14, 2026, 10:10 PM UTC

      We are continuing to investigate this issue.

    • resolved · Sep 15, 2026, 08:49 AM UTC

      This issue has been resolved, and a fix has been successfully deployed.

    Latest: This issue has been resolved, and a fix has been successfully deployed.

  3. Resolved 20h 19m
    Started Sep 14, 2026, 02:50 PM UTC · Resolved Sep 15, 2026, 11:10 AM UTC
    Ask
    Timeline · 2 updates
    • scheduled · Sep 14, 2026, 02:50 PM UTC

      Ask Red Hat's underlying model hosting platform, Red Hat OpenShift AI, is being updated during which Ask Red Hat will be unavailable.

    • in progress · Sep 15, 2026, 09:28 AM UTC

      Scheduled maintenance is currently in progress. We will provide updates as necessary.

    Latest: Scheduled maintenance is currently in progress. We will provide updates as necessary.

  4. Resolved 19h 41m
    Started Sep 14, 2026, 01:34 PM UTC · Resolved Sep 15, 2026, 09:15 AM UTC
    APIRegistrySecurity Scanning
    Timeline · 12 updates
    • investigating · Sep 14, 2026, 01:34 PM UTC

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

    • 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

    • 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

    • 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

    • identified · Sep 14, 2026, 03:35 PM UTC

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

    • 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.

    • 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.

    • 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.

    • 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

    • 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.

    • monitoring · Sep 15, 2026, 08:47 AM UTC

      Registry is operational, security scanning is under maintenance.

    • 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.

    Latest: 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 faili…

  5. Resolved 2h 18m
    Started Sep 07, 2026, 11:13 AM UTC · Resolved Sep 07, 2026, 01:32 PM UTC
    Ask
    Timeline · 1 update
    • scheduled · Sep 07, 2026, 11:13 AM UTC

      Ask Red Hat - Safety Model Upgrade

    Latest: Ask Red Hat - Safety Model Upgrade

See the full Quay outage history

30 more incidents in the last 90 days, plus the full multi-year archive of per-service events and update timelines.

Browse Quay outage history →

Or sign up free to get alerts when Quay breaks · 10 free monitors · No credit card

Outage history

Past 90 days · 34 incidents View full outage history →