Is Google's data center in Moscow launched?
The list of Google data centers in the news slipped last time last year (see TechCrunch ). Google itself does not like to voice the location of its datacenters (DC), as it considers their power as its competitive advantage, and can practice the design of DC on companies that do not have the word "Google" in their name. Some information about your own DC can only be obtained by a tricky search engine query .
... as of March 2008. Bold highlighted the largest.
IN USA
INTERNATIONAL
For a long time, Russian users received YouTube content from either American or European DCs, usually leaving to them via Google’s channels, the entry point to which is located on the MSK-IX Moscow traffic exchange point (I admit that there were other options, but I’m I do not know them).
But just the other day I noticed an unusual behavior of videos loading from YouTube. It turned out - surprise surprise! - that the traffic is given away by none other than a member of the Russian organized criminal group (separate peering group) of Comstar-Direct (nee MTU-Intel, AS8359). In particular, the traces to youtube video servers looked like this:
and
RIPE reports that subnet 212.188.7.0/24 is called MTU-RCA (a bonus to anyone who prompts the correct decryption of RCA :), but nothing more is known about it. Comstar recently did not report anything about the launch of the DC, and therefore, it seems to me that this is a special subnet for Google.
')
For comparison, here’s how traffic would go in the usual case:
How to say. Undoubtedly, the appearance of the Google Google shopping center in Moscow is good, since now less time will be spent on requests to servers, content will be given faster. But, on the other hand, I absolutely do not like at the moment the choice of Google as an uplink for DC of one provider - Comstar-Direct. Apart from the fact that they are one of the ideologists of the Separate Peering Group and the guardians of the high cost of transit of backbone traffic, the refusal to pass traffic through the MSK-IX can significantly increase the bills for upstream services from those providers whose customers love UTube videos. That is, innocent people may suffer.
List of DC Google
... as of March 2008. Bold highlighted the largest.
IN USA
- Mountain View, pcs. California
- Pleasanton, pcs. California
- San Jose, pieces California
- Los Angeles, pieces California
- Palo Alto, pieces California
- Seattle, pieces Washington
- Portland, pieces Oregon
- Dulles, pieces Oregon
- Chicago, pieces Illinois
- Atlanta, units Georgia (two sites)
- Reston, pieces Virginia
- Ashburn, pieces Virginia
- Virginia Beach, pcs. Virginia
- Houston, pieces Texas
- Miami, pieces Florida
- Lenoir, pieces North Carolina
- Goose Creek, units North Carolina
- Pryor, pcs. Oklahoma (under construction, delayed)
- Kansl Bluffs, units 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 content from either American or European DCs, usually leaving to them via Google’s channels, the entry point to which is located on the MSK-IX Moscow traffic exchange point (I admit that there were other options, but I’m I do not know them).
But just the other day I noticed an unusual behavior of videos loading from YouTube. It turned out - surprise surprise! - that the traffic is given away by none other than a member of the Russian organized criminal group (separate peering group) of Comstar-Direct (nee MTU-Intel, AS8359). In particular, the traces to youtube video servers looked like this:
> 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]and
> 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]RIPE reports that subnet 212.188.7.0/24 is called MTU-RCA (a bonus to anyone who prompts the correct decryption of RCA :), but nothing more is known about it. Comstar recently did not report anything about the launch of the DC, and therefore, it seems to me that this is a special subnet for Google.
')
For comparison, here’s 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 the Google Google shopping center in Moscow is good, since now less time will be spent on requests to servers, content will be given faster. But, on the other hand, I absolutely do not like at the moment the choice of Google as an uplink for DC of one provider - Comstar-Direct. Apart from the fact that they are one of the ideologists of the Separate Peering Group and the guardians of the high cost of transit of backbone traffic, the refusal to pass traffic through the MSK-IX can significantly increase the bills for upstream services from those providers whose customers love UTube videos. That is, innocent people may suffer.
Source: https://habr.com/ru/post/62574/
All Articles