What is "Network Egress via Carrier Peering Network" in GCP ?<p>I had expected it to be possible to run a VM in GCP within the Free Tier up to 1GB of bandwidth (excluding China and Australia) from a North American VM.<p>After requesting an explanation from GCP Support for "Network Egress via Carrier Peering Network" charges, I was told Carrier Peering is responsible. (No Carrier Peering enabled).<p>I was then told "is caused by VM-to-VM egress when both VMs are in the same Google Cloud region, regardless of zone, when using the external IP addresses (per GB). " (Only a single VM in the account).<p>I was then told "VPC Network is not included in the Free Tier program. You are running an external IP addresses that is causing the charges on your account. Regular network pricing still applies to all traffic." - I suspect a little disingenuous as a VPC is zero cost. I expected Egress to be billed but only to certain regions outside of the free tier and only after 1GB of traffic to other regions. Neither of which are the case.<p>Is any one able to shed any light on this?
Did you choose the cheaper networking tier ($.06/Gb) vs the GCP standard (maybe called premium now) ($0.10/Gb)<p>I have never seen this charge, but I have never used the cheaper networking, which uses non-gcp networks to lower costs, at the expense of other tradeoffs. This sounds like carrier peering at first read, and that the external network operator may have passed some charges back through GCP to you?<p>If you didn't change any network defaults and you had two vms in same region, different zones being rather chatty, that could do it as well. Using external IPs always incurs a charge.<p><a href="https://cloud.google.com/vpc/network-pricing" rel="nofollow">https://cloud.google.com/vpc/network-pricing</a>