Investigating - We are currently investigating this issue.
Apr 6, 19:01 EDT
Registry Operational
API Operational
Build System Operational
Frontend ? Operational
Security Scanning Operational
Amazon Web Services Operational
Database Operational
GitHub ? Operational
Payment Management Operational
Plan Management Operational
Atlassian Bitbucket Webhooks ? Operational
Atlassian Bitbucket SSH Operational
Atlassian Bitbucket API Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Past Incidents
Apr 5, 2020

No incidents reported.

Apr 4, 2020

No incidents reported.

Apr 3, 2020

No incidents reported.

Apr 2, 2020

No incidents reported.

Apr 1, 2020

No incidents reported.

Mar 31, 2020

No incidents reported.

Mar 30, 2020

No incidents reported.

Mar 29, 2020

No incidents reported.

Mar 28, 2020

No incidents reported.

Mar 27, 2020

No incidents reported.

Mar 26, 2020
Resolved - We've deployed a fix to bypass the GitHub permission indicator returned by their API, which should allow for creation of triggers
Mar 26, 17:37 EDT
Identified - Due to an apparent change in the GitHub API response around repository permissions, Quay is showing "Admin permissions required" for creating triggers on certain GitHub repositories, despite users having said permissions on those repositories. We've reached out to GitHub to determine the root cause.

As a workaround, users can grant themselves explicit admin access on the GitHub repository for which they wish to add a build trigger. We are also currently investigating a hotfix change on our end to remove this check temporarily.
Mar 26, 12:28 EDT
Mar 25, 2020

No incidents reported.

Mar 24, 2020

No incidents reported.

Mar 23, 2020

No incidents reported.