Google Cloud Service Health

Google Cloud Service Health
Incidents
Global: Issues with populating a UI element in Cloud Console for Cloud Run, Google Container Registry and Artifacts Registry

This page provides status information on the services that are part of Google Cloud. Check back here to view the current status of the services listed below. If you are experiencing an issue not listed here, please contact Support. Learn more about what's posted on the dashboard in this FAQ. For additional information on these services, please visit https://cloud.google.com/.

Available
Service information
Service disruption
Service outage

Incident affecting Cloud Developer Tools, Cloud Run, Container Registry, Artifact Registry, Google Cloud Console

Global: Issues with populating a UI element in Cloud Console for Cloud Run, Google Container Registry and Artifacts Registry

Incident began at 2021-10-20 08:06 and ended at 2021-10-21 09:27 (all times are US/Pacific).

Date	Time	Description
21 Oct 2021	12:15 PDT	We apologize for the inconvenience this service disruption/outage may have caused. We would like to provide some information about this incident below. Please note, this information is based on our best knowledge at the time of posting and is subject to change as our investigation continues. If you have experienced impact outside of what is listed below, please reach out to Google Support by opening a case using https://cloud.google.com/support (All Times US/Pacific) Incident Start: 04 October 2021 16:20 Incident End: 20 October 2021 11:24 Duration: 15 days, 19 hours, 4 minutes Affected Services and Features: Google Cloud Build, Google Cloud Run, Google Container Registry, Artifacts Registry Regions/Zones: Global Description: Google Cloud Run, Google Container Registry, and Artifacts Registry experienced issues displaying build and source provenance information in Cloud Console for 15 days, 19 hours, and 4 minutes. From preliminary analysis, the root cause of the issue was related to a recent deployment that introduced a new type of provenance and deprecated an old type. Engineers rolled back the deployment to resolve the issue. Customer Impact: Build and source provenance for Cloud Build, Cloud Run, Container Registry, and Artifacts Registry were not being populated in Google Cloud Console.
21 Oct 2021	09:27 PDT	The issue with Container Analysis API has been resolved for all affected users as of Thursday, 2021-10-21 09:27 US/Pacific. We thank you for your patience while we worked on resolving the issue.
20 Oct 2021	12:02 PDT	Summary: Global: Issues with populating a UI element in Cloud Console for Cloud Run, Google Container Registry and Artifacts Registry Description: Mitigation work is currently underway by our engineering team The mitigation is expected to complete by Thursday, 2021-10-21 and We will provide more information by Thursday, 2021-10-21 12:00 US/Pacific. Diagnosis: Customers were able to look in the Cloud Run, Google Container Registry and Artifacts Registry UIs and see the build and source provenance info previously. This information is no longer being populated. Workaround: For Cloud Run, there is no known workaround. For Google Container Registry and Artifacts Registry, if you have a Cloud Build ID, you can use `gcloud build describe <id>` to view the build information.
20 Oct 2021	10:38 PDT	Summary: Issues with Cloud Run - Mitigation start Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2021-10-20 12:30 US/Pacific. Diagnosis: Cloud customers using Cloud Run were able to look back in the UI and see the software source location of their Cloud Run runs, but they can no longer do so. Workaround: None at this time.
20 Oct 2021	09:55 PDT	Summary: Issues with Cloud Run - Mitigation start Description: Mitigation work is currently underway by our engineering team. We do not have an ETA for mitigation at this point. We will provide more information by Wednesday, 2021-10-20 10:48 US/Pacific. Diagnosis: Cloud customers using Cloud Run were able to look back in the UI and see the software source location of their Cloud Run runs, but they can no longer do so. Workaround: None at this time.
20 Oct 2021	08:57 PDT	Summary: Issues with Cloud Run - Our Engineering team is investigating the issue. Description: We are experiencing an issue with Container Analysis API beginning at Wednesday, 2021-10-20 08:45:56 PDT Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2021-10-20 10:00 US/Pacific with current details. Diagnosis: Cloud customers using Cloud Run were able to look back in the UI and see the software source location of their Cloud Run runs, but they can no longer do so. Workaround: None at this time.
20 Oct 2021	08:30 PDT	Summary: Issues with Cloud Run - Our Engineering team is investigating the issue. Description: We are experiencing an issue with Container Analysis API beginning at Wednesday, 2021-10-20 08:45:56 PDT Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2021-10-20 08:59 US/Pacific with current details. Diagnosis: Cloud customers using Cloud Run were able to look back in the UI and see the software source location of their Cloud Run runs, but they can no longer do so. Workaround: None at this time.
20 Oct 2021	08:27 PDT	Summary: Issues with Cloud Run - Our Engineering team is investigating the issue. Description: We are experiencing an issue with Container Analysis API beginning at Wednesday, 2021-10-20 08:06:56 PDT Our engineering team continues to investigate the issue. We will provide an update by Wednesday, 2021-10-20 08:59 US/Pacific with current details. Diagnosis: Cloud customers using Cloud Run were able to look back in the UI and see the software source location of their Cloud Run runs, but they can no longer do so. Workaround: None at this time.

All times are US/Pacific