I've been unable to launch a fairly beefy machine (e2-custom-8-18432) in us-east4-c since yesterday evening.

I launch this machine via a schedule every day at 5pm.

Recently moved it from us-east4-a, as i had been seeing the errors there.

I've been using gcloud for a long time and until this month I've never had this error come up?

I'm even willing to reserve an instance, but will this help?