Cloud CDN 與 Google 使用的 CDN 邊緣 PoP 相同，可為數十億名使用者提供 Google 網頁資源。這種做法會將各個存在點 (PoP) 連接至盡可能多的網路，以減少延遲，並確保我們有足夠的容量來應付大量流量尖峰 (例如串流媒體或節慶銷售活動)。我們與網際網路服務供應商 (ISP) 簽訂開放式對等互連政策。
進一步瞭解我們對與 ISP 對等互連的開放式做法。
服務據點
Cloud CDN 在以下都會區域的 100 多個位置運作快取作業。 Google Cloud 也提供互連位置，可讓企業網路連線至 Google Cloud ，以及網路邊緣位置，可連線至 Google Cloud 服務。Google 會在全球各地的眾多邊緣 PoP 與其他網路業者連線，包括下列清單中的許多 Cloud CDN 網站。
使用中的 POP 組合會隨時變更，恕不另行通知。如果發生設備維護、設備故障、採用新 POP、移除舊 POP 和其他事件，下列清單不一定能反映目前使用中的 POP。
[[["容易理解","easyToUnderstand","thumb-up"],["確實解決了我的問題","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["難以理解","hardToUnderstand","thumb-down"],["資訊或程式碼範例有誤","incorrectInformationOrSampleCode","thumb-down"],["缺少我需要的資訊/範例","missingTheInformationSamplesINeed","thumb-down"],["翻譯問題","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["上次更新時間：2025-08-11 (世界標準時間)。"],[[["\u003cp\u003eCloud CDN uses Google's extensive network of edge points of presence (PoPs), ensuring low latency and the capacity to handle large traffic surges.\u003c/p\u003e\n"],["\u003cp\u003eCloud CDN maintains caches in over 100 metropolitan locations, including multiple PoPs in many cities to support service demand and network partner peering.\u003c/p\u003e\n"],["\u003cp\u003eThe list of active Cloud CDN PoPs is subject to change due to maintenance, equipment changes, and the addition or removal of PoPs.\u003c/p\u003e\n"],["\u003cp\u003eGoogle's network connectivity also includes interconnect locations for corporate network connections and edge locations for accessing Google Cloud services.\u003c/p\u003e\n"],["\u003cp\u003eCloud CDN has an open peering policy with internet service providers (ISPs) to optimize connectivity and performance.\u003c/p\u003e\n"]]],[],null,["# Cache locations\n\nCloud CDN relies on the [same CDN edge points of presence that Google\nuses](https://peering.google.com/#/infrastructure) to serve\nGoogle's web properties to billions of users. This approach connects individual\npoints of presence (PoPs) into as many networks as possible, reducing latency\nand ensuring that we have capacity for large traffic spikes (for example, for\nstreaming media or holiday sales). We have an open peering policy with ISPs.\nLearn more about our open approach to [peering with ISPs](https://peering.google.com/).\n\nPoints of presence\n------------------\n\nCloud CDN operates caches at more than 100 locations across the\nfollowing metropolitan areas. Google Cloud also has [interconnect\nlocations](/network-connectivity/docs/interconnect/concepts/colocation-facilities)\nto connect your corporate network to Google Cloud and [network edge\nlocations](/vpc/docs/edge-locations) to connect to Google Cloud services.\nGoogle connects its network with other network operators at numerous [edge\nPoPs](/about/locations#network) around the world, including many of the\nCloud CDN sites in the following list.\n\nThe set of PoPs in active use can change without notice. Equipment maintenance,\nequipment failure, the introduction of new PoPs, the removal of old PoPs, and\nother events mean that the following list might not reflect the PoPs that are\nin use.\n\nMany of the following cities have multiple PoPs to support service demand or to\npeer with different network partners. Cloud CDN caches separately in\neach location.\n\n\n**North America**\n\n- Ashburn, Virginia, US\n- Atlanta, Georgia, US\n- Charleston, South Carolina, US\n- Chicago, Illinois, US\n- Columbus, Ohio, US\n- Council Bluffs, Iowa, US\n- Dallas/Fort Worth, Texas, US\n- Denver, Colorado, US\n- Las Vegas, Nevada, US\n- Lenoir, North Carolina, US\n- Los Angeles, California, US\n- Miami, Florida, US\n- Montréal, Québec, Canada\n- New York, New York, US\n- Phoenix, Arizona, US\n- Querétaro, Mexico\n- Reno, California, US\n- Salt Lake City, Utah, US\n- San Francisco, California, US\n- Seattle, Washington, US\n- Stevenson, Alabama, US\n- The Dalles, Oregon, US\n- Toronto, Ontario, Canada\n- Tulsa, Oklahoma, US\n\n**South America**\n\n- Bogotá, Colombia\n- Buenos Aires, Argentina\n- Rio de Janeiro, Brazil\n- Santiago, Chile\n- São Paulo, Brazil\n\n**Europe**\n\n- Amsterdam, Netherlands\n- Berlin, Germany\n- Budapest, Hungary\n- Den Helder, Netherlands\n- Dublin, Ireland\n- Frankfurt, Germany\n- Groningen, Netherlands\n- Hamburg, Germany\n- Hamina, Finland\n- Helsinki, Finland\n- London, England\n- Madrid, Spain\n- Marseille, France\n- Milan, Italy\n- Munich, Germany\n- Paris, France\n- Prague, Czech Republic\n- Sofia, Bulgaria\n- St. Ghislain, Belgium\n- Stockholm, Sweden\n- Turin, Italy\n- Warsaw, Poland\n- Zurich, Switzerland\n\n**Middle East**\n\n- Doha, Qatar\n- Fujairah, United Arab Emirates\n- Muscat, Oman\n- Tel Aviv, Israel\n\n**Asia Pacific**\n\n- Bangkok, Thailand\n- Changhua County, Taiwan\n- Chennai, India\n- Hong Kong SAR, China\n- Jakarta, Indonesia\n- Kuala Lumpur, Malaysia\n- Manila, Philippines\n- Mumbai, India\n- Delhi, India\n- Osaka, Japan\n- Seoul, South Korea\n- Singapore\n- Taipei, Taiwan\n- Tokyo, Japan\n\n**Oceania**\n\n- Sydney, Australia\n- Melbourne, Australia\n\n**Africa**\n\n- Johannesburg, South Africa\n- Lagos, Nigeria\n- Mombasa, Kenya\n\n\u003cbr /\u003e\n\nWhat's next\n-----------\n\n- To enable Cloud CDN for an external Application Load Balancer, see [Setting up Cloud CDN with a managed instance\n group](/cdn/docs/setting-up-cdn-with-mig).\n- To learn about the details of caching, see the [Caching overview](/cdn/docs/caching).\n- To learn about invalidating cached content, see the [Cache invalidation overview](/cdn/docs/cache-invalidation-overview)."]]
