GCE instance creation/start/stop operations failing in us-central1-f

446 views
Skip to first unread message

Google Cloud Platform Status

unread,
Oct 30, 2020, 7:31:05 PM10/30/20
to gce-ope...@googlegroups.com
Description: We are experiencing an issue with Google Compute Engine starting on Friday, 2020-10-30 07:30 US/Pacific. The backlog is continuing to decrease, and delays on new instance creation have significantly decreased from the peak with an average of 1 minute. We are anticipating the backlog to clear in approximately 40 minutes.

We will provide an update by Friday, 2020-10-30 17:00 US/Pacific with current details.

Diagnosis: Affected customers may see delays performing instance operations, but they should eventually complete.

Workaround: When possible try instance operations in other zones.

Google Cloud Platform Status

unread,
Oct 30, 2020, 7:37:53 PM10/30/20
to gce-ope...@googlegroups.com
Description: Other Cloud Services that create instances on demand may be impacted such as: Google Kubernetes Engine, Composer, Dataproc, and Dataflow

We will provide an update by Friday, 2020-10-30 17:00 US/Pacific with current details.

Diagnosis: Affected customers may see delays performing instance operations, but they should eventually complete. Other Cloud Services that create instances on demand may also experience impact such as: Google Kubernetes Engine, Composer, Dataproc, and Dataflow.

Google Cloud Platform Status

unread,
Oct 30, 2020, 7:56:20 PM10/30/20
to gce-ope...@googlegroups.com
Description: We believe the issue with Google Compute Engine operations is partially resolved. All previous operations should have completed, and customers should experience normal latency on new operations.

We will provide an update by Friday, 2020-10-30 17:45 US/Pacific with current details.

Google Cloud Platform Status

unread,
Oct 30, 2020, 8:02:41 PM10/30/20
to gce-ope...@googlegroups.com
The issue with Google Compute Engine has been resolved for all affected users as of Friday, 2020-10-30 16:35 US/Pacific.

We thank you for your patience while we worked on resolving the issue.
Reply all
Reply to author
Forward
0 new messages