3 ms·
This is basically correct. BGP is weird. The addresses for one of Google's many datacenters were routed incorrectly for packets coming from some subset of IP
by amalcon 14y ago
This is basically correct. BGP is weird. The addresses for one of Google's many datacenters were routed incorrectly for packets coming from some subset of IP space. Unless Google is running active ping tests to that subset of IP space, the way they would normally detect it is for someone to call and complain.
In this case, the author decided to take a shortcut and call the owner of the "problem peer" directly.
- veidr 14y agoAlthough only a vanishingly small percentage of Google users can call and complain. Blog or tweet or post to HN and hope Matt Cutts sees it and notifies the right team, maybe.
- mh- 14y ago>Blog or tweet or post to HN and hope Matt Cutts sees it and notifies the right team, maybe. It seems that's more or less the quasi-official support channel even for paid services from Google.
- Matt_Cutts 14y agoA team of Googlers could have been working on this in parallel to Tom. I'm guessing that a sudden drop of queries like that would cause people at Google to start digging into what happened. I don't know either way, because network ops and BGP is pretty far from my area (search quality).
- jauer 14y agoA common way to notice things like this is to subscribe to a service like Renesys or Cyclops (http://cyclops.cs.ucla.edu/ http://cyclops.cs.ucla.edu/) that will alert you if it sees your subnets being announced by a different AS.