Cloud CDN relies on the [same CDN edge points of presence that Google
uses](https://peering.google.com/#/infrastructure) to serve
Google's web properties to billions of users. This approach connects individual
points of presence (PoPs) into as many networks as possible, reducing latency
and ensuring that we have capacity for large traffic spikes (for example, for
streaming media or holiday sales). We have an open peering policy with ISPs.
Learn more about our open approach to [peering with ISPs](https://peering.google.com/).

## Points of presence

Cloud CDN operates caches at more than 100 locations across the
following metropolitan areas. Google Cloud also has [interconnect
locations](https://docs.cloud.google.com/network-connectivity/docs/interconnect/concepts/colocation-facilities)
to connect your corporate network to Google Cloud and [network edge
locations](https://docs.cloud.google.com/vpc/docs/edge-locations) to connect to Google Cloud services.
To maximize cache hit ratios and ensure resilient content delivery, Cloud CDN
dynamically pools and distributes caching resources across Google's global edge network.
Google connects its network with other network operators at numerous [edge
PoPs](https://cloud.google.com/about/locations/#network) around the world,
including many of the Cloud CDN sites in the following list.

The set of PoPs in active use can change without notice. Equipment maintenance,
equipment failure, the introduction of new PoPs, the removal of old PoPs, and
other events mean that the following list might not reflect the PoPs that are
in use.

Many of the following cities have multiple PoPs to support service demand or to
peer with different network partners. Cloud CDN caches separately in
each location.


**North America**

- Ashburn, Virginia, US
- Atlanta, Georgia, US
- Charleston, South Carolina, US
- Chicago, Illinois, US
- Columbus, Ohio, US
- Council Bluffs, Iowa, US
- Dallas/Fort Worth, Texas, US
- Denver, Colorado, US
- Las Vegas, Nevada, US
- Lenoir, North Carolina, US
- Los Angeles, California, US
- Miami, Florida, US
- Montréal, Québec, Canada
- New York, New York, US
- Phoenix, Arizona, US
- Querétaro, Mexico
- Reno, California, US
- Salt Lake City, Utah, US
- San Francisco, California, US
- Seattle, Washington, US
- Stevenson, Alabama, US
- The Dalles, Oregon, US
- Toronto, Ontario, Canada
- Tulsa, Oklahoma, US

**South America**

- Bogotá, Colombia
- Buenos Aires, Argentina
- Rio de Janeiro, Brazil
- Santiago, Chile
- São Paulo, Brazil

**Europe**

- Amsterdam, Netherlands
- Berlin, Germany
- Budapest, Hungary
- Den Helder, Netherlands
- Dublin, Ireland
- Frankfurt, Germany
- Groningen, Netherlands
- Hamburg, Germany
- Hamina, Finland
- Helsinki, Finland
- London, England
- Madrid, Spain
- Marseille, France
- Milan, Italy
- Munich, Germany
- Paris, France
- Prague, Czech Republic
- Sofia, Bulgaria
- St. Ghislain, Belgium
- Stockholm, Sweden
- Turin, Italy
- Warsaw, Poland
- Zurich, Switzerland

**Middle East**

- Doha, Qatar
- Fujairah, United Arab Emirates
- Muscat, Oman
- Tel Aviv, Israel

**Asia Pacific**

- Bangkok, Thailand
- Changhua County, Taiwan
- Chennai, India
- Hong Kong SAR, China
- Jakarta, Indonesia
- Kuala Lumpur, Malaysia
- Manila, Philippines
- Mumbai, India
- Delhi, India
- Osaka, Japan
- Seoul, South Korea
- Singapore
- Taipei, Taiwan
- Tokyo, Japan

**Oceania**

- Sydney, Australia
- Melbourne, Australia

**Africa**

- Johannesburg, South Africa
- Lagos, Nigeria
- Mombasa, Kenya

<br />

## What's next

- To enable Cloud CDN for an external Application Load Balancer, see [Setting up Cloud CDN with a managed instance
  group](https://docs.cloud.google.com/cdn/docs/setting-up-cdn-with-mig).
- To learn about the details of caching, see the [Caching overview](https://docs.cloud.google.com/cdn/docs/caching).
- To learn about invalidating cached content, see the [Cache invalidation overview](https://docs.cloud.google.com/cdn/docs/cache-invalidation-overview).