Jump to content

Google accident 'breaks' the Internet in Japan

WMGroomAK

In a moment of carelessness, Google accidentally took down a large part of the Internet in Japan temporarily and caused a widespread slowing of internet traffic.  According to an Engadget article, Google had set the wrong network information which made it appear as if large chunks of IP Addresses were to be routed through Google instead of the Japanese ISPs they belonged to.  This resulted in the traffic getting redirected to nowhere and caused large delays in service even after the problem was fixed within 8 minutes of occurring.

 

https://www.engadget.com/2017/08/28/google-accidentally-broke-internet-japan/

Quote

Last week, nearly half of Japan briefly lost access to the internet because of an error made by Google. The mistake was noticed and corrected within just a few minutes, but its effects led to hours of slowed internet connections. The impact was so large that Japan's Internal Affairs and Communications Ministry initiated an investigation into the issue.

 

The problem occurred around noon on Friday. A mistake on Google's end made it appear as if a large chunk of IP addresses were available for internet traffic to be routed through Google. However, those IP addresses actually belonged to Japanese internet service providers. So a large amount of traffic that was meant for Japan was suddenly sent towards Google by major internet service providers like Verizon. But Google isn't a service provider and isn't meant to route traffic, so all of that traffic destined for Japan was basically just sent nowhere.

 

Connectivity was restored within the hour, but persistently slow connection speeds resulting from the mistake affected industries like finance, where online trading was halted, and transportation -- East Japan Railway Co. riders weren't able to buy tickets or board trains. The internet service providers impacted the most were KDDI Corp. and NTT Communications, the latter of which provides service to well over seven million people.

 

A Google spokesperson told Asahi Shimbun, "We set wrong information for the network and, as a result, problems occurred. We modified the information to the correct one within eight minutes. We apologize for causing inconvenience and anxieties (among Internet users)."

Seems like a major Oops moment that you would hope they had some kind of checks for, but I guess it's good to know about this potential issue now and maybe find a solution for it... :P

 

EDIT:  Just got around to the Bleeping Computers article, which has a bit more of the technical details on what happened, if not why, who or how...  Basically, Google 'hijacked' about 135,000 network prefixes from around the world, which redirected all of that traffic to Google.  One interesting bit is that the article mentions that this error led to inadvertently broadcasting these prefixes to Verizon who then passed this on down the network...

 

https://www.bleepingcomputer.com/news/technology/google-error-causes-widespread-internet-outage-in-japan/

Quote

According to an analysis by BGPMon, a company part of OpenDNS, part of Cisco, Google hijacked over 135,000 network prefixes, from all over the world, of which over 24,000 belonged to NTT, by far the most affected ISP.

 

"It’s easy to make configuration mistakes that can lead to incidents like this," says Andree Toonk, one of the BGPMon engineers who has analyzed the outage.

 

"In this case it appears a configuration error or software problem in Google's network led to inadvertently announcing thousands of prefixes to Verizon, who in turn propagated the leak to many of its peers," he added.

 

"Since it is easy to make configurations errors, it clearly is a necessity to have filters on both sides of an EBGP session. In this case it appears Verizon had little or no filters, and accepted most if not all BGP announcements from Google which lead to widespread service disruptions," Toonk also said. "At the minimum Verizon should probably have a maximum-prefix limit on their side and perhaps some as-path filters which would have prevented the wide spread impact."

 

 

Edited by WMGroomAK
Additional Article and info
Link to comment
Share on other sites

Link to post
Share on other sites

Yah, there are mechanisms that exist within BGP to prevent this type of thing but that involves actually knowing what you're doing AND how to go about implementing them :P 

Current Network Layout:

Current Build Log/PC:

Prior Build Log/PC:

Link to comment
Share on other sites

Link to post
Share on other sites

Ah good old BGP.....This is a lot more common of an issue than people realize. But I dont know why it took 8 mins to fix, its like a 20 sec fix follow by 30 sec for BGP to fail over..

Link to comment
Share on other sites

Link to post
Share on other sites

2 minutes ago, mynameisjuan said:

Ah good old BGP.....This is a lot more common of an issue than people realize. But I dont know why it took 8 mins to fix, its like a 20 sec fix follow by 30 sec for BGP to fail over..

The 8min could also be the time it took for them to realize they messed up.

if you want to annoy me, then join my teamspeak server ts.benja.cc

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, The Benjamins said:

The 8min could also be the time it took for them to realize they messed up.

I had to do an emergency DNS cut over that took DNS down for 13 secs. In that time we had 43 calls of no internet. And that is for about 10,000 customers. They would of known really really quick lol

Link to comment
Share on other sites

Link to post
Share on other sites

23 minutes ago, valdyrgramr said:

You all laughed at me when I used Bing!  Look who's laughing now!

It's still us laughing at you for using Bing :P 

Current Network Layout:

Current Build Log/PC:

Prior Build Log/PC:

Link to comment
Share on other sites

Link to post
Share on other sites

26 minutes ago, valdyrgramr said:

You all laughed at me when I used Bing!  Look who's laughing now!

Jokes on you, A BGP change means you cannot even reach bing if you are on those IP blocks.

Link to comment
Share on other sites

Link to post
Share on other sites

27 minutes ago, valdyrgramr said:

You all laughed at me when I used Bing!  Look who's laughing now!

I'm still laughing. Use DuckDuckGo.

Spoiler

Quiet Whirl | CPU: AMD Ryzen 7 3700X Cooler: Noctua NH-D15 Mobo: MSI B450 TOMAHAWK MAX RAM: HyperX Fury RGB 32GB (2x16GB) DDR4 3200 Mhz Graphics card: MSI GeForce RTX 2070 SUPER GAMING X TRIO PSU: Corsair RMx Series RM550x Case: Be quiet! Pure Base 600

 

Buffed HPHP ProBook 430 G4 | CPU: Intel Core i3-7100U RAM: 4GB DDR4 2133Mhz GPU: Intel HD 620 SSD: Some 128GB M.2 SATA

 

Retired:

Melting plastic | Lenovo IdeaPad Z580 | CPU: Intel Core i7-3630QM RAM: 8GB DDR3 GPU: nVidia GeForce GTX 640M HDD: Western Digital 1TB

The Roaring Beast | CPU: Intel Core i5 4690 (BCLK @ 104MHz = 4,05GHz) Cooler: Akasa X3 Motherboard: Gigabyte GA-Z97-D3H RAM: Kingston 16GB DDR3 (2x8GB) Graphics card: Gigabyte GTX 970 4GB (Core: +130MHz, Mem: +230MHz) SSHD: Seagate 1TB SSD: Samsung 850 Evo 500GB HHD: WD Red 4TB PSU: Fractal Design Essence 500W Case: Zalman Z11 Plus

 

Link to comment
Share on other sites

Link to post
Share on other sites

2 minutes ago, matrix07012 said:

I'm still laughing. Use DuckDuckGo.

Doesnt Duckduckgo use bing's engine? Just without the telemetry data of course 

Link to comment
Share on other sites

Link to post
Share on other sites

3 minutes ago, mynameisjuan said:

Doesnt Duckduckgo use bing's engine? Just without the telemetry data of course 

No, It's just one of it's sources.

https://duck.co/help/results/sources

Spoiler

Quiet Whirl | CPU: AMD Ryzen 7 3700X Cooler: Noctua NH-D15 Mobo: MSI B450 TOMAHAWK MAX RAM: HyperX Fury RGB 32GB (2x16GB) DDR4 3200 Mhz Graphics card: MSI GeForce RTX 2070 SUPER GAMING X TRIO PSU: Corsair RMx Series RM550x Case: Be quiet! Pure Base 600

 

Buffed HPHP ProBook 430 G4 | CPU: Intel Core i3-7100U RAM: 4GB DDR4 2133Mhz GPU: Intel HD 620 SSD: Some 128GB M.2 SATA

 

Retired:

Melting plastic | Lenovo IdeaPad Z580 | CPU: Intel Core i7-3630QM RAM: 8GB DDR3 GPU: nVidia GeForce GTX 640M HDD: Western Digital 1TB

The Roaring Beast | CPU: Intel Core i5 4690 (BCLK @ 104MHz = 4,05GHz) Cooler: Akasa X3 Motherboard: Gigabyte GA-Z97-D3H RAM: Kingston 16GB DDR3 (2x8GB) Graphics card: Gigabyte GTX 970 4GB (Core: +130MHz, Mem: +230MHz) SSHD: Seagate 1TB SSD: Samsung 850 Evo 500GB HHD: WD Red 4TB PSU: Fractal Design Essence 500W Case: Zalman Z11 Plus

 

Link to comment
Share on other sites

Link to post
Share on other sites

Honestly it seems to me verizon is at fault here... there is no reason to rely so heavily on google's network settings...

Don't ask to ask, just ask... please 🤨

sudo chmod -R 000 /*

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, valdyrgramr said:

Here I am with my internetz and my gift cards.

Don't make me disable your internet :P 

Current Network Layout:

Current Build Log/PC:

Prior Build Log/PC:

Link to comment
Share on other sites

Link to post
Share on other sites

1 minute ago, valdyrgramr said:

Where's your gift cardz m8?

I don't have any ;-;

Current Network Layout:

Current Build Log/PC:

Prior Build Log/PC:

Link to comment
Share on other sites

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×