The unavailability of the resource is a particular zone/region is something that considered as rare occurrence. Google's infrastructure management team should receive a notification regarding this already. For the time being, I would recommend you to re-deploy the service(VM) is a different zone where the resource is currently available. However, kindly keep in mind that not all resources are globally available. Feel free to refer
this document as it describes global, regional, and zonal Compute Engine resources. The
sortable table provided in the help center article about '
the list of available regions and zones' lets you to select different options to see where resources are available. Once you decided the resource and respective zone/region, you might need to refer our help center about “
Moving an Instance Between Zones” as well.
On an additional note, always deploying and balance the workloads across multiple regions. This is a good approach for any production environment. Kindly review our public
documentation which outlines how to build and design robust systems.
If the issue is keep persisting in the asia-south1 region, I would strongly recommend you to report it using
issue tracker to get additional support from Google Cloud's Compute Engine team.