Is Quay.io down in the US?
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.
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 passingin the US, measured from Ashburn and San Jose
All 2 of our probes in the US, in Ashburn and San Jose, read checks passing when they last checked Quay.io at Nov 5, 2026, 5:54 PM UTC.
Over the last 24 hours we completed 256 checks from Ashburn and San Jose and 256 answered cleanly, 100.00% availability.
Of the 2 other regions we check Quay.io from, all 2 read checks passing right now.
Email me when Quay.io reports an incident on its status page, and again when it reports it resolved.
What our Ashburn and San Jose probes measured
Last checked Nov 5, 2026, 5:54 PM UTC.
Quay.io from Ashburn and San Jose over the last 30 days
Over the last 30 days, Quay.io answered our Ashburn probe in 809 ms on average, and 1 check in 20 took longer than 1,240 ms.
Over the last 30 days, Quay.io answered our San Jose probe in 1,370 ms on average, and 1 check in 20 took longer than 1,928 ms.
Ranked by average response time across the 4 cities we check Quay.io from, Ashburn 1st, San Jose 3rd; Ashburn was fastest at 809 ms and Tokyo slowest at 2,425 ms.
From Ashburn and San Jose we ran 794 checks of Quay.io in 4 days, and 793 answered cleanly: 99.87% availability.
1 of the 4 days had at least one failed check. The weakest was Nov 3 (UTC), at 99.59% across 247 checks.
In Ashburn local time (EST), Quay.io was slowest around 2 AM, at 971 ms on average over the last 14 days, and quickest around 12 AM, at 425 ms.
| Day (UTC) | Checks | Availability | Average response |
|---|---|---|---|
| Thu, Nov 5 | 192 | 100.00% | 1,050 ms |
| Wed, Nov 4 | 251 | 100.00% | 1,061 ms |
| Tue, Nov 3 | 247 | 99.59% | 1,015 ms |
| Mon, Nov 2 | 104 | 100.00% | 1,131 ms |
Quay.io outages measured from the US
Our Ashburn and San Jose probes measured no confirmed Quay.io outage in the last 90 days.
How the other regions read right now
Of the 2 other regions we check Quay.io from, all 2 read checks passing right now.
| Probe city | Right now | Last 24h |
|---|---|---|
| Frankfurt | Checks passing | 100.00% of 101 checks |
| Tokyo | Checks passing | 100.00% of 62 checks |
Other countries we check Quay.io from
How we measured this
The US readings on this page come from RealUptime's own Ashburn and San Jose probes against Quay.io's public endpoints. They are not user reports, and they are not Quay.io's own status page.
See Quay.io's full check readings, the 90-day history by region, or the outage tracker methodology.
The US readings here are taken from that country and show the time of the last one, but Quay.io has not yet accumulated enough continuous history for us to publish this page to search engines.
Check your own site from Ashburn
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 serversRun 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