Incident affecting Cloud Developer Tools, Cloud Build
Performance of Github-related triggers is degraded in Cloud Build
Incident began at 2023-03-27 05:48 and ended at 2023-03-27 06:52 (all times are US/Pacific).
Previously affected location(s)
Taiwan (asia-east1)Hong Kong (asia-east2)Tokyo (asia-northeast1)Osaka (asia-northeast2)Seoul (asia-northeast3)Mumbai (asia-south1)Singapore (asia-southeast1)Jakarta (asia-southeast2)Sydney (australia-southeast1)Warsaw (europe-central2)Finland (europe-north1)Belgium (europe-west1)London (europe-west2)Frankfurt (europe-west3)Netherlands (europe-west4)Zurich (europe-west6)GlobalMontréal (northamerica-northeast1)São Paulo (southamerica-east1)Iowa (us-central1)South Carolina (us-east1)Northern Virginia (us-east4)Oregon (us-west1)Los Angeles (us-west2)Salt Lake City (us-west3)Las Vegas (us-west4)
| ||27 Mar 2023||06:52 PDT|| |
The issue with Cloud Build has been resolved for all affected projects as of Monday, 2023-03-27 06:48 US/Pacific.
We thank you for your patience while we worked on resolving the issue.
| ||27 Mar 2023||06:03 PDT|| |
Summary: Performance of Github-related triggers is degraded in Cloud Build
Description: We are experiencing an issue with Cloud Build.
Our engineering team continues to investigate the issue.
We will provide an update by Monday, 2023-03-27 07:00 US/Pacific with current details.
Diagnosis: If the customers push to Github repo, their triggers may not not trigger a build. If the customers try to set up a new trigger Github might respond with '500' error.
Workaround: None at this time.
- All times are US/Pacific