Google once again hit the Register of banned sites

Today, my dear wife decided to update her blog on Blogspote, but unfortunately could not go to him. By logging in to the blog anonymizer, I made sure that it was there. Swearing once again to the provider, I still decided to check the thought that had crept inside of me - what if it was suddenly blocked? I determined the address by NSLookup: 173.194.71.132, I went to zapret-info.gov.ru and hammered a captcha the second time I saw:



Finding out that 173.194.71.132 belongs to Google, I explained to my wife the situation and said that the only way out would be to start a blog on a dedicated IP on paid hosting, then the probability of such a WTF would be much lower.
')
So I just don't understand one thing, why block the whole IP? The only reason, in my opinion, is to hide the true reason for the blocking. After all, it is convenient to hang “forbidden content” on the same IP as the objectionable site and enter the entire IP into the registry.



UPD: Comment from degorov : And at this address there are GoogleFlats, Google reader icons, plugins for chrome. storage.googleapis.com is also on the same IP.

UPD2: Comment from trip : They say that in gmail attachments have stopped downloading. Perhaps, too, somehow connected. (I confirm, I can look through the GoogleDox, but I can not download the file.)

UPD3: Goodymun offered a version of the "paranoid conspiracy theory": The ip that contains googleusercontent.com is in the registry. This, if I am not mistaken, blocks the ability to view the “Saved copies” of the pages and their translation. In fact, the two easiest ways to access closed sites for an inexperienced user (not counting Opera Turbo). This coincidence looks like a targeted attack on Google services. (Indeed, paranoid, but this theory also has the right to life - we are waiting for comments)

UPD4: V1TSK with team-fortress.ru discovered a problem yesterday at 16 o'clock: Currently, some servers from googleusercontent.com with IP 173.194.71.132 are blocked, namely: s2.googleusercontent.com, s3.googleusercontent.com, s5 .googleusercontent.com, mail-attachments.googleusercontent.com. At the moment, part of the functionality of such services as Gmail (viewing and downloading attachments are no longer available), Google Reader, Google Plus, Google Drive has fallen off. (That's the reason for the inability to download attachments from Google Mail)

UPD5: Address from the registry is removed. I want to express my deep gratitude to all users who supported the post. I think it was thanks to you and Habra managed to quickly spread information on Runet and help eliminate the next "technical error". Thank!

UPD6: For those whose providers have blocked IP, there is a partial solution to the problem from PavelPavlov : Add the following entries to the hosts file (the list is updated - now you can download attachments from Google Mail):

173.194.70.132 nt0.ggpht.com
173.194.70.132 nt1.ggpht.com
173.194.70.132 nt2.ggpht.com
173.194.70.132 nt3.ggpht.com
173.194.70.132 lh1.googleusercontent.com
173.194.70.132 lh2.googleusercontent.com
173.194.70.132 lh3.googleusercontent.com
173.194.70.132 lh4.googleusercontent.com
173.194.70.132 lh5.googleusercontent.com
173.194.70.132 lh6.googleusercontent.com
173.194.70.132 lh7.googleusercontent.com
173.194.70.132 image-oz-opensocial.googleusercontent.com
173.194.70.132 images-pos-opensocial.googleusercontent.com
173.194.70.132 images0-focus-opensocial.googleusercontent.com
173.194.70.132 images1-focus-opensocial.googleusercontent.com
173.194.70.132 images2-focus-opensocial.googleusercontent.com
173.194.70.132 images3-focus-opensocial.googleusercontent.com
173.194.70.132 s0.googleusercontent.com
173.194.70.132 s1.googleusercontent.com
173.194.70.132 s2.googleusercontent.com
173.194.70.132 webcache.googleusercontent.com
173.194.70.132 clients0.googleusercontent.com
173.194.70.132 clients1.googleusercontent.com
173.194.70.132 clients2.googleusercontent.com
173.194.70.132 www-tt-opensocial.googleusercontent.com
173.194.70.132 googleusercontent.com
173.194.70.132 images0-focus-opensocial.googleusercontent.com
173.194.70.132 www-gm-opensocial.googleusercontent.com
173.194.70.132 0-focus-opensocial.googleusercontent.com
173.194.70.132 1-focus-opensocial.googleusercontent.com
173.194.70.132 2-focus-opensocial.googleusercontent.com
173.194.70.132 doc-0k-6k-docs.googleusercontent.com
173.194.70.132 doc-2k-6k-docs.googleusercontent.com
173.194.70.132 doc-3k-6k-docs.googleusercontent.com
173.194.70.132 doc-4k-6k-docs.googleusercontent.com
173.194.70.132 doc-5k-6k-docs.googleusercontent.com
173.194.70.132 doc-6k-6k-docs.googleusercontent.com
173.194.70.132 doc-7k-6k-docs.googleusercontent.com
173.194.70.132 doc-8k-6k-docs.googleusercontent.com
173.194.70.132 doc-9k-6k-docs.googleusercontent.com
173.194.70.132 doc-10k-6k-docs.googleusercontent.com
173.194.70.132 mail-attachment.googleusercontent.com
173.194.70.132 lh4.ggpht.com

UPD7: Added 2 more lines to the list of hosts above, for fixing attachments and background image. Do not forget after the withdrawal of IP from under the ban by your provider to return the hosts file to its original state.