I can't ping any server in asia-east1-b

[ericweng07]

Suddenly I can't connect to my server and I try to ping my server there is no response. 
I create a brand new instance on asia-east1-b  but I still can't ping the server.
If I create a instance on asia-east1-a or asia-east1-c , I can ping the server. 
Please help!

[DamianS]

Hello @ericweng07  ,Welcome on Google Cloud Community.

This site https://status.cloud.google.com/regional/asia  shows that there is no issues in your region, thus if ICMP is allowed, you should be able to ping VMs in asia-east1-b. Are you sure that any single FW rule has not beet changed or VPC config ( especially with routing part) has not been changed for asia-east1-b zone ?

Reason I'm asking is because I've created fresh VM under asia-east1-b and I was able to execute ping without any issues AFTER adding icmp allow FW rule. 

--
cheers,
DamianS
LinkedIn medium.com Cloudskillsboost

[jamespatrickm]

Hi @ericweng07 ,

Welcome to Google Cloud Community!

I agree with @DamianS’ answer. I did try to create a new VM also under asia-east1-b and was able to ping it after my VM’s firewall rules allow ICMP traffic. Just be mindful of the best practices for firewall rules as firewall rules are evaluated in order. Your ICMP rules may get overridden by a more limiting rule.

Also, an invaluable tool that I can think of in this scenario is the Connectivity Test under our Network Intelligence Center. This will enable you to monitor your networks which is very handy in these kinds of situations.

Hope this helps.

[ericweng07]

This unavailable status lasts for 1 hour and suddenly return to normal. 
I'm sure.... There were some accident happened for 1 hour, however , it okay after 1 hour.