The issue with Google Kubernetes Engine GetClusters API endpoint in europe-west3 and us-east1 has been resolved for all affected users as of 2019-02-26 20:50 US/Pacific. We will conduct an internal investigation of this issue and make appropriate improvements to our systems to help prevent or minimize future recurrence.

Our engineering team is continuing to work on the issues. We will provide another status update by Tuesday, 2019-02-26 21:00 US/Pacific with current details.

Mitigation work is currently underway by our Engineering Team. We will provide another status update by Tuesday, 2019-02-26 20:00 US/Pacific with current details.

Further to this, the issue persists despite the previously published actions and we are pursuing alternative solutions. We will provide another status update by Tuesday, 2019-02-26 19:00 US/Pacific with current details.

Mitigation work is currently underway by our Engineering Team. We are currently rolling back a change to mitigate the issue in the affected regions. We will provide another status update by Tuesday, 2019-02-26 18:00 US/Pacific with current details.

We are experiencing an issue with Google Kubernetes Engine GetClusters API endpoint beginning Tuesday, 2019-02-26 14:52 US/Pacific. Current data indicate(s) that this issue affects europe-west3 and us-east1. The issue partially affected europe-west2-a and us-east1-d but these zones have recovered as of Tuesday, 2019-02-26 15:10 US/Pacific.

Users affected by this issue may receive HTTP 5XX errors when listing clusters with the GetClusters API Endpoint. Users will also be unable to resize, upgrade or repair their clusters in the affected regions.

For everyone who is affected, we apologize for the disruption. We will provide an update by Tuesday, 2019-02-26 16:30 US/Pacific with current details.

Issues with Google Kubernetes Engine GetClusters API endpoint in europe-west3 and us-east1.