Is Quay.io Down?

This page shows the live Quay.io status so you can confirm in seconds if Quay.io is down.

Quay.io current status

Updated

Quay.io is operational

IsDown pulls data from the official status page every few minutes and collects user-reported Quay.io issues.
Refresh the page to see the latest updates.

Get Quay.io outage alerts in
Slack Slack Teams Teams Datadog Datadog PagerDuty PagerDuty

Quay.io user-reported issues in the last 24 hours

This chart displays the number of user-reported Quay.io problems over the past 24 hours, grouped into 20-minute intervals. It's normal to see occasional reports, which may be due to individual user issues rather than a broader problem.

IsDown Logo Third-party monitoring

All Your Service Status Pages in One Dashboard

Monitoring 4000+ third-party services in real-time
Get custom alerts via Slack, Teams, Datadog, etc.
Create public or private status pages
Start Free Trial
14-day free trial · No credit card required
Trusted by thousands of teams

Quay.io outage history

IsDown has tracked 168 incidents since started monitoring Quay.io downtimes in June 2020. We are also collecting data from 4000+ services, and normalize the data to give you a clear picture of the impact of the outage.

  • May 05 2025
    connect.redhat.com container factory component outage

    5 days ago · lasted about 3 hours

    connect.redhat.com container factory component outage

  • Apr 24 2025
    Connect.redhat.com Outage

    16 days ago · lasted about 2 hours

    An outage has been detected on connect.redhat.com. It impacts account management, the container factory, and partner subscriptions on connect.redhat.com. We are currently working to restore the functionality.

  • Apr 15 2025
    Quay.io Intermittent 502s

    25 days ago · lasted 7 days

    We are currently investigating this issue.

  • Apr 02 2025
    Quay.io Intermittent 502s

    about 1 month ago · lasted about 4 hours

    We are currently investigating this issue.

  • Apr 02 2025
    MWNX-001 - repository.jboss.org

    about 1 month ago · lasted about 2 hours

    Team is currently investigating this issue.

  • Jun 2020 ...
    IsDown started monitoring Quay.io status

    We've tracked and collected 168 incidents since started monitoring Quay.io status

Sign up and check all outage history

Latest user comments about Quay.io issues

  • D

    Diana

    I experience image pull issue for some images like prometheus/node-exporter:v1.8.1

  • J

    joep

    seeing loads of 502: bad gateway errors

  • A

    Adi

    502 bad gateway when trying to initialize source, determining manifest MIME type, trying to reuse blob container

  • L

    Luke

    Cannot pull some docker images form quay.io/v2

  • K

    Kien

    quay.io is unaccessible at this time.

  • B

    Brian

    Cannot access quay.io from australia

  • R

    Ryan

    going to quay.io gives a 500 error/page

  • D

    danila

    cant ping from cmd or vmware ubuntu

  • V

    veekaly

    I'm not able to pull official prometheus (quay.io/prometheus/prometheus) images from Quay

  • O

    Omar

    Server Down or bad Gateway

  • P

    Priit

    Image pull backoff from registry

  • R

    Robert

    Requests return 502, or time-out

  • J

    jooyoung

    Registry

    can not pull image "https://quay.io/v2/prometheus/node-exporter/manifests/v1.7.0"

  • M

    m

    Failed to pull image "quay.io/prometheus/node-exporter:v1.7.0": failed to pull and unpack image "quay.io/prometheus/node-exporter:v1.7.0": failed to copy: httpReadSeeker: failed open: unexpected status code https://quay.io/v2/prometheus/node-exporter/manifests/sha256:52a6f10ff10238979c365c06dbe...

  • L

    Ludost

    502 Bad Gateway on the main page and on the docker repositories

  • P

    Paul

    Error response from daemon: login attempt to https://quay.io/v2/ failed with status: 502 Bad Gateway An error occurred. Exiting... ERROR: Something went wrong

Quay.io outages in the last 30 days

Number of Incidents

3 issues

Last incident

5 days ago

IsDown Logo Seamless Integrations

Get Quay.io outage alerts and updates in your favorite tools

Receive vendor outage notifications where your team already works. Compatible with Slack, Microsoft Teams, PagerDuty, Datadog, Better Stack, Rootly, Incident.io, Statuspage.io, and more.
Never miss an outage
Easy setup · No coding required
Works with your existing stack

Having problems with Quay.io? What can you do?

  1. First, stay calm.

    • We know it's stressful when Quay.io is down, but running around is not going to fix it.
    • Remember that it's normal for services to go down sometimes. It can be for a number of reasons, from maintenance to unexpected issues.

  2. Make a quick evaluation of the impact of the Quay.io outage

    • Try to evaluate the impact of the outage on your business. Is it impacting a majority of your users or just a few?
    • Did Quay.io already acknowledge the issue? And published a status update? (You can find it in the top of the page or in Quay.io status page)
    • If not, understand if other users are also experiencing issues. You can also check this information on the top of the page.

  3. Communicate with your team and users quickly

    • If Quay.io is having problems and impacting your business, it's important to keep your team and users informed.
    • Share this page with your team, so you can start incident response procedures. No need for everyone to go around searching for information. Create a post or a specific channel in your internal communication tools (Slack, Teams, Google Chat, etc.) so you can aggregate all the information in one place.
    • If you have a status page, create a status update to inform your users about the issue. This way they know what's going on and you can avoid a flow of support requests overburding your team.

  4. Understand the root cause

    • After the first communication, let's move on to the next step. Do a more thorough investigation to understand the root cause of the issue and impact.
    • Reach out to the service provider to understand if they are aware of the issue and if they are already working on it. You can reach them in their support channels, or their social media channels if they have any.

  5. Is there any mitigation for the issue?

    • Understand if there are workarounds or mitigations for the issue. Can you use a different provider? Is the switch easy to do? Talk with your team to understand the best course of action.
    • Need to wait on the service provider to fix the issue? Understand if there is a timeline for the fix. Adapt your communication with your team and users to the situation. It's very important to keep everyone informed.

  6. Did Quay.io recover?

    • Continue to monitor the situation. A lot of times, the service can see a brief recovery and declare the issue as resolved, but it can come back. Keep monitor for some time to make sure it's really resolved.

  7. Post-incident analysis

    • Once the issue is resolved, it's important to do a post-incident analysis. Understand what went wrong and if it's possible or needed to do something to prevent it from happening again.
    • Sometimes if it's a critical dependency, you might need to have a backup plan in place to avoid a similar issue.
    • Vendors usually publish post-mortem analysis reports, so keep an eye on their social media channels and website for more information.

  8. Prepare for the next incident, because it will happen again

    • Start monitoring your dependencies. Sign up to IsDown and aggregate all your dependencies status in one place.
    • Nowadays, it's very common to have a lot of dependencies, and keeping an eye on them is not an easy task. IsDown can help you with that, by aggregating and monitoring all dependencies status and alerting you if they are having issues. Create status pages to communicate with your team and users.

Related Services Dashboard

Services commonly monitored together with Quay.io

Create your own dashboard
AWS

AWS

OK
Slack

Slack

OK
Stripe

Stripe

OK
Mailjet

Mailjet

OK
Fly.io

Fly.io

OK
GitHub

GitHub

OK
1Password

1Password

OK
TestRail

TestRail

OK
Zoom

Zoom

OK
PagerDuty

PagerDuty

OK
Confluence

Confluence

OK
Google Workspace

Google Workspace

OK
Google Cloud

Google Cloud

OK
Microsoft Office 365

Microsoft Office 365

OK
Jira Software

Jira Software

OK

Want to be informed about Quay.io status changes?

IsDown offers an easy way to monitor Quay.io with maximum flexibility

Major Outages Notifications

IsDown monitors Quay.io for major outages. A major outage is when Quay.io experiences a critical issue that severely affects one or more services/regions. When Quay.io marks an incident as a major outage, IsDown updates its internal status, the customer status page and dashboard. Depending on the customer settings, IsDown will also send notifications.

Minor Outages Notifications

IsDown monitors Quay.io status page for minor outages. A minor outage is when Quay.io experiences a small issue affecting a small percentage of its customer's applications. An example is the performance degradation of an application. When a minor outage occurs, IsDown updates its internal status and shares that information on the customer status page. Depending on the customer settings, IsDown will also send notifications.

Outage Details

IsDown collects all information from the outages published in Quay.io status page to provide the most accurate information. If available, we gather the title, description, time of the outage, status, and outage updates. Another important piece of information is the affected services/regions which we use to filter the notifications that impact your business.

Maintenance Feed

Quay.io publishes scheduled maintenance events on their status page. IsDown collects all the information for each event and creates a feed that people can follow to ensure they are not surprised by unexpected downtime or problems. We also send the feed in our weekly report, alerting the next maintenances that will take place.

Component Filtering

IsDown monitors Quay.io and all their 13 components that can be affected by an outage. IsDown allows you to filter the notifications and status page alerts based on the components you care about. For example, you can choose which components or regions affect your business and filter out all other outages. This way you avoid alert fatigue in your team.

Early Outage Indicators

Quay.io and other vendors don't always report outages on time. Our crowdsourced status platform helps you stay ahead of outages. Users report issues and outages, sharing details on what problems they are facing. We use that info to provide early signs of outages. This way, even without an official update, you can stay ahead of possible problems.

Reports by users in other services in the last 12 hours

Roblox https://roblox.com
Roblox user reports
Instagram https://www.instagram.com/
Instagram user reports
Meta https://meta.com
Meta user reports
Epic Games https://epicgames.com/
Epic Games user reports
Chewy https://www.chewy.com/
Chewy user reports
Astound https://www.astound.com/
Astound user reports
Steam https://store.steampowered.com/?l=portuguese
Steam user reports
Google Cloud https://cloud.google.com/
Google Cloud user reports
SpotOn https://www.spoton.com/
SpotOn user reports
CenturyLink https://www.centurylink.com/
CenturyLink user reports
WileyPLUS https://wileyplus.com
WileyPLUS user reports
TikTok https://www.tiktok.com/
TikTok user reports

Frequently Asked Questions

Is Quay.io down today?

Quay.io isn't down. You can check Quay.io status and incident details on the top of the page. IsDown continuously monitors Quay.io official status page every few minutes. In the last 24 hours, there were 0 outages reported.

What is the current Quay.io status?

Quay.io is currently operational. You can check Quay.io status and incident details on the top of the page. The status is updated in almost real-time, and you can see the latest outages and issues affecting customers.

Is there a Quay.io outage now?

No, there is no ongoing official outage. Check on the top of the page if there are any reported problems by other users.

Is Quay.io slow today?

Currently there's no report of Quay.io being slow. Check on the top of the page if there are any reported problems by other users.

How are Quay.io outages detected?

IsDown monitors the Quay.io official status page every few minutes. We also get reports from users like you. If there are enough reports about an outage, we'll show it on the top of the page.

When was the last Quay.io outage?

Quay.io last outage was on May 05, 2025 with the title "connect.redhat.com container factory component outage"

Quay.io not working for you? How do I know if Quay.io is down?

  • Check on the top of the page if there are any reported problems by other users.
  • Find their support at their official website.
  • Find their support contact at their official status page.

How can I check Quay.io status and outages?

Why use IsDown to monitor Quay.io instead of the official status page?

Because IsDown is a status page aggregator, which means that we aggregate the status of multiple cloud services. You can monitor Quay.io and all the services that impact your business. Get a dashboard with the health of all services and status updates. Set up notifications via Slack, Datadog, PagerDuty, and more, when a service you monitor has issues or when maintenances are scheduled.

How IsDown compares to DownDetector?

IsDown and DownDetector help users determine if a service is having problems. The big difference is that IsDown is a status page aggregator. IsDown monitors a service's official status page to give our customers a more reliable source of information. The integration allows us to provide more details about the outage, like incident title, description, updates, and the parts of the affected service. Additionally, users can create internal status pages and set up notifications for all their third-party services.

Never again lose time looking in the wrong place

Start Monitoring in 5 minutes

14-day free trial · No credit card required · No code required