I been having this issue since Monday, is anyone else having this problem? I have same problem in all the west zone, I wonder if its because my account is small or if its a bug
It sounds like you're dealing with a frustrating issue! I haven’t encountered this problem myself, but it could be a bug or something specific to your account. Have you tried reaching out to support or clearing your cache to see if that helps? It might also be worth checking if there are any known outages in the West Zone.
Hi @amousavi14,
Welcome to Google Cloud Community!
Your issue may be subject to certain limitations such as resource quotas, API request limits, or service usage restrictions. You can check the quota usage for your project in the Google Cloud Console under IAM & Admin > Quotas & System Limits. To request a higher quota value, you may follow the steps in Request a higher quota value documentation.
Sometimes, specific services or resources might be unavailable in certain regions or zones due to capacity limits. Google Cloud may temporarily limit the provisioning of resources in specific areas if too many users are active there. This also can happen when you try to request resources in a zone that can't accommodate your request, such as GPUs or CPUs.
For troubleshooting, you can check out the following resources:
Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.
It seems like GCP was out of resource, is there a way that we can track if a region is out of resource and estimate ETA for when the resources will be available?
Hello,
I'm also having the same issue with that region. I checked the quotas and I don't see anything that would be causing it.
I just now got the same error in us-west1-b when I tried resizing a disk from 50G to 60G. My account is also small, just one VM. All my quotas are below 20%.
I was able to resize in us-west1-a on Monday, not sure if that helps you or not. really wish google did a better job notifying us about availability and ETAs to fix it.
When I retried two days later (on 2024-Dec-25), it worked. (Sorry for the delayed update.)