Skip to content

Outage tracker / Quay.io

Is Quay.io down?

Short linkrlup.io/down/quay

I'm having a problem

Vendor reports an incidentWhat Quay.io reports

Quay.io reports an incident on its status page: Docs.redhat.com - Intermittent performance degradation.

Impact: major. Since 2026-11-05 11:40 UTC.

Latest update, 2026-11-05 11:40 UTC: We are experiencing intermittent performance issues on docs.redhat.com. Some users may see slow page loads, timeouts, or pages that fail to load. We are currently investigating the issue.

Quay.io's status page

Our regional reading

This is our own reading from outside, shown beside the vendor's statement. It is not counted as a separate outage.

Checks passingchecked 6 minutes ago

Our checks of Quay.io pass from all 4 regions we check.

As of Nov 5, 2026, 2:27 PM UTC, RealUptime's checks of Quay.io passed in all 4 regions that returned a reading.

Front-door and live API checks

our check readinglive · checked Nov 5, 2026, 2:27 PM UTC
US-East730 msChecks passing
US-West1358 msChecks passing
Europe1200 msChecks passing
Asia-Pacific2227 msChecks passing
their status pagetheir claim, not our reading

Quay.io reports: Partial outage (“Partial System Outage”)

from Quay.io's own status page, checked Nov 5, 2026, 1:56 PM UTC

Quay.io reports an active incident: Docs.redhat.com - Intermittent performance degradation (partial outage, since Nov 5, 2026, 11:40 AM UTC)

Quay.io's status page reports Partial System Outage. Our checks of Quay.io currently pass with normal latency. Our checks currently pass from all 4 regions. These observations can coexist: a partial error-rate degradation on their side does not have to affect every request. Our checks measure whether a single request succeeds, not the vendor's internal error rate, so this can happen when an issue affects only part of a service that our simple check does not exercise. We show the vendor's report and our check reading side by side. A check can miss problems that users see. Read both before you draw a conclusion.

Quay.io's own component breakdown, as they publish it

  • APIOperational
  • APIOperational
  • API ManagerOperational
  • Ansible Automation Platform - Automation AnalyticsOperational
  • Ansible LightspeedOperational
  • AskOperational
  • Catalog AppOperational
  • ContentOperational
  • Docs MCPOperational
  • DownloadsOperational
  • HomepageOperational
  • HomepageOperational
  • HomepageOperational
  • HomepageOperational
  • OpenShift Update ServiceOperational
  • Partner Container Certification WorkflowOperational
  • Registry Account ManagementOperational
  • maven.repository.redhat.comOperational
  • subscription.rhsm.redhat.comOperational
  • Ansible Automation Platform - Automation HubOperational
  • Assisted Installer ServiceOperational
  • Build SystemOperational
  • Community and DiscussionsOperational
  • Container APIOperational
  • HomepageOperational
  • HomepageOperational
  • HomepageOperational
  • Partner Acceleration DeskOperational
  • Product MCPOperational
  • Red Hat Ansible Automation Platform Service on AWS: ProvisioningOperational
  • SearchOperational
  • api.rhsm.redhat.comOperational
  • npm.registry.redhat.comOperational
  • redhat.atlassian.netOperational
  • registry.redhat.ioOperational
  • ComplianceOperational
  • Core PlatformOperational
  • Partner Account ManagementOperational
  • Product HubOperational
  • Red Hat Ansible Automation Platform Service on AWS: Existing DeploymentsOperational
  • RegistryOperational
  • SSO AuthenticationOperational
  • SearchOperational
  • SearchMajor outage
  • Security MCPOperational
  • cdn.redhat.comOperational
  • registry.access.redhat.comOperational
  • repository.jboss.orgOperational
  • Cost ManagementOperational
  • Customer Service WebformOperational
  • FrontendOperational
  • Partner PortalOperational
  • Product IndexOperational
  • SSO AuthenticationOperational
  • SSO AuthenticationOperational
  • Web Page ContentOperational
  • registry.connect.redhat.comOperational
  • DownloadsOperational
  • ExpertsOperational
  • OpenShift Cluster ManagerOperational
  • Partner Program ContentOperational
  • SearchOperational
  • Security ScanningOperational
  • HomepageOperational
  • OpenShift DedicatedOperational
  • Partner Relationship ManagementOperational
  • KnowledgebaseOperational
  • Partner SubscriptionsOperational
  • RBACOperational
  • Service Management APIOperational
  • LabsOperational
  • Partner Training PortalOperational
  • Red Hat Advanced Cluster Security Cloud ServiceOperational
  • Product Life CyclesOperational
  • Red Hat Content CenterOperational
  • Red Hat Lightspeed - AdvisorOperational
  • Red Hat Lightspeed - Advisor (Openshift) - APIOperational
  • SearchOperational
  • SearchOperational
  • Red Hat Lightspeed - Chrome ServiceOperational
  • SSO AuthenticationOperational
  • Security PagesOperational
  • Red Hat Lightspeed - Cloud-ConnectorOperational
  • SFTPOperational
  • Red Hat Lightspeed - ComplianceOperational
  • SSO AuthenticationOperational
  • Red Hat Lightspeed - Export-ServiceOperational
  • StartOperational
  • Red Hat Lightspeed - Image BuilderOperational
  • Start a CallOperational
  • Red Hat Lightspeed - InventoryOperational
  • Subscription Management APIOperational
  • Red Hat Lightspeed - Malware DetectionOperational
  • Subscription Management FrontendOperational
  • Red Hat Lightspeed - Malware detectionOperational
  • Support CasesOperational
  • Red Hat Lightspeed - NotificationsOperational
  • Red Hat Lightspeed - PatchOperational
  • Red Hat Lightspeed - PlanningOperational
  • Red Hat Lightspeed - Playbook-DispatcherOperational

These are Quay.io's components, named and scored by Quay.io. We do not map them onto the functions we check above, because we have no way to know which of their components our checks touch. Two lists, side by side, neither one rewriting the other.

This is Quay.io's own claim about their service, shown separately from what we measured. We never change our own numbers based on what a vendor reports, and this reading never changes theirs. Read both.

Quay.io response time, by region

US-East
1.4sp95 · latest
2s1s0ms
US-East response time (p95) over the last 30 daysDaily 95th-percentile response time for US-East, scaled to a maximum of 2s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.3s2026-11-03 UTC: p95 1.1s2026-11-04 UTC: p95 1.3s2026-11-05 UTC: p95 1.4s
Oct 7Oct 21Nov 5
US-West
2.2sp95 · latest
2.5s1.3s0ms
US-West response time (p95) over the last 30 daysDaily 95th-percentile response time for US-West, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.9s2026-11-03 UTC: p95 1.7s2026-11-04 UTC: p95 2.1s2026-11-05 UTC: p95 2.2s
Oct 7Oct 21Nov 5
Europe
2.4sp95 · latest
2.5s1.3s0ms
Europe response time (p95) over the last 30 daysDaily 95th-percentile response time for Europe, scaled to a maximum of 2.5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 1.4s2026-11-03 UTC: p95 1.3s2026-11-04 UTC: p95 1.5s2026-11-05 UTC: p95 2.4s
Oct 7Oct 21Nov 5
Asia-Pacific
2.7sp95 · latest
5s2.5s0ms
Asia-Pacific response time (p95) over the last 30 daysDaily 95th-percentile response time for Asia-Pacific, scaled to a maximum of 5s. Days with no samples are not plotted, not shown as zero.2026-11-02 UTC: p95 4.1s2026-11-03 UTC: p95 2.7s2026-11-04 UTC: p95 2.8s2026-11-05 UTC: p95 2.7s
Oct 7Oct 21Nov 5

Check your own site while you wait on Quay.io

Watching an outage above does not tell you whether your own connection or site is also having a problem. Enter your own URL for one live check, right now, no signup. This checks the site you enter, not Quay.io. It cannot diagnose Quay.io's own systems.

What we measured, function by function

Quay.io answers on more than one surface, and they can fail apart. Each row is one surface, checked from the same regions. The verdict above follows the api row, because that is the surface we treat as this service's own; a failure on any other row is a partial outage, not a full one.

  • WebUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region
  • APIprimaryUS-East: Checks passingUS-West: Checks passingEurope: Checks passingAsia-Pacific: Checks passingUS-Central: Not monitored from this regionCanada: Not monitored from this regionUK: Not monitored from this regionSoutheast Asia: Not monitored from this regionAustralia: Not monitored from this regionSouth America: Not monitored from this region

Email me when Quay.io reports an incident on its status page, and again when it reports it resolved.

Get an email when Quay.io reports an incident

Email me when Quay.io reports an incident on its status page, and again when it reports it resolved. No account, no card.

Delivery channel

Double opt-in: nothing is sent until you click the link in the confirmation email. One email when it reports an incident, one when it reports it resolved, and a one-click unsubscribe in every one. We do not send anything else to this address.

This is Quay.io's own statement from its status page, with our regional reading beside it.

What are you seeing? (optional)

No account needed, and we never store your IP address. Reports are counted separately from our own measurements and are always shown as unverified.

What our checks show, and what people reported

  • North America
    Not monitored from this regionUS-East, US-West, US-Central, Canada
    • US-East
      Checks passinglatency: 730msstatus code: 200checked: Nov 5, 2026, 2:27 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-East probes reach Quay.io normally. We do not have enough reports from US-East to say anything about what people there are seeing.
    • US-West
      Checks passinglatency: 1358msstatus code: 200checked: Nov 5, 2026, 2:21 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur US-West probes reach Quay.io normally. We do not have enough reports from US-West to say anything about what people there are seeing.
    • US-Central
      Not monitored from this regionQuay.io is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Canada
      Not monitored from this regionQuay.io is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • South America
    Not monitored from this regionQuay.io is not monitored from this region.
    0 people in the last 5 minutesNot enough reports to say
  • Europe
    Not monitored from this regionEurope, UK
    • Europe
      Checks passinglatency: 1200msstatus code: 200checked: Nov 5, 2026, 2:24 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Europe probes reach Quay.io normally. We do not have enough reports from Europe to say anything about what people there are seeing.
    • UK
      Not monitored from this regionQuay.io is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
  • Asia Pacific
    Not monitored from this regionAsia-Pacific, Southeast Asia, Australia
    • Asia-Pacific
      Checks passinglatency: 2227msstatus code: 200checked: Nov 5, 2026, 2:23 PM UTC
      0 people in the last 5 minutesNot enough reports to sayOur Asia-Pacific probes reach Quay.io normally. We do not have enough reports from Asia-Pacific to say anything about what people there are seeing.
    • Southeast Asia
      Not monitored from this regionQuay.io is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say
    • Australia
      Not monitored from this regionQuay.io is not monitored from this region.
      0 people in the last 5 minutesNot enough reports to say

Somewhere else or not sure: 0 people in the last 5 minutes

These are unverified reports from people using Quay.io, counted separately from what our own probes measure. Anyone can file one, no account is needed, and the region on a report is chosen by the person filing it. We never open, extend or close an outage in our record based on report volume: only our own measurements do that. We have not received any reports for Quay.io yet, which is not evidence that nothing is wrong.

Recent probe events

Docs.redhat.com - Intermittent performance degradationdeclared on their status page2026-11-05
access.redhat.com - Community and Discussions, 71h 40mdeclared on their status page2026-10-30
API errors, 2h 12mdeclared on their status page2026-10-29
Red Hat Lightspeed Compliance Degraded Performance, 96h 19mdeclared on their status page2026-10-29
Red Hat Connect Major Outage - Investigating, 1h 49mdeclared on their status page2026-10-26
Quayio Is Facing Intermittent 500s Due to a Service Maintenance, 8h 56mdeclared on their status page2026-10-24
access.redhat.com - Security Pages - CVE Outage, 288h 8mdeclared on their status page2026-10-23
"access.redhat.com - Security Pages - CVE Outage, 25mdeclared on their status page2026-10-23

check entries are our own probes' readings; declared entries are the vendor's. How this check works

We have been measuring Quay.io since November 2, 2026. We show nothing from before that date, and we never add an outage we did not observe ourselves, from any source.

Need this in writing? Generate an SLA evidence report for Quay.io covering any window you pick, with our check readings and Quay.io's own claim at the time, side by side.

Full check history for Quay.io: 90 days of check results by region, month-by-month uptime by our checks, and every probe event on record.

Monitor your own site the same way

This page shows what we see when we check this service, using the same ten regions, for a site you run. RealUptime Monitor watches your own servers from inside your network, and it starts free.

Start monitoring your own servers

Run a service people depend on? Give them a status page on your own domain, checked every minute from six regions, for $9 a month. Get Starter

Put this badge in your README

Quay.io uptime by RealUptime's checksLive, from this page's own readings.
[![Quay.io uptime by RealUptime's checks](https://realuptime.io/outages/quay/badge.svg?days=30)](https://realuptime.io/outages/quay)
<a href="https://realuptime.io/outages/quay"><img src="https://realuptime.io/outages/quay/badge.svg?days=30" alt="Quay.io uptime by RealUptime's checks" height="20"></a>

Share of checks passed over 30 days; the window is printed on it. If our readings go stale it says stale, and if we have no readings it says so and shows no color. How the badge works.

To cite this page: RealUptime, "Is Quay.io down?", https://realuptime.io/outages/quay. The readings change with every check, so give the date you read them.

What we check

secondary
https://quay.io/
secondary
https://status.redhat.com/
primaryfunctional: live API
https://quay.io/api/v1/discovery

What our check can and cannot see

A pass means the configuration document the service publishes, such as an API or sign-in description, loaded. That document is usually static or cached, so it does not show that the endpoints it describes are answering.

Host checked: quay.io

RealUptime is not affiliated with Quay.io; the name identifies what we checked, and nothing here speaks for Quay.io's own team. We send a single web request to Quay.io from 4 regions on our own schedule and time the response. We do not see inside Quay.io's systems, do not use an account or real transaction, and are not the same signal Quay.io's own team has access to. Treat this as one external data point, not a verdict. At least one endpoint we check for Quay.io is a real functional API call (marked “functional” above), not just a landing page, so a passing check there says an API answered, though it still does not show that every feature of the service works for you. Quay.io operates in a limited set of regions, so we only check it from where it is actually available; we do not probe from a region we know it does not serve. We started monitoring this service on November 2, 2026 (3 of 14 days so far, 3714 of 500 checks). We show a full track record once we have enough continuous history. Check back soon, or monitor your own site continuously with RealUptime. Read the full methodology.

Related services

1PasswordAWS (Amazon Web Services)AblyAcuity SchedulingAdobe Fonts