View source for Google data centers

{{short description|Facilities containing Google servers}}
{{Use American English|date=July 2021}}
{{Use mdy dates|date=July 2021}}
[[File:Google datacenter (2007) - panoramio - erwinboogert (2).jpg|thumb|Former Google data center in [[Eemshaven]], Netherlands]]
{{external media
| float  = right
| caption = YouTube <!-- text placed left or right of headerimage --->
| headerimage= [[File:YouTube 2024.svg|alt=YouTube logo|x20px|left]]
| video1 = [https://www.youtube.com/watch?v=zDAYZU4A3w0&t=17s Google Data Center 360° Tour]
}}

'''Google data centers''' are the large [[data center]] facilities [[Google]] uses to provide [[List of Google products|their services]], which combine large drives, computer nodes organized in aisles of racks, internal and external networking, environmental controls (mainly cooling and humidification control), and operations software (especially as concerns [[load balancing (computing)|load balancing]] and [[fault tolerance]]).

There is no official data on how many [[Server (computing)|servers]] are in Google data centers, but [[Gartner]] estimated in a July 2016 report that Google at the time had 2.5 million servers. This number is changing as the company expands capacity and refreshes its hardware.<ref>{{cite web |title=How Many Servers Does Google Have? |url=https://www.datacenterknowledge.com/archives/2017/03/16/google-data-center-faq |website=Data Center Knowledge |date=March 16, 2017 |access-date=September 20, 2018}}</ref>

== Locations ==
The locations of Google's various data centers by continent are as follows:<ref name="google">{{cite web|url=https://about.google/locations/?region=north-america&office=mountain-view|title=Google data centers, locations|access-date=July 21, 2014}}</ref><ref>{{Cite web |title=ISO/IEC 27001 - Compliance |url=https://cloud.google.com/security/compliance/iso-27001 |access-date=2023-07-11 |website=Google Cloud |language=en}}</ref>
{| class="wikitable sortable"
|+
!Continent
!Location
!Geo
!Products Location
!Cloud Location
!Timeline
!Description
|-
|North America
|[[Arcola, Virginia|Arcola (VA), USA]]
|{{coord|38|56|35.99|N|77|31|27.61|W|scale:5000_region:US}}
|[https://www.google.com/about/datacenters/locations/loudoun-county/ Loudoun County]
|N. Virginia (us-east4)
|2017 - announced<ref name=":1">{{Cite web |last=Report |first=Times-Mirror Staff |title=Google 'caps off' $600M investment in Loudoun County |url=https://www.loudountimes.com/business/google-caps-off-600m-investment-in-loudoun-county/article_6a4a3110-9291-11e9-a5f5-673864320f20.html |access-date=February 12, 2021 |website=LoudounTimes.com |date=June 19, 2019 |language=en}}</ref><ref name=":2">{{cite web |title=Google Plans 2 Loudoun Data Centers |url=https://www.loudounnow.com/business/google-plans-2-loudoun-data-centers/article_db81d1e4-775c-5896-a381-6e4c282e64c8.html |access-date=12 April 2023 |website=LoudounNow.com |date=November 29, 2017 |language=en}}</ref>
|
|-
|North America
|[[Atlanta|Atlanta (GA), USA]]
|{{coord|33|44|59.04|N|84|35|5.33|W|scale:5000_region:US}}
|[https://www.google.com/about/datacenters/locations/douglas-county/ Douglas County]
| -
|2003 - launched
|350 employees
|-
|South America
|[[Cerrillos, Chile|Cerrillos, Santiago, Chile]]
|{{Coord|-33.520515|-70.721695|format=dms}}<ref>{{Cite web |last=Arellano (CIPER) |first=Alberto |date=2020-05-25 |title=Las zonas oscuras de la evaluación ambiental que autorizó "a ciegas" el megaproyecto de Google en Cerrillos |url=https://www.ciperchile.cl/2020/05/25/las-zonas-oscuras-de-la-evaluacion-ambiental-que-autorizo-a-ciegas-el-megaproyecto-de-google-en-cerrillos/ |access-date=2023-07-10 |website=CIPER Chile |language=es}}</ref>
| -
|Santiago (southamerica-west1)
|2020 - announced<ref>{{cite web |title=Google instalará un nuevo data center en Chile |url=http://www.diarioeldia.cl/tendencias/google-instalara-nuevo-data-center-en-chile |url-status=dead |archive-url=https://web.archive.org/web/20210922081126/http://www.diarioeldia.cl/tendencias/google-instalara-nuevo-data-center-en-chile |archive-date=September 22, 2021 |access-date=September 28, 2019 |website=diarioeldia.cl |language=es}}</ref>
2021 - launched<ref>{{Cite web |date=2021-12-01 |title=Una nueva Región de Google Cloud en Santiago, todo el potencial de la nube ahora más cerca |url=https://blog.google/intl/es-419/actualizaciones-de-producto/en-la-nube/santiago-cloud-region-opening/ |access-date=2023-07-10 |website=Google}}</ref>
|
|-
|Asia
|[[Changhua County|Changhua County, Taiwan]]
|{{coord|24|08|18.6|N|120|25|32.6|E|scale:5000}}
|[https://www.google.com/about/datacenters/locations/changhua-county/ Changhua County]
|Taiwan

(asia-east1)
|2011 - announced
2013 - launched
|60 employees
|-
|North America
|[[Clarksville, Tennessee|Clarksville (TN), USA]]
|{{Coord|36.6211599|-87.2630735|format=dms}}
|[https://www.google.com/about/datacenters/locations/montgomery-county/ Montgomery County]
| -
|2015 - announced
|
|-
|North America
|[[Columbus, Ohio|Columbus (OH), USA]]
|
| -
|Columbus (us-east5)
|2022 - launched<ref>{{Cite web |title=A Google Cloud region now available in Columbus, Ohio |url=https://cloud.google.com/blog/products/infrastructure/new-google-cloud-region-in-columbus-ohio-is-open |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|North America
|[[Council Bluffs, Iowa|Council Bluffs (IA), USA]]
|{{Coord|41|13|17.7|N|95|51|49.92|W|scale:5000_region:US}}
|[https://www.google.com/about/datacenters/locations/council-bluffs/ Council Bluffs]
|
|2007 - announced

2009 - completed first phase completed

2012 and 2015 - expanded
|130 employees
|-
|North America
|[[Council Bluffs, Iowa|Council Bluffs (IA), USA]]
|{{Coord|41.1682533|-95.7961246|format=dms}}
|
|Iowa (us-central1)
|
|
|-
|Asia
|[[Delhi|Delhi, India]]
|
| -
|Delhi (asia-south2)
|2020 - announced
2021 - launched<ref>{{Cite web |title=Namaste, India. Our new cloud region in Delhi NCR is now live. |url=https://cloudonair.withgoogle.com/events/india-region-launch |website=cloudonair.withgoogle.com}}</ref>
|
|-
|Middle East
|[[Doha|Doha, Qatar]]
|
| -
|Doha (me-central1)
|2023 - launched<ref>{{Cite web |title=New Google Cloud region now open in Qatar |url=https://cloud.google.com/blog/products/infrastructure/new-google-cloud-region-now-open-in-qatar |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Europe
|[[Dublin, Ireland]]
|{{coord|53|19|12.39|N|6|26|31.43|W|scale:5000}}
|[https://www.google.com/about/datacenters/locations/dublin/ Dublin]
| -
|2011 - announced
2012 - launched
|150 employees<ref>{{Cite web |title=Dublin, Ireland – Data Centers – Google |url=https://www.google.com/about/datacenters/inside/locations/dublin/working-here.html |access-date=April 2, 2019 |website=www.google.com}}</ref>
|-
|Europe
|[[Eemshaven|Eemshaven, Netherlands]]
|{{Coord|53.4252171|6.8622574}}
|[https://www.google.com/about/datacenters/locations/eemshaven/ Eemshaven]
|Netherlands (europe-west4)
|2014 - announced
2016 - launched

2018, 2019 - expansion
|200 employees
|-
|Europe
|[[Frankfurt|Frankfurt, Germany]]
|{{Coord|50.1226299|8.9741678|format=dms}}<ref>{{Cite web |title=PROJEKT IN HANAU: RECHENZENTRUM FÜR GOOGLE ENTWICKELT |url=https://www.ndc-garbe.com/de/projekt-in-hanau-rechenzentrum-fuer-google-entwickelt/ |website=NDC-GARBE|date=September 2, 2021 }}</ref>
| -
|Frankfurt (europe-west3)
|2022 - expanded<ref>{{Cite web |title=Google Cloud investing in Germany with new infrastructure and sustainable energy |url=https://cloud.google.com/blog/products/infrastructure/google-invests-1-billion-euros-in-germanys-digital-future |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Europe
|[[Fredericia|Fredericia, Denmark]]
|{{coord|55|33|29.5|N|9|39|20.8|E|scale:5000}}
|[https://www.google.com/about/datacenters/locations/fredericia/ Fredericia]
| -
|2018 - announced<ref>{{Cite web |date=2018-11-20 |title=Breaking ground for Google's first data center in Denmark |url=https://blog.google/inside-google/infrastructure/breaking-ground-googles-first-data-center-denmark/ |access-date=2023-07-10 |website=Google |language=en-us}}</ref>
2020 - launched
|€600M building costs
|-
|Europe
|[[Ghlin|Ghlin, Hainaut, Belgium]]
|{{coord|50|28|09.6|N|3|51|55.7|E|scale:5000}}
|[https://www.google.com/about/datacenters/locations/st-ghislain/ Saint-Ghislain]
|Belgium (europe-west1)
|2007 - announced
2010 - launched
|12 employees
|-
|Europe
|[[Hamina|Hamina, Finland]]
|{{coord|60|32|11.68|N|27|7|1.21|E|scale:10000}}
|[https://www.google.com/about/datacenters/locations/hamina/ Hamina]
|Finland

(europe-north1)
|2009 - announced
2011 - first phase completed

2022 - expansion
|6 buildings, 400 employees <ref>{{cite web |date=September 11, 2020 |title=Google gets green light for its sixth data center in Hamina, Finland |url=https://www.fiercetelecom.com/telecom/google-gets-green-light-for-sixth-data-center-hamina-finland}}</ref>
|-
|North America
|[[Henderson, Nevada|Henderson (NV), USA]]
|{{Coord|36.0556248|-115.0102258|format=dms}}
|[https://www.google.com/about/datacenters/locations/henderson/ Henderson]
|Las Vegas (us-west4)
|2019 - announced<ref>{{Cite web |title=Investing in Google infrastructure, investing in Nevada. |url=https://cloud.google.com/blog/products/infrastructure/investing-in-google-infrastructure-investing-in-nevada |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>

2020 - launched
|64-acres; $1.2B building costs<ref>{{Cite web |last=Torres-Cortez |first=Ricardo |date=September 16, 2020 |title=Google to invest additional $600M at Henderson data center – Las Vegas Sun Newspaper |url=https://lasvegassun.com/news/2020/sep/16/google-to-invest-additional-600m-at-henderson-data/ |archive-url= |archive-date= |access-date=February 12, 2021 |website=lasvegassun.com |language=en |quote="With this latest announcement, Google will bring their total investment in the city of Henderson to $1.2 billion," said Mayor Debra March in the release}}</ref><ref>{{Cite web |last=Baxtel |title=Google Henderson NV Data Center |url=https://baxtel.com/data-center/google-henderson-nv |access-date=February 12, 2021 |website=baxtel.com |language=en}}</ref>
|-
|Asia
|[[Hong Kong|Hong Kong, Hong Kong]]
|
| -
|Hong Kong (asia-east2)
|2017 - announced<ref>{{Cite web |title=Coming soon: GCP's Hong Kong region |url=https://cloud.google.com/blog/products/gcp/coming-in-2018-gcps-hong-kong-region |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
2018 - launched<ref>{{Cite web |title=Growing our presence in Asia Pacific: New GCP regions in Hong Kong and Jakarta |url=https://cloud.google.com/blog/products/gcp/gcps-region-in-hong-kong-is-now-open |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Asia
|[[Inzai|Inzai, Japan]]
|{{Coord|35.8177804|140.1323916|format=dms}}
|[https://www.google.com/about/datacenters/locations/inzai-japan/ Inzai]
| -
|2023 - launched
|
|-
|Asia
|[[Jakarta|Jakarta, Indonesia]]
|
| -
|Jakarta (asia-southeast2)
|2020 - launched<ref>{{Cite web |title=The new Google Cloud region in Jakarta is now open |url=https://cloud.google.com/blog/products/infrastructure/new-google-cloud-region-in-jakarta-now-open/ |access-date=2021-09-15 |website=Google Cloud Blog |language=en}}</ref>
|
|-
|Asia
|[[Kōtō|Koto-Ku, Tokyo, Japan]]
|
| -
|Tokyo

(asia-northeast1)
|2016 - launched<ref>{{Cite web |title=Google Cloud Platform Tokyo region now open for business |url=https://cloud.google.com/blog/topics/inside-google-cloud/google-cloud-platform-tokyo-region-now-open-for-business |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|North America
|[[Leesburg, Virginia|Leesburg (VA), USA]]
|{{coord|39|3|6.38|N|77|32|20.38|W|scale:5000_region:US}}
|[https://www.google.com/about/datacenters/locations/loudoun-county/ Loudoun County]
|N. Virginia (us-east4)
|2017 - announced<ref name=":1" /><ref name=":2" />
|
|-
|North America
|[[Lenoir, North Carolina|Lenoir (NC), USA]]
|{{coord|35|53|54.78|N|81|32|50.58|W|scale:5000_region:US}}
|[https://www.google.com/about/datacenters/locations/lenoir/ Lenoir]
| -
|2007 - announced

2009 - launched
|over 110 employees
|-
|Asia
|Lok Yang Way, [[Pioneer, Singapore]]
|{{Coord|1.3239859|103.693253|format=dms}}<ref>{{Cite web |title=Google - Singapore |url=https://www.streetdirectory.com/asia_travel/search/?q=Google&country=singapore&state=0 |access-date=2023-07-11 |website=www.streetdirectory.com}}</ref>
|[https://www.google.com/about/datacenters/locations/singapore/ Singapore]
|Singapore (asia-southeast1)
|2022 - launched
|
|-
|Europe
|[[London|London, UK]]
|
| -
|London

(europe-west2)
|2017 - launched<ref>{{Cite web |title=Google Cloud Platform now open in London |url=https://cloud.google.com/blog/products/gcp/google-cloud-platform-now-open-in-london |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|North America
|[[Los Angeles|Los Angeles (CA), USA]]
|
| -
|Los Angeles (us-west2)
|
|
|-
|Europe
|[[Madrid|Madrid, Spain]]
|{{Coord|40.5195333|-3.3409366|format=dms}}
| -
|Madrid (europe-southwest1)
|2022 - launched<ref>{{Cite web |title=New Google Cloud region in Madrid, Spain now open |url=https://cloud.google.com/blog/products/infrastructure/new-google-cloud-region-in-madrid-spain-now-open |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Pacific
|[[Melbourne|Melbourne, Australia]]
|
| -
|Melbourne

(australia-southeast2)
|2021 - launched<ref>{{Cite web |title=The Google Cloud region in Melbourne is now open |url=https://cloud.google.com/blog/products/infrastructure/the-google-cloud-region-in-melbourne-is-now-open |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Europe
|[[Middenmeer|Middenmeer, Noord-Holland, The Netherlands]]
|{{Coord|52.7901053|5.0292193|format=dms}}<ref>{{Cite web |title=Welcome |url=https://www.agriporta7.nl/ |access-date=2023-07-10 |website=Agriport A7 |language=nl-NL}}</ref>
|[https://www.google.com/about/datacenters/locations/middenmeer/ Middenmeer]
|Netherlands (europe-west4)
|2019 - announced<ref>{{Cite web |date=June 24, 2019 |title=Google to Spend $1.1 Billion on New Data Centers in Netherlands |url=https://www.bloomberg.com/news/articles/2019-06-24/google-to-spend-1-1-billion-on-new-data-centers-in-netherlands |website=Data Center Knowledge}}</ref>
|
|-
|North America
|[[Midlothian, Texas|Midlothian (TX), USA]]
|{{Coord|32.443170|-97.062324|format=dms}}
|[https://www.google.com/about/datacenters/locations/midlothian/ Midlothian]
|Dallas (us-south1)
|2019 - announced
2022 - launched<ref>{{Cite web |title=A Google Cloud region now available in Dallas, Texas |url=https://cloud.google.com/blog/products/infrastructure/a-google-cloud-region-now-available-in-dallas-texas |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|375-acres; $600M building costs<ref>{{Cite web |date=June 14, 2019 |title=Google's massive $600M data center takes shape in Ellis County as tech giant ups Texas presence |url=https://www.dallasnews.com/business/real-estate/2019/06/14/google-s-massive-600m-data-center-takes-shape-in-ellis-county-as-tech-giant-ups-texas-presence/ |access-date=February 12, 2021 |website=Dallas News |language=en}}</ref>
|-
|Europe
|[[Milan|Milan, Italy]]
|
| -
|Milan (europe-west8)
|2022 - launched<ref>{{Cite web |title=New Google Cloud region in Milan, Italy now open |url=https://cloud.google.com/blog/products/infrastructure/new-google-cloud-region-in-milan-italy-now-open |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|North America
|[[Moncks Corner, South Carolina|Moncks Corner (SC), USA]]
|{{Coord|33|03|50.8|N|80|02|36.1|W|scale:5000_region:US}}
|[https://www.google.com/about/datacenters/locations/berkeley-county/ Berkeley County]
|South Carolina (us-east1)
|2007 - launched

2013 - expanded
|150 employees
|-
|North America
|[[Montreal|Montreal, Quebec, Canada]]<ref>{{Cite web |title=Project to expand Google's activities in Quebec - Future computer data center in Beauharnois |url=https://www.quebec.ca/nouvelles/actualites/details/projet-dexpansion-des-activites-de-google-au-quebec-futur-centre-de-donnees-informatiques-a-beauharnois-31234 |access-date=May 10, 2021 |website=www.quebec.ca |language=fr}}</ref>
|
| -
|Montréal (northamerica-northeast1)
|2018 - launched<ref>{{Cite web |title=GCP arrives in Canada with launch of Montréal region |url=https://cloud.google.com/blog/products/gcp/gcp-arrives-in-canada-with-launch-of-montreal-region |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|62.4-hectares; $600M building costs<ref>{{Cite web |title=Google's ongoing commitment in Quebec |url=https://blog.google/intl/en-ca/company-news/inside-google/googles-ongoing-commitment-to-quebec/ |access-date=February 12, 2021 |website=Google Blog - Company News |language=en}}</ref>
|-
|Asia
|[[Mumbai|Mumbai, India]]
|
| -
|Mumbai (asia-south1)
|2017 - launched<ref>{{Cite web |last=Stiver |first=Dave |date=November 1, 2017 |title=GCP arrives in India with launch of Mumbai region |url=https://cloud.google.com/blog/products/gcp/gcp-arrives-in-india-with-launch-of-mumbai-region/ |access-date=July 30, 2019 |website=Google Cloud Blog |language=en}}</ref>
|
|-
|North America
|[[New Albany, Ohio|New Albany (OH), USA]]
|{{Coord|40.0613352|-82.7586278|format=dms}}
|[https://www.google.com/about/datacenters/locations/new-albany/ New Albany]
| -
|2019 - announced
|400-acres; $600M building costs<ref>{{Cite web |last=Williams |first=Mark |title=Google joins New Albany high-tech crowd with $600 million data center |url=https://www.dispatch.com/business/20191103/google-joins-new-albany-high-tech-crowd-with-600-million-data-center |access-date=February 12, 2021 |website=The Columbus Dispatch |language=en |archive-date=December 30, 2020 |archive-url=https://web.archive.org/web/20201230214959/https://www.dispatch.com/business/20191103/google-joins-new-albany-high-tech-crowd-with-600-million-data-center |url-status=dead }}</ref><ref>{{Cite web |title=New Albany, Ohio – Data Centers – Google |url=https://www.google.com/about/datacenters/locations/new-albany/ |access-date=February 12, 2021 |website=Google Data Centers |language=en}}</ref>
|-
|Asia
|[[Osaka|Osaka, Japan]]
|
| -
|Osaka

(asia-northeast2)
|2019 - launched<ref>{{Cite web |title=Google Cloud launches new Osaka region to support growing customer base in Japan |url=https://cloud.google.com/blog/products/infrastructure/google-cloud-launches-new-osaka-region-to-support-growing-customer-base-in-japan |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|South America
|[[Osasco|Osasco, São Paulo, Brazil]]
|
| -
|São Paulo (southamerica-east1)
|2017 - launched<ref>{{Cite web |title=GCP arrives in South America with launch of São Paulo region! |url=https://cloud.google.com/blog/products/gcp/gcp-arrives-in-south-america-with-launch-of-sao-paulo-region |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|North America
|[[Papillion, Nebraska|Papillion (NE), USA]]
|{{Coord|41.1332915|-96.144178|format=dms}}
|[https://www.google.com/about/datacenters/locations/papillion/ Papillion]
| -
|2019 - announced
|275-acres; $600M building costs<ref>{{Cite web |title=Google confirms it is behind $600m Papillion data center project |url=https://www.datacenterdynamics.com/en/news/google-confirms-it-behind-600m-papillion-data-center-project/ |access-date=February 12, 2021 |website=www.datacenterdynamics.com |date=October 4, 2019 |language=en}}</ref><ref>{{Cite web |title=Papillion, Nebraska – Data Centers – Google |url=https://www.google.com/about/datacenters/locations/papillion/ |access-date=February 12, 2021 |website=Google Data Centers |language=en}}</ref>
|-
|Europe
|[[Paris|Paris, France]]
|
| -
|Paris (europe-west9)
|2022 - launched<ref>{{Cite web |title=Google Cloud region in Paris France now open |url=https://cloud.google.com/blog/products/infrastructure/google-cloud-region-in-paris-france-now-open |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|North America
|[[Pryor Creek, Oklahoma|Pryor Creek (OK), USA]]
|{{coord|36|14|28.1|N|95|19|48.22|W|scale:5000}}
|[https://www.google.com/about/datacenters/locations/mayes-county/ Mayes County]
| -
|2007 - announced

2012 - expanded 
|over 400 employees,<ref>{{Cite web |last=Dawn-Hiscox |first=Tanwen |date=February 20, 2018 |title=Google to spend m on Pryor data center expansion |url=https://www.datacenterdynamics.com/news/google-to-spend-600m-on-pryor-data-center-expansion/ |url-status=live |archive-url=https://web.archive.org/web/20190423135640/https://www.datacenterdynamics.com/news/google-to-spend-600m-on-pryor-data-center-expansion/ |archive-date=April 23, 2019 |access-date=April 23, 2019 |website=Data Centre Dynamics}}</ref> land at [[MidAmerica Industrial Park]] 
|-
|South America
|[[Quilicura|Quilicura, Santiago, Chile]]
|{{coord|33|21|30.5|S|70|41|50.4|W|scale:5000}}
|[https://www.google.com/about/datacenters/locations/quilicura/ Quilicura]
| -
|2012 - announced
2015 - launched
|up to 20 employees expected. A million dollar investment plan to increase capacity at Quilicura was announced in 2018.<ref>{{cite web |date=September 28, 2018 |title=Google ha decido de invertir millones de dólares en su centro de datos en Chile |url=http://newtechmag.net/2018/09/28/google-ha-decidido-invertir-140-millones-de-dolares-en-su-centro-de-datos-de-chile/ |url-status=dead |archive-url=https://web.archive.org/web/20190330032359/http://newtechmag.net/2018/09/28/google-ha-decidido-invertir-140-millones-de-dolares-en-su-centro-de-datos-de-chile/ |archive-date=March 30, 2019 |access-date=December 8, 2018 |website=Newtechmag.net |language=es}}</ref>
|-
|North America
|[[Reno metropolitan area, Nevada|Reno (NV), USA]]
|{{Coord|39.5011558|-119.4295537|format=dms}}
|[https://www.google.com/about/datacenters/locations/storey-county/ Storey County]
| -
|2017 - 1,210 acres of land bought in the [[Tahoe Reno Industrial Center]]<ref>{{cite web |author=Tanwen Dawn-Hiscox |date=April 18, 2017 |title=Google is planning a massive data center in Nevada |url=https://www.datacenterdynamics.com/news/google-is-planning-a-massive-data-center-in-nevada/ |access-date=December 8, 2018 |website=Datacenterdynamics.com}}</ref>

2018 - announced

2018 November - project approved by the state of Nevada<ref>{{cite web |author=Jason Hidalgo |date=November 16, 2018 |title=Nevada approves Google's M data center near Las Vegas, M in tax incentives |url=https://eu.rgj.com/story/money/business/2018/11/16/nevada-approves-google-application-600-million-data-center-near-vegas/2026903002/ |access-date=December 8, 2018 |website=Rgj.com}}</ref><ref>{{cite web |author=Jason Hidalgo |date=September 16, 2020 |title=Google to invest $600 million in data center near Reno, gets tax break |url=https://www.datacenterdynamics.com/en/news/google-is-planning-a-massive-data-center-in-nevada/ |access-date=October 26, 2020 |website=Reno Gazette Journal |quote="With our new data center in Storey County and our expanded investment in our Henderson site, Google will have two facilities in Nevada, bringing our total investment to over $1.88 billion."}}</ref>
|
|-
|North America
|[[Salt Lake City, Utah|Salt Lake City (UT), USA]]
|
| -
|Salt Lake City (us-west3)
|2020 - launched<ref>{{Cite web |title=Google Cloud region in Salt Lake City now open |url=https://cloud.google.com/blog/products/infrastructure/google-cloud-region-in-salt-lake-city-now-open |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Asia
|[[Seoul|Seoul, South Korea]]
|
| -
|Seoul

(asia-northeast3)
|2020 - launched<ref>{{Cite web |title=New GCP Region in Seoul |url=https://cloud.google.com/blog/products/infrastructure/new-gcp-region-in-seoul |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Pacific
|[[Sydney|Sydney, Australia]]
|
| -
|Sydney

(australia-southeast1)
|2017 - launched<ref>{{Cite web |title=Google Cloud expands to Australia with new Sydney region |url=https://cloud.google.com/blog/products/gcp/google-cloud-region-in-sydney |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Middle East
|[[Tel Aviv|Tel Aviv, Israel]]<ref>{{Cite web |title=Google launches GCP region in Tel Aviv, Israel |url=https://www.datacenterdynamics.com/en/news/google-launches-gcp-region-in-tel-aviv-israel/ |website=datacenterdynamics.com|date=October 19, 2022 }}</ref>
|
| -
|Tel Aviv (me-west1)
|2022 - launched<ref>{{Cite web |title=Google Cloud region in Tel Aviv Israel now open |url=https://cloud.google.com/blog/products/infrastructure/new-google-cloud-region-in-israel-is-now-open |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|North America
|[[The Dalles, Oregon|The Dalles (OR), USA]]
|{{coord|45|37|57.04|N|121|12|8.16|W|scale:5000_region:US}}
|[https://www.google.com/about/datacenters/locations/the-dalles/ The Dalles]
|Oregon (us-west1)
|2006 - launched
|80 full-time employees
|-
|North America
|[[Toronto|Toronto, Canada]]
|
| -
|Toronto (northamerica-northeast2)
|2021 - launched<ref>{{Cite web |title=Google Cloud Toronto region now open |url=https://cloud.google.com/blog/products/infrastructure/google-cloud-toronto-region-now-open |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Europe
|[[Turin|Turin, Italy]]
|{{Coord|45.146729|7.742147|format=dms}}
| -
|Turin (europe-west12)
|2023 - launched<ref>{{Cite web |title=New Google Cloud region in Turin, Italy now open |url=https://cloud.google.com/blog/products/infrastructure/new-google-cloud-region-in-turin-italy-now-open |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|South America
|[[Vinhedo|Vinhedo, São Paulo, Brazil]]
|
|
|São Paulo (southamerica-east1)
|
|
|-
|Europe
|[[Warsaw|Warsaw, Poland]]
|
| -
|Warsaw (europe-central2)
|2019 - announced
2021 - launched<ref>{{Cite web |date=September 27, 2019 |title=Google to Build Cloud Data Centers in Poland |url=https://www.datacenterknowledge.com/google-alphabet/google-build-cloud-data-centers-poland |website=Data Center Knowledge}}</ref>
|
|-
|Asia
|[[Wenya|Wenya, Jurong West, Singapore]]
|{{coord|1|21|04.8|N|103|42|35.2|E|scale:5000}}
|[https://www.google.com/about/datacenters/locations/singapore/ Singapore]
|Singapore (asia-southeast1)
|2011 - announced
2013 - launched

2015 - expanded
|
|-
|North America
|[[Bridgeport, Alabama|Widows Creek (Bridgeport) (AL), USA]]
|{{coord|34|54|48.4|N|85|44|53.1|W|scale:5000_region:US}}<ref>{{Cite web |title=Google kicks off construction on M Alabama data center |url=http://www.madeinalabama.com/2018/04/google-kicks-off-construction-on-alabama-data-center/ |access-date=August 19, 2019 |website=Made in Alabama |date=April 9, 2018 |language=en}}</ref> 
|[https://www.google.com/about/datacenters/locations/jackson-county/ Jackson County]
| -
|2018 - broke ground
|
|-
|Europe
|[[Zürich|Zürich, Switzerland]]
|{{Coord|47.4459257|8.2109085|format=dms}}<ref>{{Cite web |title=Die Schweizer Google Cloud Platform zieht zu Green in den Aargau |url=https://www.itmagazine.ch/artikel/68008/Die_Schweizer_Google_Cloud_Platform_zieht_zu_Green_in_den_Aargau.html |access-date=2023-07-10 |website=Swiss IT Magazine |language=de}}</ref>
| -
|Zurich (europe-west6)
|2018 - announced
2019 - launched<ref><<Cite web|url=https://www.datacenterknowledge.com/google-alphabet/google-building-cloud-data-centers-close-swiss-banks|title=Google{{dead link|date=June 2021 |bot=InternetArchiveBot |fix-attempted=yes }} Building Cloud Data Centers Close to Swiss Banks||</ref>
|
|-
|Europe
|[[Austria]]
|
|
|
|2022 - announced<ref name=":3">{{Cite web |title=Introducing 5 new Google Cloud regions |url=https://cloud.google.com/blog/products/infrastructure/introducing-new-google-cloud-regions |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Europe
|[[Berlin|Berlin, Germany]]<ref>{{Cite news |date=2022-09-30 |title=Google plant ein großes Rechenzentrum südlich des Flughafens BER |language=de |work=Der Spiegel |url=https://www.spiegel.de/netzwelt/web/google-plant-ein-grosses-rechenzentrum-suedlich-des-flughafens-ber-a-00f47a15-0c78-4c82-a42f-2524f0dc42ee |access-date=2023-07-10 |issn=2195-1349}}</ref>
|
|
|Berlin (europe-west10)
|2021 - announced<ref>{{Cite web |title=Google Cloud investing in Germany with new infrastructure and sustainable energy |url=https://cloud.google.com/blog/products/infrastructure/google-invests-1-billion-euros-in-germanys-digital-future |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref> 2023 August - launched <ref>{{Cite web |title=Berlin-Brandenburg Google Cloud region is now open |url=https://cloud.google.com/blog/products/infrastructure/berlin-brandenburg-google-cloud-region-is-now-open |access-date=2024-02-03 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Middle East
|[[Dammam|Dammam, Saudi Arabia]]
|
|
|
|2021 - announced<ref>{{Cite web |title=Google Cloud Platform region updates |url=https://cloud.google.com/blog/products/infrastructure/google-cloud-platform-region-updates |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Europe
|[[Athens|Athens, Greece]]
|
|
|
|2022 - announced<ref name=":3" />
|
|-
|North America
|[[Kansas City, Missouri]]
|
|
|
|2019 - announced<ref>{{Cite web |title=Google affiliate's latest move signals selection of KC for $600M data center |url=https://www.bizjournals.com/kansascity/news/2019/08/28/google-data-center-deed-executed-for-kcmo-land.html |access-date=February 12, 2021 |website=www.bizjournals.com}}</ref>
|
|-
|Middle East
|[[Kuwait]]
|
|
|
|2023 - announced<ref>{{Cite web |title=Bringing a new Google Cloud region to Kuwait |url=https://cloud.google.com/blog/products/infrastructure/bringing-a-new-google-cloud-region-to-kuwait |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Asia
|[[Malaysia]]
|
|
|
|2022 - announced<ref name=":0">{{Cite web |title=Announcing new Google Cloud regions in Asia Pacific |url=https://cloud.google.com/blog/products/infrastructure/announcing-new-google-cloud-regions-in-asia-pacific |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Pacific
|[[Auckland, New Zealand]]
|
|
|
|2022 - announced<ref name=":0" />
|
|-
|Europe
|[[Oslo|Oslo, Norway]]
|
|
|
|2022 - announced<ref name=":3" />
|
|-
|North America
|[[Querétaro|Querétaro, Mexico]]
|
|
|
|2022 - announced<ref>{{Cite web |title=Announcing a new Google Cloud region in Mexico |url=https://cloud.google.com/blog/products/infrastructure/announcing-a-new-google-cloud-region-in-mexico |access-date=2023-07-10 |website=Google Cloud Blog |language=en-US}}</ref>
|
|-
|Africa
|[[Johannesburg, South Africa]]
|
|
|Johannesburg (africa-south1)
|2022 - announced<ref name=":3" />2024 - launched
|
|-
|Europe
|[[Sweden]]
|
|
|
|2022 - announced<ref name=":3" />
|
|-
|Asia
|[[Tainan City|Tainan City, Taiwan]]
|
| -
|Taiwan

(asia-east1)
|2019 September - announced<ref name="Taipei Times 2019">{{cite web |date=September 12, 2019 |title=Google purchases land for new data center in Tainan |url=http://www.taipeitimes.com/News/biz/archives/2019/09/12/2003722106 |access-date=December 20, 2019 |website=Taipei Times}}</ref><ref name="Focus Taiwan 2019">{{cite web |date=September 11, 2019 |title=Google to set up data center in Tainan |url=http://m.focustaiwan.tw/news/ast/201909110016.aspx |access-date=December 20, 2019 |website=Focus Taiwan}}</ref><ref name="Taiwan News 2019">{{cite web |date=September 11, 2019 |title=Google to set up second data center in Taiwan |url=https://www.taiwannews.com.tw/en/news/3774158 |access-date=December 20, 2019 |website=Taiwan News}}</ref>
|
|-
|Asia
|[[Thailand]]
|
|
|
|2022 - announced<ref name=":0" />
|
|-
|Asia
|[[Yunlin County|Yunlin County, Taiwan]]
|
| -
|Taiwan (asia-east1)
|2020 September - announced<ref name="Taipei News 2020">{{cite web |date=September 3, 2020 |title=Google confirms plans to build 3rd data center in Taiwan |url=https://www.taiwannews.com.tw/en/news/4001183 |access-date=September 3, 2020 |website=Taiwan News}}</ref>
|
|-
|North America
|[[Mesa, Arizona|Mesa (AZ), USA]]
|
|
|
|2023 - construction started<ref>{{Cite web |date=2024-03-14 |title=Our work to build a more sustainable future in Arizona |url=https://blog.google/outreach-initiatives/sustainability/google-carbon-free-data-center-arizona-/ |access-date=2024-10-05 |website=Google |language=en-us}}</ref>
|
|-
|Europe
|[[Waltham Cross|Waltham Cross, Hertfordshire, UK]]
|{{Coord|51.695666|-0.048728|format=dms}}
|
|
|2024 January - announced<ref>{{Cite web |date=2024-01-18 |title=Our $1 billion investment in a new UK data centre |url=https://blog.google/around-the-globe/google-europe/united-kingdom/google-1-billion-investment-in-a-new-uk-data-centre/ |access-date=2024-01-19 |website=Google |language=en-us}}</ref>
|
|-
|South America
|[[Canelones Department|Canelones, Uruguay]]
|{{Coord|-34.815481|-55.995683|format=dms}}
|
|
|2024 - construction started<ref>{{Cite web |date=2024-08-29 |title=A new data center in Latin America |url=https://blog.google/around-the-globe/google-latin-america/a-new-data-center-in-latin-america/ |access-date=2024-10-05 |website=Google |language=en-us}}</ref>
2026 - inauguration expected<ref>{{Cite web |date=2024-08-30 |title=Google y la piedra fundamental (comenzó la construcción del centro de datos en Parque de las Ciencias) |url=https://infonegocios.biz/nota-principal/google-y-la-piedra-fundamental-comenzo-la-construccion-del-centro-de-datos-en-parque-de-las-ciencias |access-date=2024-10-05 |language=es-uy}}</ref>
|
|}

== Hardware ==

=== Original hardware ===
[[File:Googles First Server.jpg|thumb|upright|Google's first production server rack, circa 1998]]
The original hardware (circa 1998) that was used by Google when it was located at [[Stanford University]] included:<ref>{{cite web|url=http://google.stanford.edu/googlehardware.html |title="Google Stanford Hardware" |access-date=March 23, 2017 |url-status=bot: unknown |archive-url=https://web.archive.org/web/19990209043945/http://google.stanford.edu/googlehardware.html |archive-date=February 9, 1999 }}. ''[[Stanford University]] (provided by [[Internet Archive]]).'' Retrieved on July 10, 2006.</ref>

* [[Sun Ultra series|Sun Microsystems Ultra II]] with dual 200&nbsp;[[Hertz|MHz]] processors, and 256&nbsp;[[Megabyte|MB]] of [[Random access memory|RAM]]. This was the main machine for the original [[History of Google#Beginnings|Backrub]] system.
* 2 × 300&nbsp;MHz dual [[Pentium II]] servers donated by [[Intel]], they included 512&nbsp;MB of RAM and 10 × 9&nbsp;[[Gigabyte|GB]] hard drives between the two. It was on these that the main search ran.
* F50 IBM [[RS/6000]] donated by [[IBM]], included 4 processors, 512&nbsp;MB of memory and 8 × 9&nbsp;GB hard disk drives.
* Two additional boxes included 3 × 9&nbsp;GB hard drives and 6 x 4&nbsp;GB hard disk drives respectively (the original storage for Backrub). These were attached to the Sun Ultra II.
* SSD disk expansion box with another 8 × 9&nbsp;GB hard disk drives donated by IBM.
* Homemade disk box which contained 10 × 9&nbsp;GB [[SCSI]] hard disk drives.

=== Google Cluster ===
The state of Google infrastructure in 2003 was described in a report by [[Luiz André Barroso]], [[Jeff Dean]], and [[Urs Hölzle]] as a "reliable computing infrastructure from clusters of unreliable commodity PCs".<ref>{{Cite journal |last1=Barroso |first1=L.A. |last2=Dean |first2=J. |last3=Holzle |first3=U. |date=March 2003 |title=Web search for a planet: The Google cluster architecture |url=https://ieeexplore.ieee.org/document/1196112 |journal=IEEE Micro |volume=23 |issue=2 |pages=22–28 |doi=10.1109/MM.2003.1196112 |issn=1937-4143|url-access=subscription }}</ref>

At the time, on average, a single search query read ~100 [[Megabyte|MB]] of data, and consumed <math>\sim 10^{10}
</math> CPU cycles. During peak time, Google served ~1000 queries per second. To handle this peak load, they built a compute cluster with ~15,000 commodity-class PCs instead of expensive supercomputer hardware to save money. To make up for the lower hardware reliability, they wrote [[Fault tolerance|fault tolerant]] software. 

The structure of the cluster consists of five parts. Central Google Web servers (GWS) face the public Internet. Upon receiving a user request, the Google Web server communicates with a spell checker, an advertisement server, many index servers, many document servers. Each of the four parts responds to a part of the request, and the GWS assembles their responses and serves the final response to the user.

The raw documents were ~100 TB, and the index files were ~10 TB. The index files are sharded, and each shard is served by a "pool" of index servers. Similarly, the raw documents are also sharded. Each query to the index file results in a list of document IDs, which are then sent to the document servers to retrieve the title and the keyword-in-context snippets.

There were several CPU generations in use, ranging from single-processor 533&nbsp;MHz [[Celeron|Intel-Celeron]]-based servers to dual 1.4&nbsp;GHz Intel [[Pentium III]]. Each server contained one or more hard drives, 80 [[Gigabyte|GB]] each. Index servers have less disk space than document servers. Each rack had two [[Network switch|Ethernet switches]], one per side. The servers on each side interconnected via a 100-Mbps. Each switch had a ~250 MB/sec uplink to a central switch that connected to all racks.

The design objectives include:

* Use low-reliability consumer hardware and make up for it with fault-tolerant software.
* Maximize parallelism, such as by splitting a single document match lookup in a large index into a [[MapReduce]] over many small indices.
* Partition index data and computation to minimize communication and evenly balance the load across servers, because the cluster is a large shared-memory machine.
* Minimize system management overheads by developing all software in-house.
* Pick hardware that maximizes performance/price, not absolute performance.
* Pick hardware that has high [[Network throughput|thoroughput]] over high [[Latency (engineering)|latency]]. This is because queries are served with massive parallelism, with very few dependent steps and minimal communication between servers, so high latency does not matter.

Due to the massive parallelism, scaling up hardware scales up the thoroughput linearly, i.e. doubling the compute cluster doubles the number of queries servable per second.

The cluster is made of server racks at 2 configurations: 40 x [[Rack unit|1u]] per side with 2 sides, or 20 x [[2u server|2u]] per side with 2 sides. The power consumption is 10 kW per rack, at a density of 400 W/ft^2, consuming 10 [[Kilowatt-hour|MWh]] per month, costing $1,500 per month.

=== Production hardware ===
As of 2014, Google has used a heavily customized version of [[Debian]] [[Linux]]. They migrated from a Red Hat-based system incrementally in 2013.<ref>{{Cite web|url=https://events.static.linuxfound.org/sites/events/files/lcjp13_merlin.pdf|title=Case Study: Live upgrading many thousand of servers from an ancient Red Hat distribution to a 10 year newer Debian based one|last=Merlin|first=Marc|date=2013|website=Linux Foundation|access-date=June 9, 2017}}</ref>

The customization goal is to purchase CPU generations that offer the best performance per dollar, not absolute performance. How this is measured is unclear, but it is likely to incorporate running costs of the entire server, and CPU power consumption could be a significant factor.<ref>{{cite book|title=Strategies for E-business|author1=Tawfik Jelassi |author2=Albrecht Enders |chapter=Case study 16 — Google|publisher=Pearson Education|year=2004<!--|isbn=0-273-68840-5-->|isbn=978-0-273-68840-2|page=424}}</ref> Servers as of 2009–2010 consisted of custom-made open-top systems containing two processors (each with several cores<ref name="hp5" />), a considerable amount of RAM spread over 8 DIMM slots housing double-height DIMMs, and at least two SATA hard disk drives connected through a non-standard ATX-sized power supply unit.<ref>{{YouTube|M5wfv7RE_J4|Google's secret power supplies}}</ref> The servers were open top so more servers could fit into a rack. According to CNET and a book by [[John L. Hennessy|John Hennessy]], each server had a novel 12-volt battery to reduce costs and improve power efficiency.<ref name="hp5">Computer Architecture, Fifth Edition: A Quantitative Approach, {{ISBN|978-0123838728}}; Chapter Six; 6.7 "A Google Warehouse-Scale Computer" [https://books.google.com/books?id=gQ-fSqbLfFoC&q=google+ups&pg=PA471 page 471] "Designing motherboards that only need a single 12-volt supply so that the UPS function could be supplied by standard batteries associated with each server"</ref><ref>[https://www.cnet.com/news/google-uncloaks-once-secret-server-10209580/ Google uncloaks once-secret server], April 1, 2009.</ref>

According to Google, their global data center operation electrical power ranges between 500 and 681 [[megawatts]].<ref name="GoogleGreen">{{Cite web|url=https://sustainability.google/|title=Google Sustainability|website=Google Sustainability}}</ref><ref>{{Cite web |url=http://www.analyticspress.com/datacenters.html |title=Analytics Press Growth in data center electricity use 2005 to 2010 |access-date=May 22, 2012 |archive-url=https://web.archive.org/web/20120111082558/http://www.analyticspress.com/datacenters.html |archive-date=January 11, 2012 |url-status=dead }}</ref>
The combined processing power of these servers might have reached from 20 to 100 [[FLOPS|petaflops]] in 2008.<ref>[http://blogs.nmscommunications.com/communications/2008/05/google-surpasses-supercomputer-community-unnoticed.html Google Surpasses Supercomputer Community, Unnoticed?] {{Webarchive|url=https://web.archive.org/web/20081205075355/http://blogs.nmscommunications.com/communications/2008/05/google-surpasses-supercomputer-community-unnoticed.html |date=December 5, 2008 }}, May 20, 2008.</ref>

=== Network topology ===
Details of the Google worldwide private networks are not publicly available, but Google publications<ref>{{Citation | url = http://research.google.com/pubs/pub36603.html | title = Research | year = 2010 | volume = 48 | issue = 7 | contribution = Fiber Optic Communication Technologies: What's Needed for Datacenter Network Operations| last1 = Lam | first1 = Cedric F. | last2 = Liu | first2 = Hong | last3 = Koley | first3 = Bikash | last4 = Zhao | first4 = Xiaoxue | last5 = Kamalov | first5 = Valey | last6 = Gill | first6 = Vijay }}</ref><ref>{{Citation | url = https://storage.googleapis.com/pub-tools-public-publication-data/pdf/36936.pdf|page=4|author=Lam, Cedric F.|date=2010  |title=FTTH look ahead — technologies & architectures}}</ref> make references to the "Atlas Top 10" report that ranks Google as the third largest ISP behind [[Level 3 Communications|Level 3]].

In order to run such a large network, with direct connections to as many ISPs as possible at the lowest possible cost, Google has a very open [[peering]] policy.<ref>{{Citation | url = http://www.peeringdb.com/view.php?asn=15169 | contribution = kumara ASN15169 | title = Peering DB}}</ref>

From this site, we can see that the Google network can be accessed from 67 public exchange points and 69 different locations across the world. As of May 2012, Google had 882&nbsp;Gbit/s of public connectivity (not counting private peering agreements that Google has with the largest ISPs). This public network is used to distribute content to Google users as well as to crawl the internet to build its search indexes.
The private side of the network is a secret, but a recent disclosure from Google<ref>{{Citation | url = http://opennetsummit.org/speakers.html | contribution = Urs Holzle | title = Speakers | publisher = Open Network Summit | access-date = May 22, 2012 | archive-url = https://web.archive.org/web/20120510132234/http://opennetsummit.org/speakers.html | archive-date = May 10, 2012 | url-status = dead }}</ref> indicate that they use custom built high-radix<!-- what is that? --> [[Multilayer switch|switch-routers]] (with a capacity of 128 × 10 [[Gigabit Ethernet]] port) for the [[wide area network]]. Running no less than two routers per datacenter (for redundancy) we can conclude that the Google network scales in the terabit per second range (with two fully loaded routers the bi-sectional bandwidth amount to 1,280&nbsp;Gbit/s).

These custom switch-routers are connected to [[Wavelength-division multiplexing|DWDM]] devices to [[Data Center Interconnect|interconnect data centers]] and [[point of presence]]s (PoP) via [[dark fiber]].

From a datacenter view, the network starts at the rack level, where [[19-inch rack]]s are custom-made and contain 40 to 80 servers (20 to 40 1[[Rack unit|U]] servers on either side, while new servers are 2U rackmount systems.<ref name="google_arch">[http://static.googleusercontent.com/external_content/untrusted_dlcp/research.google.com/en/us/archive/googlecluster-ieee.pdf Web Search for a Planet: The Google Cluster Architecture] (Luiz André Barroso, Jeffrey Dean, Urs Hölzle)</ref> Each rack has an [[Ethernet switch]]). Servers are connected via a 1&nbsp;Gbit/s [[Ethernet]] link to the top of rack switch (TOR). TOR switches are then connected to a [[gigabit]] cluster switch using multiple gigabit or ten gigabit uplinks.<ref>{{Cite web |url=http://bnrg.eecs.berkeley.edu/~randy/Courses/CS294.F09/wharehousesizedcomputers.pdf |title=Warehouse size computers |access-date=May 22, 2012 |archive-date=June 19, 2012 |archive-url=https://web.archive.org/web/20120619202125/http://bnrg.eecs.berkeley.edu/~randy/Courses/CS294.F09/wharehousesizedcomputers.pdf |url-status=dead }}</ref> The cluster switches themselves are interconnected and form the datacenter interconnect fabric (most likely using a dragonfly design rather than a classic butterfly or flattened butterfly layout<ref>[http://research.google.com/pubs/archive/37069.pdf Denis Abt High Performance Datacenter Networks: Architectures, Algorithms, and Opportunities]</ref>).

From an operation standpoint, when a client computer attempts to connect to Google, several [[Domain Name System|DNS servers]] resolve <code>www.google.com</code> into multiple IP addresses via [[Round-robin DNS|Round Robin]] policy. Furthermore, this acts as the first level of [[Load balancing (computing)|load balancing]] and directs the client to different Google clusters. A Google cluster has thousands of [[server (computing)|servers]], and once the client has connected to the server additional load balancing is done to send the queries to the least loaded web server. This makes Google one of the largest and most complex [[content delivery network]]s.<ref name="Reid">{{cite book|title=Network Programming in .NET|author=Fiach Reid|pages=[https://archive.org/details/networkprogrammi00fiac/page/251 251–253]|chapter=Case Study: The Google search engine|publisher=Digital Press|year=2004|isbn=978-1-55558-315-6|chapter-url=https://archive.org/details/networkprogrammi00fiac/page/251}}</ref>

Google has numerous data centers scattered around the world. At least 12 significant Google data center installations are located in the United States. The largest known centers are located in [[The Dalles, Oregon]]; [[Atlanta|Atlanta, Georgia]]; [[Reston, Virginia]]; [[Lenoir, North Carolina]]; and [[Moncks Corner, South Carolina]].<ref name="DataCenter">{{cite web | url = http://www.datacenterknowledge.com/archives/2008/03/27/google-data-center-faq/ | title = Google Data Center FAQ | author = Rich Miller | work = Data Center Knowledge | date = March 27, 2008 | access-date = March 15, 2009 | archive-url = https://web.archive.org/web/20090313082216/http://www.datacenterknowledge.com/archives/2008/03/27/google-data-center-faq/ | archive-date = March 13, 2009 | url-status = dead | df = mdy-all }}</ref> In Europe, the largest known centers are in [[Eemshaven]] and [[Groningen]] in the [[Netherlands]] and [[Mons, Belgium|Mons]], [[Belgium]].<ref name="DataCenter" /> Google's [[Oceania]] Data Center is located in [[Sydney]], [[Australia]].<ref name="DataCenterAustralia">{{cite web| url = http://www.itnews.com.au/News/168772,found-google-australias-secret-data-network.aspx | title =Found: Google Australia's secret data network | author = Brett Winterford| work = ITNews | date= March 5, 2010 | access-date = March 20, 2010}}</ref>

=== Data center network topology ===
To support [[fault tolerance]], increase the scale of data centers and accommodate low-radix switches, Google has adopted various modified [[Clos network|Clos]] topologies in the past.<ref>{{Cite book|last1=Singh|first1=Arjun|last2=Ong|first2=Joon|last3=Agarwal|first3=Amit|last4=Anderson|first4=Glen|last5=Armistead|first5=Ashby|last6=Bannon|first6=Roy|last7=Boving|first7=Seb|last8=Desai|first8=Gaurav|last9=Felderman|first9=Bob|last10=Germano|first10=Paulie|last11=Kanagala|first11=Anand|title=Proceedings of the 2015 ACM Conference on Special Interest Group on Data Communication |chapter=Jupiter Rising: A Decade of Clos Topologies and Centralized Control in Google's Datacenter Network |date=2015 |pages=183–197 |chapter-url=https://research.google/pubs/pub43837/ |doi=10.1145/2785956.2787508|s2cid=2817692|doi-access=free|isbn=978-1-4503-3542-3 }}</ref>

=== Project 02 ===
[[File:Google_data_center.jpg|thumb|Google data center in The Dalles, Oregon]]
One of the largest Google data centers is located in the town of [[The Dalles, Oregon]], on the [[Columbia River]], approximately 80 miles (129&nbsp;km) from [[Portland, Oregon|Portland]]. Codenamed "Project 02", the complex was built in 2006 and is approximately the size of two [[American football field]]s, with [[cooling towers]] four stories high.<ref name="project02">Markoff, John; Hansell, Saul. "[https://www.nytimes.com/2006/06/14/technology/14search.html Hiding in Plain Sight, Google Seeks More Power.]" ''[[New York Times]].'' June 14, 2006. Retrieved on October 15, 2008.</ref><ref>Google "[https://www.google.com/datacenter/thedalles/ The Dalles, Oregon Data Center]" Retrieved on January 3, 2011.</ref> The site was chosen to take advantage of inexpensive [[hydroelectric power]], and to tap into the region's large [[dark fiber|surplus]] of [[fiber optic]] cable, a remnant of the [[dot-com boom]]. A blueprint of the site appeared in 2008.<ref>Strand, Ginger.
"[http://harpers.org/media/slideshow/annot/2008-03/zoom.html Google Data Center]" ''[[Harper's Magazine]]''. March 2008. Retrieved on October 15, 2008. {{webarchive |url=https://web.archive.org/web/20120830120156/http://harpers.org/media/slideshow/annot/2008-03/zoom.html |date=August 30, 2012 }}</ref>

=== Summa papermill ===
In February 2009, [[Stora Enso]] announced that they had sold the Summa paper mill in [[Hamina]], [[Finland]] to Google for 40 million Euros.<ref>{{cite web | url = http://www.storaenso.com/media-centre/press-releases/2009/02/Pages/stora-enso-divests-summa-mill.aspx | title = Stora Enso divests Summa Mill premises in Finland for million | publisher = [[Stora Enso]] | date = February 12, 2009 | access-date = December 2, 2009 | archive-url = https://web.archive.org/web/20090413023322/http://www.storaenso.com/media-centre/press-releases/2009/02/Pages/stora-enso-divests-summa-mill.aspx | archive-date = April 13, 2009 | url-status = dead }}</ref><ref>{{dead link|date=November 2017}} {{Cite journal | url = http://www.kauppalehti.fi/5/i/talous/uutiset/etusivu/uutinen.jsp?oid=2009/02/18987 | title = Stooora yllätys: Google ostaa Summan tehtaan | journal = [[Kauppalehti]] | date = February 12, 2009 | place = Helsinki | access-date = February 12, 2009 | language = fi | archive-url = https://web.archive.org/web/20090214232026/http://www.kauppalehti.fi/5/i/talous/uutiset/etusivu/uutinen.jsp?oid=2009%2F02%2F18987 | archive-date = February 14, 2009 | url-status = dead }}</ref> Google invested 200 million euros on the site to build a data center and announced additional 150 million euro investment in 2012.<ref>{{Cite journal | url = http://www.taloussanomat.fi/talous/2009/03/04/google-investoi-200-miljoonaa-euroa-haminaan/20095951/133 | title = Google investoi 200 miljoonaa euroa Haminaan | journal = [[Taloussanomat]] | date = February 4, 2009 | place = Helsinki | access-date = March 15, 2009 | language = fi}}</ref><ref>{{cite web| url=https://www.google.com/about/datacenters/inside/locations/hamina/ |title=Hamina, Finland|access-date=April 23, 2018}}</ref> Google chose this location due to the availability and proximity of renewable energy sources.<ref>[http://www.fincloud.freehostingcloud.com/ Finland – First Choice for Siting Your Cloud Computing Data Center.] {{webarchive|url=https://web.archive.org/web/20130706112506/http://www.fincloud.freehostingcloud.com/ |date=July 6, 2013 }} Accessed August 4, 2010.</ref>

=== Floating data centers ===
{{See also|Google barges}}
In 2013, the press revealed the existence of Google's floating data centers along the coasts of the states of California ([[Treasure Island, San Francisco|Treasure Island]]'s Building 3) and Maine. The development project was maintained under tight secrecy. The data centers are 250 feet long, 72 feet wide, 16 feet deep. The patent for an in-ocean data center cooling technology was bought by Google in 2009<ref>{{cite web|url=https://www.theguardian.com/technology/2013/oct/30/google-secret-floating-data-centers-california-maine|title=Google's worst-kept secret: floating data centers off US coasts|website=Theguardian.com|date=October 30, 2013|author=Rory Carroll|access-date=December 8, 2018}}</ref><ref>{{cite web|url=https://www.datacenterknowledge.com/archives/2009/04/29/google-gets-patent-for-data-center-barges|title=Google Gets Patent for Data Center Barges|website=Datacenterknowledge.com|date=April 29, 2009|author=Rich Miller|access-date=December 8, 2018}}</ref> (along with a wave-powered ship-based data center patent in 2008<ref>{{cite web|url=https://www.cnet.com/news/google-files-patent-for-wave-powered-floating-data-center/|title=Google files patent for wave-powered floating data center|website=Cnet.com|date=September 8, 2008|author=Martin Lamonica|access-date=December 8, 2018}}</ref><ref>{{cite web|url=https://www.datacenterdynamics.com/news/googles-ship-based-datacenter-patent-application-surfaces/|title=Google's ship based datacenter patent application surfaces|website=Datacenterdynamics.com|date=September 7, 2008|access-date=December 8, 2018}}</ref>). Shortly thereafter, Google declared that the two massive and secretly built infrastructures were merely "interactive learning centers, [...] a space where people can learn about new technology."<ref>{{cite web|url=https://www.theguardian.com/technology/2013/nov/06/google-barge-mystery-solved-interactive-learning-center|title=Google barge mystery solved: they're for 'interactive learning centers'|website=Theguardian.com|date=November 6, 2013|access-date=December 8, 2018}}</ref>

Google halted work on the barges in late 2013 and began selling off the barges in 2014.<ref name="sold">{{cite news|url=https://www.mercurynews.com/2014/08/01/google-confirms-selling-a-mystery-barge/|title=Google confirms selling a mystery barge|date=August 1, 2014|work=[[San Jose Mercury News]]|author=Brandon Bailey|access-date=April 7, 2015}}</ref><ref name="consumerist-ended">{{cite news|url=https://consumerist.com/2014/11/07/what-happened-to-those-google-barges/|title=What Happened To Those Google Barges?|date=November 7, 2014|work=[[Consumerist]]|author=Chris Morran|access-date=January 15, 2017}}</ref>

== Software ==
Most of the [[software stack]] that Google uses on their servers was developed in-house.<ref>{{cite book | title=An Introduction to Search Engines and Web Navigation|author=Mark Levene|publisher= Pearson Education |year=2005<!--|isbn=0-321-30677-5-->|isbn=978-0-321-30677-7|page=73}}</ref> According to a well-known former Google employee in 2006, [[C++]], [[Java (programming language)|Java]], [[Python (programming language)|Python]] and (more recently) [[Go (programming language)|Go]] are favored over other programming languages.<ref>{{cite web|url=http://www.artima.com/weblogs/viewpost.jsp?thread=143947 |title=Python Status Update |publisher=Artima |date=January 10, 2006 | access-date = February 17, 2012}}</ref> For example, the back end of Gmail is written in Java and the back end of Google Search is written in C++.<ref>{{cite web|url=http://panela.blog-city.com/python_at_google_greg_stein__sdforum.htm |title=Warning |work=Panela |publisher=Blog-city |access-date=February 17, 2012 |url-status=dead |archive-url=https://web.archive.org/web/20111228034932/http://panela.blog-city.com/python_at_google_greg_stein__sdforum.htm |archive-date=December 28, 2011 }}</ref> Google has acknowledged that Python has played an important role from the beginning, and that it continues to do so as the system grows and evolves.<ref>{{cite web| url = http://python.org/about/quotes/ |title=Quotes about Python |publisher=Python |access-date = February 17, 2012}}</ref>

The software that runs the Google infrastructure includes:<ref>{{cite web|url= http://highscalability.com/google-architecture |title=Google Architecture |publisher= High Scalability |date=November 22, 2008 |access-date=February 17, 2012}}</ref>
* [[Google Web Server|Google Web Server (GWS)]]{{snd}} custom Linux-based Web server that Google uses for its online services.
* Storage systems:
** [[Google File System]] and its successor, Colossus<ref name="fikes">{{Citation | first = Andrew | last = Fikes | url = http://research.google.com/university/relations/facultysummit2010/storage_architecture_and_challenges.pdf | contribution = Storage Architecture and Challenges | title = TechTalk | date = July 29, 2010 }}{{dead link|date=April 2019 |bot=InternetArchiveBot |fix-attempted=yes }}</ref><ref name="ma">{{cite web | url = http://www.systutorials.com/3202/colossus-successor-to-google-file-system-gfs/ | title = Colossus: Successor to the Google File System (GFS) | publisher = SysTutorials | date = November 29, 2012 | access-date=May 10, 2016}}</ref>
** [[Bigtable]]{{snd}} structured storage built upon GFS/Colossus<ref name="fikes" />
** [[Spanner (distributed database technology)|Spanner]]{{snd}} planet-scale database, supporting externally-consistent distributed transactions<ref name="fikes" /><ref name="ladis">{{Citation | first = Jeffrey 'Jeff' | last = Dean | year = 2009 | url = http://www.cs.cornell.edu/projects/ladis2009/talks/dean-keynote-ladis2009.pdf | contribution = Design, Lessons and Advice from Building Large Distributed Systems | format = keynote talk presentation | title = Ladis | publisher = Cornell}}</ref>
** [[Google F1]]{{snd}} a distributed, quasi-[[SQL]] [[DBMS]] based on Spanner, substituting a custom version of MySQL.<ref>{{Citation | url = http://research.google.com/pubs/pub38125.html | title = Research | format = presentation | place = [[Sigmod]] | contribution = F1 — the Fault-Tolerant Distributed RDBMS Supporting Google's Ad Business | year = 2012 | first1 = Jeffrey 'Jeff' | last1 = Shute | first2 = Mircea | last2 = Oancea | first3 = Stephan | last3 = Ellner | first4 = Benjamin 'Ben' | last4 = Handy | first5 = Eric | last5 = Rollins | first6 = Bart | last6 = Samwel | first7 = Radek | last7 = Vingralek | first8 = Chad | last8 = Whipkey | first9 = Xin | last9 = Chen | first10 = Beat | last10 = Jegerlehner | first11 = Kyle | last11 = Littlefield | first12 = Phoenix | last12 = Tong | access-date = September 18, 2012 | archive-date = June 9, 2017 | archive-url = https://web.archive.org/web/20170609055135/https://research.google.com/pubs/pub38125.html | url-status = dead }}</ref>
* [[Distributed lock manager#Google's Chubby lock service|Chubby lock service]]
* [[MapReduce]] and [[Sawzall (programming language)|Sawzall programming language]]
* Indexing/search systems:
** TeraGoogle{{snd}} Google's large search index (launched in early 2006)<ref>{{Cite web|date=2008-07-28|title=Google alums rev up a new search engine|url=https://www.latimes.com/archives/la-xpm-2008-jul-28-fi-search28-story.html|access-date=2021-09-15|website=Los Angeles Times|language=en-US}}</ref>
** Caffeine (Percolator){{snd}} continuous indexing system (launched in 2010).<ref name="caffeine1" />
** Hummingbird{{snd}} major search index update, including complex search and voice search.<ref>{{cite web|url=http://insidesearch.blogspot.co.il/2013/09/fifteen-years-onand-were-just-getting.html |title=Google official release note |access-date=September 28, 2013}}</ref>
* [[Google Borg|Borg]] declarative process scheduling software

Google has developed several abstractions which it uses for storing most of its data:<ref name="quinlan">{{cite web |url=http://www.eweekeurope.co.uk/news/news-it-infrastructure/google-developing-caffeine-storage-system-1620 |title=Google Developing Caffeine Storage System &#124; TechWeekEurope UK |publisher=Eweekeurope.co.uk |date=August 18, 2009 |access-date=February 17, 2012 |archive-url=https://web.archive.org/web/20111115162704/http://www.eweekeurope.co.uk/news/news-it-infrastructure/google-developing-caffeine-storage-system-1620 |archive-date=November 15, 2011 |url-status=dead }}</ref>
* [[Protocol Buffers]]{{snd}} "Google's lingua franca for data",<ref>{{cite web|url=https://code.google.com/apis/protocolbuffers/docs/overview.html |title=Developer Guide – Protocol Buffers – Google Code |access-date=February 17, 2012}}</ref> a binary serialization format which is widely used within the company.
* [[SSTable]] (Sorted Strings Table){{snd}} a persistent, ordered, immutable map from keys to values, where both keys and values are arbitrary byte strings. It is also used as one of the building blocks of Bigtable.<ref>http://static.googleusercontent.com/media/research.google.com/en/us/archive/bigtable-osdi06.pdf {{Bare URL PDF|date=March 2022}}</ref>
* RecordIO{{snd}} a sequence of variable sized records.<ref name="quinlan" /><ref>{{cite web|author=windley on |url=http://www.windley.com/archives/2008/06/velocity_08_storage_at_scale.shtml |title=Phil Windley's Technometria &#124; Velocity 08: Storage at Scale |publisher=Windley.com |date=June 24, 2008 |access-date=February 17, 2012}}</ref><ref>{{cite web|url=https://groups.google.com/group/protobuf/browse_thread/thread/ee27572aef9da70a |title=Message limit – Protocol Buffers &#124; Google Groups |access-date=February 17, 2012}}</ref>

=== Software development practices ===
Most operations are read-only. When an update is required, queries are redirected to other servers, so as to simplify consistency issues. Queries are divided into sub-queries, where those sub-queries may be sent to different ducts in [[Parallel computing|parallel]], thus reducing the latency time.<ref name="google_arch" />

To lessen the effects of unavoidable [[Computer hardware|hardware]] failure, software is designed to be [[fault tolerant]]. Thus, when a system goes down, data is still available on other servers, which increases reliability.

== Search infrastructure ==

[[File:Google Data Center, The Dalles.jpg|thumb|Google data center in [[The Dalles, Oregon]]]]
=== Index ===
Like most search engines, Google indexes documents by building a data structure known as [[inverted index]]. Such an index obtains a list of documents by a query word. The index is very large due to the number of documents stored in the servers.<ref name=Reid />

The index is partitioned by document IDs into many pieces called [[Shard (database architecture)|shards]]. Each shard is [[Replication (computer science)|replicated]] onto multiple servers. Initially, the index was being served from [[hard disk drive]]s, as is done in traditional [[information retrieval]] (IR) systems. Google dealt with the increasing query volume by increasing number of replicas of each shard and thus increasing number of servers. Soon they found that they had enough servers to keep a copy of the whole index in main memory (although with low replication or no replication at all), and in early 2001 Google switched to an ''in-memory index'' system. This switch "radically changed many design parameters" of their search system, and allowed for a significant increase in throughput and a large decrease in latency of queries.<ref name="wsdm2009">{{cite web|url=http://research.google.com/people/jeff/WSDM09-keynote.pdf |title=Jeff Dean's keynote at WSDM 2009 |access-date=February 17, 2012}}</ref>

In June 2010, Google rolled out a next-generation indexing and serving system called "Caffeine" which can continuously crawl and update the search index. Previously, Google updated its search index in batches using a series of [[MapReduce]] jobs. The index was separated into several layers, some of which were updated faster than the others, and the main layer wouldn't be updated for as long as two weeks. With Caffeine, the entire index is updated incrementally on a continuous basis. Later Google revealed a distributed data processing system called "Percolator"<ref>Daniel Peng, Frank Dabek. (2010). [https://research.google.com/pubs/pub36726.html Large-scale Incremental Processing Using Distributed Transactions and Notifications]. Proceedings of the 9th USENIX Symposium on Operating Systems Design and Implementation.</ref> which is said to be the basis of Caffeine indexing system.<ref name="caffeine1">The Register. [https://www.theregister.co.uk/2010/06/09/google_completes_caffeine_search_index_overhaul/ Google Caffeine jolts worldwide search machine]</ref><ref name="caffeine2">The Register. [https://www.theregister.co.uk/2010/09/24/google_percolator/ Google Percolator – global search jolt sans MapReduce comedown]</ref>

=== Server types ===
Google's server infrastructure is divided into several types, each assigned to a different purpose:<ref name="google_arch" /><ref name=Reid /><ref name=Evans1>{{cite book|title=Future of Google Earth|author=Chandler Evans|chapter=Google Platform|publisher=Madison Publishing Company|year=2008<!--|isbn=1-4196-8903-7-->|isbn=978-1-4196-8903-1|page=299}}</ref><ref>{{cite book|title=Google Power|author=Chris Sherman|pages=[https://archive.org/details/googlepowerunlea0000sher/page/10 10–11]|publisher=McGraw-Hill Professional|year=2005<!--|isbn=0-07-225787-3-->|isbn=978-0-07-225787-8|chapter=How Google Works|url=https://archive.org/details/googlepowerunlea0000sher/page/10}}</ref><ref>{{cite book|chapter=How Google Works|pages=[https://archive.org/details/googlepediaultim0000mill/page/17 17–18]|title=Googlepedia|author=Michael Miller|publisher=Pearson Technology Group|year=2007<!--|isbn=0-7897-3639-X-->|isbn=978-0-7897-3639-0|url=https://archive.org/details/googlepediaultim0000mill/page/17}}</ref>
* Web servers coordinate the execution of queries sent by users, then format the result into an [[HTML]] page. The execution consists of sending queries to index servers, merging the results, computing their rank, retrieving a summary for each hit (using the document server), asking for suggestions from the spelling servers, and finally getting a list of advertisements from the ad server.
* Data-gathering servers are permanently dedicated to [[web crawler|spidering]] the Web. Google's web crawler is known as GoogleBot. They update the index and document databases and apply Google's algorithms to assign ranks to pages.
* Each index server contains a set of index shards. They return a list of document IDs ("docid"), such that documents corresponding to a certain docid contain the query word. These servers need less disk space, but suffer the greatest CPU workload.
* Document servers store documents. Each document is stored on dozens of document servers. When performing a search, a document server returns a summary for the document based on query words. They can also fetch the complete document when asked. These servers need more disk space.
* Ad servers manage advertisements offered by services like [[AdWords]] and [[AdSense]].
* Spelling servers make suggestions about the spelling of queries.
There are also "canary requests", whereby a request is first sent to one or two leaf servers to see if the response time is reasonable. If not, then the request fails. This provides security.<ref>{{Cite journal |last1=Dean |first1=Jeffrey |last2=Barroso |first2=Luiz André |date=February 2013 |title=The tail at scale |url=https://dl.acm.org/doi/10.1145/2408776.2408794 |journal=Communications of the ACM |language=en |volume=56 |issue=2 |pages=74–80 |doi=10.1145/2408776.2408794 |issn=0001-0782|url-access=subscription }}</ref>

== Security ==
{{external media
| float  = right
| caption = YouTube <!-- text placed left or right of headerimage --->
| headerimage= [[File:YouTube 2024.svg|alt=YouTube logo|x20px|left]]
| video1 = [https://www.youtube.com/watch?v=kd33UVZhnAA Google Data Center Security: 6 Layers Deep]
}}

In October 2013, ''[[The Washington Post]]'' reported that the U.S. [[National Security Agency]] intercepted communications between Google's data centers, as part of a program named [[Muscular (surveillance program)|MUSCULAR]].<ref>{{cite news|url=https://www.washingtonpost.com/world/national-security/nsa-infiltrates-links-to-yahoo-google-data-centers-worldwide-snowden-documents-say/2013/10/30/e51d661e-4166-11e3-8b74-d89d714ca4dd_story.html|title=NSA infiltrates links to Yahoo, Google data centers worldwide, Snowden documents say|last1=Gellman|first1=Barton|date=October 30, 2013|newspaper=The Washington Post|access-date=November 1, 2013|last2=Soltani|first2=Ashkan}}</ref><ref>{{cite web|url=https://www.nytimes.com/2013/10/31/technology/nsa-is-mining-google-and-yahoo-abroad.html|title=N.S.A. Said to Tap Google and Yahoo Abroad|last1=Savage|first1=Charlie|last2=Miller|first2=Claire Cain|date=October 30, 2013|website=[[The New York Times]]|access-date=March 9, 2017|last3=Perlroth|first3=Nicole}}</ref> This wiretapping was made possible because, at the time, Google did not encrypt data passed inside its own network.<ref>{{cite web|url=https://arstechnica.com/information-technology/2013/10/how-the-nsas-muscular-tapped-googles-and-yahoos-private-networks/|title=How the NSA's MUSCULAR tapped Google's and Yahoo's private networks|last=Gallagher|first=Sean|date=October 31, 2013|website=[[Ars Technica]]|publisher=[[Condé Nast]]|access-date=March 9, 2017}}</ref> This was rectified when Google began encrypting data sent between data centers in 2013.<ref>{{cite web|url=https://www.nytimes.com/2013/11/01/technology/angry-over-us-surveillance-tech-giants-bolster-defenses.html|title=Angry Over U.S. Surveillance, Tech Giants Bolster Defenses|last=Miller|first=Claire Cain|date=October 31, 2013|website=[[The New York Times]]|access-date=March 9, 2017}}</ref>

== Environmental impact ==
[[File:Google Mayes County P0004991a.jpg|thumb|Google data center in [[Mayes County, Oklahoma]] at [[MidAmerica Industrial Park]]]]
Google's most efficient data center runs at {{convert|35|C}} using only fresh air cooling, requiring no electrically powered air conditioning.<ref>{{cite web|url=http://www.geek.com/chips/googles-most-efficient-data-center-runs-at-95-degrees-1478473/|title=Google's most efficient data center runs at 95 degrees|last=Humphries|first=Matthew|date=March 27, 2012|website=geek.com|archive-url=https://web.archive.org/web/20160613112324/http://www.geek.com/chips/googles-most-efficient-data-center-runs-at-95-degrees-1478473/|archive-date=June 13, 2016|access-date=June 13, 2016}}</ref>

In December 2016, Google announced that—starting in 2017—it would purchase enough renewable energy to match 100% of the energy usage of its data centers and offices. The commitment will make Google "the world's largest corporate buyer of renewable power, with commitments reaching 2.6 gigawatts (2,600 megawatts) of wind and solar energy".<ref>{{cite web|url=https://blog.google/topics/environment/100-percent-renewable-energy/|title=We're set to reach 100% renewable energy — and it's just the beginning|last=Hölzle|first=Urs|date=December 6, 2016|website=The Keyword Google Blog|access-date=December 8, 2016}}</ref><ref>{{cite web|url=https://www.theverge.com/2016/12/6/13852004/google-data-center-oklahoma-renewable-energy-climate-change|title=Google just notched a big victory in the fight against climate change|last=Statt|first=Nick|date=December 6, 2016|website=[[The Verge]]|publisher=[[Vox Media]]|access-date=December 8, 2016}}</ref><ref>{{cite web|url=https://techcrunch.com/2016/12/06/google-says-it-will-hit-100-renewable-energy-by-2017/|title=Google says it will hit 100% renewable energy by 2017|last=Etherington|first=Darrell|date=December 7, 2016|website=[[TechCrunch]]|publisher=[[AOL]]|access-date=December 8, 2016}}</ref>

{{Clear}}

== References ==
{{Reflist|30em}}

== Further reading ==
{{refbegin}}
* {{cite journal|journal=[[IEEE Micro]]|volume=23|pages=22–28|date=March–April 2002|author1=L.A. Barroso |author2=J. Dean |author3=U. Hölzle |title=Web search for a planet: The Google cluster architecture|doi=10.1109/MM.2003.1196112|url=http://static.googleusercontent.com/external_content/untrusted_dlcp/research.google.com/en/us/archive/googlecluster-ieee.pdf|issue=2}}
* Shankland, Stephen, CNET news "[http://news.cnet.com/8301-1001_3-10209580-92.html Google uncloaks once-secret server] {{Webarchive|url=https://web.archive.org/web/20140716084210/http://news.cnet.com/8301-1001_3-10209580-92.html |date=July 16, 2014 }}." April 1, 2009.
{{refend}}

== External links ==
* [http://research.google.com/pubs/papers.html Google Research Publications]
* [http://research.google.com/archive/googlecluster-ieee.pdf Web Search for a Planet: The Google Cluster Architecture] (Luiz André Barroso, Jeffrey Dean, Urs Hölzle)

{{Google LLC}}

[[Category:Google buildings and structures]]
[[Category:Data centers]]