A e2-medium VM instance is currently unavailable in the us-central1-b zone

[Sundog]

I have been getting the following error every single time I try to start my virtual machine for the past week. I had been using it for months before that without any issues. Why all the sudden are there not enough resources when that has never been a problem until now?

Is there a status page where I can see the current available resources at different server locations?

Is this something that I should anticipate going forward? When I migrated computing to Google Cloud, my goal was to improve reliability, access, and uptime when I need it.

I had chosen us-central1-b because it was the lowest cost, but is there a way to build a virtual machine that automatically picks the lowest-cost available region each time I start it? It's a hassle to image and clone the VM every time I need to pick a new region.

Error:
Failed to start instance1: A e2-medium VM instance is currently unavailable in the us-central1-b zone. Alternatively, you can try your request again with a different VM hardware configuration or at a later time. For more information, see the troubleshooting documentation.

[FrancoGP]

Hi @Sundog ,

Welcome to Google Cloud Community! 

If you are thinking about costs and savings for your vms, maybe a good idea would be to create spot machines, if you can sustain disruptions in your workload. 

There isn't currently (to my knowledge) any sum check of available resources per region, but shouldn't be a big deal to create a new one if you distribute the image in all regions and projects (if needed).

May I recommend you look for reservations on compute resources? I think it completely applies to your case and needs