User reports
0
Near baseline. 0 in the last hour. Typical hour is about 0.
All services / Social
redhat.com · Social
Is Quay down?
Something is off: the vendor reports a minor incident. Official status: Minor Service Outage
What to try while Quay is having problems
- Try a private/incognito window, or another browser or device.
- Switch between Wi-Fi and mobile data to rule out your network.
- Wait a few minutes; most incidents clear on their own.
Live diagnosis
Is it just me?
Finds which layer is broken (the service, its provider, your ISP, DNS, or your own network) and what to try.
Your browser → redhat.com—
Your browser → us—
Our checksReaching it
Official · ReportsMinor incident · Near baseline
DNS (1.1.1.1 · Google)—
Your provider—
Connection—
Upstream—
Press Run testYour browser tests the site, us, and two public DNS resolvers. We never store your IP; only anonymous counts by network and region.
Checks by region
Reachable from all 4 regions we check from.
US East · ORDReachable69 ms · 33 min ago
US West · SJCReachable82 ms · 33 min ago
Europe · AMSReachable135 ms · 33 min ago
Asia-Pacific · KIXReachable65 ms · 33 min ago
Live outage map
No reports in the last 24 hours.
Dots are whole states, provinces or countries, never exact locations. We never store IP addresses, and places with fewer than 3 reports are not shown. Updates every minute.
What's broken
Our checks
Reaching it
Last check reached it in 126 ms · 7 min ago.
Official status
Minor incident
Minor Service Outage Official status page
Reports and checks
Numbers behind the chart
| Time (UTC) | Reports | Baseline | Latency | Failed checks |
|---|---|---|---|---|
| 03:15 | 0 | 0.0 | 125 ms | 0 |
| 03:30 | 0 | 0.0 | 114 ms | 0 |
| 03:45 | 0 | 0.0 | 50 ms | 0 |
| 04:00 | 0 | 0.0 | 142 ms | 0 |
| 04:15 | 0 | 0.0 | 97 ms | 0 |
| 04:30 | 0 | 0.0 | 370 ms | 0 |
| 04:45 | 0 | 0.0 | 50 ms | 0 |
| 05:00 | 0 | 0.0 | 56 ms | 0 |
| 05:15 | 0 | 0.0 | 43 ms | 0 |
| 05:30 | 0 | 0.0 | 78 ms | 0 |
| 05:45 | 0 | 0.0 | 92 ms | 0 |
| 06:00 | 0 | 0.0 | 180 ms | 0 |
| 06:15 | 0 | 0.0 | 59 ms | 0 |
| 06:30 | 0 | 0.0 | 60 ms | 0 |
| 06:45 | 0 | 0.0 | 94 ms | 0 |
| 07:00 | 0 | 0.0 | 59 ms | 0 |
| 07:15 | 0 | 0.0 | 284 ms | 0 |
| 07:30 | 0 | 0.0 | 142 ms | 0 |
| 07:45 | 0 | 0.0 | 104 ms | 0 |
| 08:00 | 0 | 0.0 | 199 ms | 0 |
| 08:15 | 0 | 0.0 | 101 ms | 0 |
| 08:30 | 0 | 0.0 | 229 ms | 0 |
| 08:45 | 0 | 0.0 | 69 ms | 0 |
| 09:00 | 0 | 0.0 | 43 ms | 0 |
| 09:15 | 0 | 0.0 | 95 ms | 0 |
| 09:30 | 0 | 0.0 | 163 ms | 0 |
| 09:45 | 0 | 0.0 | 67 ms | 0 |
| 10:00 | 0 | 0.0 | 79 ms | 0 |
| 10:15 | 0 | 0.0 | 86 ms | 0 |
| 10:30 | 0 | 0.0 | 67 ms | 0 |
| 10:45 | 0 | 0.0 | 83 ms | 0 |
| 11:00 | 0 | 0.0 | 49 ms | 0 |
| 11:15 | 0 | 0.0 | 80 ms | 0 |
| 11:30 | 0 | 0.0 | 228 ms | 0 |
| 11:45 | 0 | 0.0 | 78 ms | 0 |
| 12:00 | 0 | 0.0 | 60 ms | 0 |
| 12:15 | 0 | 0.0 | 121 ms | 0 |
| 12:30 | 0 | 0.0 | 93 ms | 0 |
| 12:45 | 0 | 0.0 | 98 ms | 0 |
| 13:00 | 0 | 0.0 | 65 ms | 0 |
| 13:15 | 0 | 0.0 | 81 ms | 0 |
| 13:30 | 0 | 0.0 | 126 ms | 0 |
Reliability
100%Uptime · 30 days
100%Uptime · 90 days
0 / 0Outages · 30 / 90 days
—Average outage
90 days ago → today. Uptime is from our own HTTP checks; outages are incidents that lasted long enough to list. We have 1 days of data so far, so the 90-day numbers fill in over time.
Embed a live Quay status badge
Free, no iframe or script. Updates every minute and links back here. More options on the embed page · JSON · MCP server
Past outages
No outages on record for Quay yet. Outages of 10 minutes or more get their own page here.
Having trouble with Quay?
One report per service every 10 minutes from this network. No account.
Follow Quay
Get an email when Quay goes down and when it recovers. Free. Confirm by email, unsubscribe anytime.
Want it in a team channel? Send Quay alerts to Slack, Discord or a webhook — free.
Questions
Is Quay down right now?
Something is off: the vendor reports a minor incident. Official status: Minor Service Outage
Quay not working for me but the status is fine. What now?
If Quay is not working only for you, it is usually local: try a different browser or the app, switch between Wi-Fi and mobile data, and clear the cache. If lots of people report it here at the same time, the problem is on Quay's side.
How does Damn is it down decide Quay's status?
Three signals. Anonymous reports are compared with the usual volume for this hour. HTTP checks from Cloudflare have to fail twice in a row before we call our side down. When the vendor publishes a status JSON feed, that incident level is included too.
How often is Quay checked?
About every five minutes. The cron runs each minute and rotates through the catalog, so a full pass takes a few minutes.