[[["易于理解","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-08-12。"],[],[],null,["# CDN Interconnect overview\n\nCDN Interconnect enables select third-party Content Delivery Network (CDN) providers\nto establish direct peering links with Google's edge network at various locations, which enables you\nto direct your traffic from your Virtual Private Cloud (VPC) networks to a provider's network.\n\nCDN Interconnect enables you to optimize your CDN population costs and use\ndirect connectivity to select CDN providers from Google Cloud.\n\nYour network traffic egressing from Google Cloud through one of these links benefits from\nthe direct connectivity to supported CDN providers and is billed automatically with reduced\npricing.\n\n### Setting up CDN Interconnect\n\nIf your CDN provider is already part of the program, you don't have to do anything. Traffic from\nsupported Google Cloud locations to your CDN provider automatically takes advantage of the\ndirect connection and reduced pricing.\n\nWork with your supported CDN provider to learn what locations are supported\nand how to correctly configure your deployment to use intra-region egress routes.\nCDN Interconnect does not require any configuration or integration with\nCloud Load Balancing.\n\nIf your CDN provider is not part of the program, contact your CDN provider\nand ask them to work with Google to get connected.\n\n### Typical use cases for CDN Interconnect\n\n- **High-volume egress traffic.** If you're populating your CDN with large data files from Google Cloud, you can use the CDN Interconnect links between Google Cloud and selected providers to automatically optimize this traffic and save money.\n- **Frequent content updates.** Cloud workloads that frequently update data stored in CDN\n locations benefit from using CDN Interconnect because the direct link to the\n CDN provider reduces latency for these CDN destinations.\n\n For example, if you have frequently updated data served by the CDN originally\n hosted on Google Cloud, you might consider using CDN Interconnect.\n\nPricing\n-------\n\nThe special pricing for your traffic egressing from Google Cloud to a CDN\nprovider is automatic. Google works with approved CDN partners in supported\nlocations to allowlist provider IP addresses. This means that any data\nthat you send to your allowlisted CDN provider from Google Cloud is charged at\nthe reduced price. This reduced price applies only to IPv4 traffic. It does not apply to\nIPv6 traffic.\n\nTraffic between Google Cloud and pre-approved CDN Interconnect\nlocations is billed as follows:\n\n- Ingress traffic is free for all regions.\n- Egress traffic rates apply only to data leaving Compute Engine or Cloud Storage. Egress charges for CDN Interconnect appear on the invoice as *Compute Engine Data Transfer Out via Carrier Peering Network* .\n\n For *inter-region* CDN Interconnect traffic rates, see\n [Internet egress rates](/vpc/network-pricing#internet_egress).\n\n*Intra-region* pricing for CDN Interconnect applies only to intra-region\negress traffic that is sent to\n[Google-approved\nCDN Interconnect providers](/network-connectivity/docs/cdn-interconnect#cdn-interconnect-providers) at specific locations that\nGoogle approves for those providers.\n\nConsult with your CDN provider to verify that they are an approved provider, and\nif so, which of their CDN locations are approved for this program. They can help\nyou set up your deployment to use intra-region egress routes when using\nGoogle Cloud as the origin source.\n\nGoogle-approved service providers\n---------------------------------\n\nReview the list of CDN Interconnect service providers and choose\nthe option that best suits your needs.\n\n*** ** * ** ***\n\n*** ** * ** ***\n\n*** ** * ** ***\n\n*** ** * ** ***"]]
