“Foreword by Phil Aldridge, Technical Director of FunctionEight Limited. Would this have affected your business? We have clients for whom a 30 minute outage could be the difference between winning or losing a contract. Excessive you may say… but it is the case. As the reliance of corporate mission critical data becomes more and more embedded with the cloud we can expect this type of situation to occur more frequently. You can see here that the issue was not with Google itself but actually with a provider that it uses. For all the users in Asia there were no options but to simply wait for it to rectify.. there was really no-one you can call who could do anything. Do you really want to put your business in that type of position? If not then please email FunctionEight at email@example.com for a consultation on alternative solutions.”
All of Google’s service offerings went offline in some parts of the world during an unusual half-hour outage that mainly affected users in Asia on Tuesday, according to content delivery network provider CloudFlare.
CloudFlare Network Engineer Tom Paseka wrote in an official blog post that the Google Apps services went down at about 2:30 a.m. UTC on Nov 6, and a quick investigation revealed that the search giant’s public DNS server was offline as well.
The first clue came when Paseka saw that an ISP in Indonesia was part of the network path to Google.
“That was curious. Normally, we shouldn’t be seeing an Indonesian ISP (Moratel) in the path to Google. I jumped on one of CloudFlare’s routers to check what was going on,” he wrote.
The root of the problem, according to Paseka, was that Moratel’s network was reporting erroneous data to other service providers, making it seem as though it was hosting addresses that were in fact elsewhere.
“The Indonesian ISP confirmed this wasn’t a configuration issue, but rather unexpected behavior from failed equipment in their network. This sort of issue unfortunately happens a lot across the Internet, though maybe not with as big a view or impact,” he said in an email to Network World.
Most US users shouldn’t have seen an impact, though the problem was likely widely noticed in Asia in general, and Hong Kong in particular, thanks to a popular regional ISP “over-trusting” Moratel.
“The problem was exacerbated by