[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-06-16。"],[],[],null,["# Pricing\n\n| **Warning:** Certain Classic VPN dynamic routing functionality is deprecated. For more information, see [Classic VPN dynamic routing partial deprecation](/network-connectivity/docs/vpn/deprecations/classic-vpn-deprecation).\n\nAt a high level, your Cloud VPN charges consist of the following:\n\n- An hourly charge for each Cloud VPN gateway; this charge is determined partly by the number of tunnels attached to the gateway, as well as the location of the gateway\n- A monthly charge for IPsec traffic\n- An hourly charge for any external IP address assigned to a VPN gateway but *not* used by a tunnel\n\nFor more information about Cloud VPN, see the\n[Cloud VPN overview.](/network-connectivity/docs/vpn/concepts/overview)\n| **Note:** Only VPN tunnels in [certain\n| tunnel states](/network-connectivity/docs/vpn/resources/troubleshooting#message_list) are billed.\n\nPricing table\n-------------\n\nTo view pricing, select the location of the Cloud VPN gateway.\nExcept where otherwise noted, all details apply to both Classic VPN and\nHA VPN.\n\n\nGoogle does not charge for forwarding rules that send traffic to the VPN gateway.\nIf you pay in a currency other than USD, the prices listed in your currency on [Cloud Platform SKUs](https://cloud.google.com/skus/) apply.\n\nPricing scenarios\n-----------------\n\nFor help understanding Cloud VPN pricing, refer to the following examples.\n\n### `us-central1` gateway to data center\n\nSuppose you have a VPN gateway in `us-central1`. That gateway uses two tunnels to\nconnect with an on-premises data center in Iowa.\n\nEach month, you send 2 tebibytes (TiB) of data through the tunnel, from your\nVirtual Private Cloud (VPC) network to your data center. At the same time, you send 2 TiB in\nthe other direction---from the data center to your VPC network.\n\nAdditionally, your\ngateway uses a reserved external IP address.\n\nThe following table shows the charges that you'd incur during a 30-day month with this setup.\n\n### `asia-northeast1` gateway to data center and another\nVPC network\n\nSuppose your project has a VPC network called Network A, which includes a\nVPN gateway in `asia-northeast1`. This gateway\nuses two tunnels to connect with an on-premises data center in\nTokyo. Additionally, this gateway uses two tunnels to connect with Network B, another\nVPC network in your project. Network B's gateway is located in\n`europe-west6`.\n\nEach month, your data usage is as follows:\n\n- Users in Network A download 10 TiB of data from Cloud Storage and send it to the Tokyo data center.\n- Networks A and B send each other about 20 TiB of data.\n\nBoth the `asia-northeast1` and `europe-west6` gateways use reserved\nexternal IP addresses.\n\nAdditionally, you have a third VPN gateway in\n`southamerica-east1`. You created this gateway several months ago and assigned it a\nreserved external IP address. However, you never set up a tunnel for this gateway.\n\nThe following table shows the charges that this setup would incur during a 30-day month.\n\nWhat's next\n-----------\n\n- To find pricing information for other Network Connectivity products, see [Network Connectivity pricing](/network-connectivity/pricing)."]]
