Google data center launched in Moscow?
The list of Google data centers in the news skipped the last time last year (see TechCrunch ). Google itself is not very fond of voicing the location of its data centers (DC), since it considers their power to be its competitive advantage, and may practice designing DCs for companies that do not have the word “Google” in their name. Some information about their own DCs can only be obtained by a cunning search engine query .
... as of March 2008. The largest ones are marked in bold.
IN USA
INTERNATIONAL
For a long time, Russian users received YouTube site content from either American or European DCs, usually accessing them via Google channels, the entry point to which is located at the Moscow traffic exchange point MSK-IX (I assume that there were other options, but I’m talking about I don’t know them).
But just the other day, I noticed the unusual behavior of videos downloaded from YouTube. It turned out - surprise surprise! - that traffic is given by none other than a member of the Russian criminal group (separate peer group) Comstar-Direct (nee MTU-Intel, AS8359). In particular, the traces to the YouTube video servers looked as follows: and RIPE reports that the subnet 212.188.7.0/24 is called MTU-RCA (a bonus to someone who tells me the correct decryption
RCA :), but nothing more is known about it. Recently, Comstar has not reported anything about the launch of the DC, and therefore, it seems to me that we are talking about a special subnet for Google.
For comparison, here is how traffic would go in the usual case:
How to say. Undoubtedly, the appearance of Google DC in Moscow is a blessing, because Now less time will be spent on server requests, content will be delivered faster. But, on the other hand, I categorically do not like Google’s choice as the uplink for the DC of one provider, Comstar-Direct, as an uplink. In addition to being one of the ideologists of the Separate Peering Group and the guardians of the high cost of transit of main traffic, the refusal to pass traffic through MSK-IX can significantly increase bills for upstream services from those providers whose customers like YouTube videos. That is, innocent people may suffer.
Google DC List
... as of March 2008. The largest ones are marked in bold.
IN USA
- Mountain View California
- Pleasanton California
- San Jose California
- Los Angeles California
- Palo Alto California
- Seattle Washington
- Portland Oregon
- Dulles Oregon
- Chicago Illinois
- Atlanta Georgia (two sites)
- Reston, pcs. Virginia
- Ashburn Virginia
- Virginia Beach Virginia
- Houston Texas
- Miami Florida
- Lenoir, pcs. North Carolina
- Goose Creek North Carolina
- Prior, pcs. Oklahoma (under construction, delayed)
- Kansl Bluffs Iowa (under construction)
INTERNATIONAL
- Toronto Canada
- Berlin, Germany
- Frankfurt, Germany
- Munich, Germany
- Zurich, Switzerland
- Groningen, Holland
- Mons, Belgium
- Emshaven, Holland
- Paris, France
- London, Great Britain
- Dublin, Ireland
- Milan, Italy
- Moscow, Russia
- Sao Paolo, Brazil
- Tokyo, Japan
- Hong Kong, China
- Beijing, China
YouTube in Russia
For a long time, Russian users received YouTube site content from either American or European DCs, usually accessing them via Google channels, the entry point to which is located at the Moscow traffic exchange point MSK-IX (I assume that there were other options, but I’m talking about I don’t know them).
But just the other day, I noticed the unusual behavior of videos downloaded from YouTube. It turned out - surprise surprise! - that traffic is given by none other than a member of the Russian criminal group (separate peer group) Comstar-Direct (nee MTU-Intel, AS8359). In particular, the traces to the YouTube video servers looked as follows: and RIPE reports that the subnet 212.188.7.0/24 is called MTU-RCA (a bonus to someone who tells me the correct decryption
> hrping -r2 -a6 v22.lscache3.googlevideo.com
Tracing route to v22.lscache3.googlevideo.com [212.188.7.25] with 64 bytes data (92 bytes IP) over a maximum of 30 hops:
<...>
8 3.079 2.949 [195.34.59.26] a481-cr02-po2.msk.stream-internet.net
9 2.846 2.710 [195.34.59.173] a481-cr04-po1.msk.stream-internet.net
10 2.997 6.673 [195.34.59.109]
11 * 534.662 [212.188.7.25]> hrping -r2 -a6 v11.lscache5.googlevideo.com
Tracing route to v11.lscache5.googlevideo.com [212.188.7.29] with 64 bytes data (92 bytes IP) over a maximum of 30 hops:
<...>
8 4.053 3.218 [212.188.1.65]
9 3.329 6.392 [195.34.59.58] a481-cr04-po3.msk.stream-internet.net
10 5.578 3.046 [195.34.59.109]
11 23.401 3.038 [212.188.7.29]RCA :), but nothing more is known about it. Recently, Comstar has not reported anything about the launch of the DC, and therefore, it seems to me that we are talking about a special subnet for Google.
For comparison, here is how traffic would go in the usual case:
> hrping -r2 -a6 v1.cache4.googlevideo.com
Tracing route to v1.cache4.googlevideo.com [74.125.208.112] with 64 bytes data (92 bytes IP) over a maximum of 30 hops:
<...>
6 2.795 3.898 [193.232.246.232] pr01.svo01.net.google.com # точка присутствия Гугла на MSK-IX
7 30.527 27.400 [216.239.43.242] # здесь и далее сети Гугла, адресация ARIN
8 46.125 130.411 [209.85.254.153]
9 78.163 60.713 [216.239.48.10]
10 308.982 63.117 [209.85.241.183]
11 61.106 61.048 [74.125.208.112]This is good?
How to say. Undoubtedly, the appearance of Google DC in Moscow is a blessing, because Now less time will be spent on server requests, content will be delivered faster. But, on the other hand, I categorically do not like Google’s choice as the uplink for the DC of one provider, Comstar-Direct, as an uplink. In addition to being one of the ideologists of the Separate Peering Group and the guardians of the high cost of transit of main traffic, the refusal to pass traffic through MSK-IX can significantly increase bills for upstream services from those providers whose customers like YouTube videos. That is, innocent people may suffer.