2/24/11 UPDATE:  We're excited to announce a new node in Doha, QT to improve performance for clients on the QTel and affiliated networks.

The most common question we get asked about the Windows Azure Content Delivery Network (CDN) is, "Where are the nodes physically located?"  We're happy to say that customers choosing to serve data through the network today are offered 24 physical nodes* to improve delivery of performance-sensitive content around the globe.  Below is the list of current locations; we'll update this list as our network evolves.

US/EMEA

US

  • Ashburn, VA
  • Bay Area, CA
  • Chicago, IL
  • San Antonio, TX
  • Los Angeles, CA
  • Miami, FL
  • Newark, NJ
  • Seattle, WA

EMEA

  • Amsterdam, NL
  • Doha, QT  NEW
  • Dublin, IE
  • London, GB
  • Moscow, RU
  • Paris, FR
  • Stockholm, SE
  • Vienna, AT
  • Zurich, CH

Asia-Pacific/Rest of World

  • Hong Kong, HK
  • São Paulo, BR
  • Seoul, KR
  • Singapore, SG
  • Sydney, AU
  • Taipei, TW
  • Tokyo, JP

Offering pay-as-you-go, one-click-integration with Windows Azure Storage, the Windows Azure CDN is a system of servers containing copies of data, placed at various points in our global cloud services network to maximize bandwidth for access to data for clients throughout the network. The Windows Azure CDN can only deliver content from public blob containers in Windows Azure Storage - content types can include web objects, downloadable objects (media files, software, documents), applications, real time media streams, and other components of Internet delivery (DNS, routes, and database queries).

For details about pricing for the Windows Azure CDN, read our earlier blog post here.

*A Windows Azure CDN customer's traffic may not be served out of the physically "closest" node; many factors are involved including routing and peering, Internet "weather", and node capacity and availability.  We are continually grooming our network to meet our Service Level Agreements and our customers' requirements.