Slashdot Mirror
Google Suffered a Brief Outage on Monday Which Pushed Some of Its Traffic Through Russia, China and Nigeria; Company Says It Will Do an Investigation (cnet.com)
Google suffered a brief outage and slowdown Monday, with some of its traffic getting rerouted through networks in Russia, China and Nigeria. From a report: Incorrect routing instructions sent some of the search giant's traffic to Russian network operator TransTelekom, China Telecom (which, as you may recall, has been found of misdirecting internet traffic in recent months) and Nigerian provider MainOne between 1:00 p.m. and 2:23 p.m. PT, according to internet research group ThousandEyes. "This incident at a minimum caused a massive denial of service to G Suite and Google Search," wrote Ameet Naik, ThousandEyes' technical marketing manager, in a blog post. "However, this also put valuable Google traffic in the hands of ISPs in countries with a long history of Internet surveillance. Applications like Gmail and Google Drive don't appear to have been affected, but YouTube users experienced some slowdown. Google noted that the issue was resolved and said it would conduct an internal investigation. Update: Nigeria's Main One Cable Co has taken responsibility for the glitch.
This is just another in a long string of reasons to slowly back away from google.
Agreed... but to where? Bing search results have become dramatically worse in recent weeks. Yahoo... well, it uses Bing, so say no more. Duck Duck Go? Last time I used it, the results were all over the place.
Finally proof those pesky Russians are hacking the America and it's freedom.
Chinese ? Well... they all the same kind.
...However, this also put valuable Google traffic in the hands of ISPs in countries with a long history of Internet surveillance...
The subtext here is that the USA does not [*cough*] [*cough*], have government funded agencies doing the same. The other day, some government agency was found to be spying on Americans, even when congress [limited] its ability to.
So the summary should have been phrased this way:
Oh, right, all of your important information could be shunted off to your competitors. But that's not a big deal, right?
Look, I help people set up private servers to keep their data out of "the Cloud" but you can't be wrong about the arguments.
Event IF this were a BGP hijack rather than a misconfiguration error and even IF they had minted Google.com certs trusted by the default root stores, Chrome would have picked up the pinned-certificate fingerprint mismatches and refused to connect. Everything in Google's suite happens over TLS.
Yes, this would cause an outage, which costs time and money, but your information does not wind up in the hands of your competitors.
Make technically valid business arguments - don't spout crazy conspiracy theories.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
This is just another in a long string of reasons to slowly back away from google.
If you think this is a google-only problem, you should have your posting rights taken away immediately. This isn't just happening to Google, it's happening to just about everyone. If your traffic isn't encrypted, then this is a great reason to slowly back away from you.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
There is a lesson to be learned in here somewhere, both for you and for grandma.
All traffic between browser and Google is encrypted. I don't see a real security risk here.
He described himself, actually.
Anyhow, it seems too easy to blame Nigeria. Most "Nigerian Princes" were not sending email from Nigeria even. They've been unfairly memeitized. Or is it "memeificated"?
Table-ized A.I.
in the hands of ISPs in countries with a long history of Internet surveillance.
https://en.wikipedia.org/wiki/...
This might be news to some, but the US is a country with a long history of internet surveillance. AT&T maintains an entire room in one of their san francisco datacenters that does nothing but explicitly snoop traffic for the government.
Good people go to bed earlier.
Admittedly a large piece of supposition but how hard would it really be for the PRC and the rest of the usual suspects to convince Google and others to have accidents like this. Google, really, really wants to make RB off of Chinese users and so what if the CPC wanted data in return?
I've started to wonder how useful search engines are anymore since it seems like I invariably end up in the same place 95% of the time. What I probably want most of the time for general knowledge is the Wikipedia article, if it's programming related it's likely to be on Stack Overflow, and for video content I may as well just go straight to YouTube (technically Google anyways, but that's a different argument), and there are a small number of other websites that I frequently end up on after searching for something. It's probably easier to just go to those directly in most cases, but to be fair some of them have awful search (or an utterly fucked site layout with shit navigation) for their own sites so it's just easier to use Google to get to where I want within the site. May as well just buy stuff on Amazon, since the extra hour I might spend searching around to save $.50 just isn't worth my time.
If I'm in a new city and I want to know where to go to eat, it's probably better to just ask a local. Online reviews aren't always that great, and I've eaten at plenty of great little hole in the wall joints that only have one or two reviews total. I think the locals have learned not to review the really good places to keep the tourists away from them. Same goes for other services, where I trust word of mouth or the opinion of someone I know over online reviews.
I still use web search, but I often find myself using queries pretty much designed to give me the Wikipedia page I want instead of just going to Wikipedia to start with. If all web search went down for a week, I might be slightly inconvenienced, but I don't think that my life would be much worse off.
Remind me, which president passed the patriot act? And which president wanted to "close parts of the Internet"? If you think this is a Democrat thing then you really haven't been paying attention.
but to where?
Yacy. If more people use it, it can only get better. And it's very resistant to censorship.
“He’s not deformed, he’s just drunk!”
The headline makes it sound like Google had a brief outage and that caused some traffic to be routed through Russia and China. What actually happened is Some Google Traffic Routed Through Russia and China Causing Brief Outage.
But since we're all used to awful headlines here at Slashdot, and we know we can't expect much better from the original source cnet, that's perfectly fine.
Better known as 318230.
I noticed Google down just as it started and when I checked I found that Spectrum (which still uses rr.com for naming) was sending all Google bound traffic to Tata communications (an Indian Company) which sent it over to Europe on its circuits then Transtelecom in South Africa,which moved it to Chinanet. Traceroute excerpt: 10 0.ae2.pr1.dfw10.tbone.rr.com (107.14.17.236) 66.274 ms 0.ae0.pr1.dfw10.tbone.rr.com (107.14.17.232) 68.537 ms 0.ae4.pr1.dfw10.tbone.rr.com (107.14.19.97) 69.705 ms 11 ix-ae-23-0.tcore2.dt8-dallas.as6453.net (66.110.57.97) 70.130 ms 71.137 ms 70.498 ms 12 if-ae-2-2.tcore1.dt8-dallas.as6453.net (66.110.56.5) 205.871 ms 205.041 ms 207.009 ms 13 if-ae-37-3.tcore1.aeq-ashburn.as6453.net (66.198.154.68) 208.978 ms 207.757 ms 212.871 ms 14 if-ae-2-2.tcore2.aeq-ashburn.as6453.net (216.6.87.1) 211.628 ms 212.403 ms 241.799 ms 15 if-ae-12-2.tcore4.njy-newark.as6453.net (216.6.87.43) 203.197 ms 204.385 ms if-ae-12-2.tcore4.njy-newark.as6453.net (216.6.87.223) 238.450 ms 16 if-ae-1-3.tcore3.njy-newark.as6453.net (216.6.57.5) 234.408 ms 235.627 ms 235.190 ms 17 if-ae-15-2.tcore1.l78-london.as6453.net (80.231.130.25) 239.527 ms 239.084 ms 240.261 ms 18 if-ae-2-2.tcore2.l78-london.as6453.net (80.231.131.1) 240.647 ms 241.425 ms 241.816 ms 19 if-ae-14-2.tcore2.av2-amsterdam.as6453.net (80.231.131.161) 246.783 ms 247.567 ms 246.319 ms 20 if-ae-2-2.tcore1.av2-amsterdam.as6453.net (195.219.194.5) 248.282 ms 167.135 ms 192.261 ms 21 if-ae-6-2.tcore1.fnm-frankfurt.as6453.net (195.219.194.150) 193.772 ms 197.050 ms 200.104 ms 22 195.219.156.146 (195.219.156.146) 213.840 ms 213.268 ms 219.112 ms 23 mskn17ra-lo1.transtelecom.net (217.150.55.21) 271.186 ms 266.862 ms 267.265 ms 24 * * ChinaTelecom-gw.transtelecom.net (217.150.59.249) 280.990 ms 25 * * * 26 * * * 27 * * * 28 * * 154.72.45.166 (154.72.45.166) 466.625 ms There was a period in the middle of that time that Google appeared to be working but traceroute showed everything passing through chinanet and then on to Google, just long latency, but they couldn't keep it up and Google kept going down. There is another article about it at: https://www.dailymail.co.uk/ne... Sorry about the formatting but the /. editor is not accepting my line breaks. Figured the traceroute might be interesting to some even if it looks ugly.