QFT. I seriously think Google is trying to snag as much of online info as possible to finally, one day, get rid of link-based systems of determining Site Trust/Authority level.
Talk about an end run against web spam, SEO as we currently know it, and their competition.
2 10.148.96-84.rev.gaoland.net (84.96.148.10) 31.428 ms 32.239 ms 31.663 ms
3 29.151.96-84.rev.gaoland.net (84.96.151.29) 31.187 ms 30.935 ms 30.740 ms
4 * * *
5 86-201-118-80.kaptech.net (80.118.201.86) 65.248 ms 72.14.217.1 (72.14.217.1) 234.344 ms 86-201-118-80.kaptech.net (80.118.201.86) 176.411 ms
6 209.85.251.40 (209.85.251.40) 110.609 ms 41.829 ms 41.676 ms
7 209.85.243.111 (209.85.243.111) 53.511 ms 60.526 ms 86.770 ms
8 72.14.236.191 (72.14.236.191) 51.294 ms 209.85.251.231 (209.85.251.231) 51.597 ms 51.674 ms
9 209.85.243.73 (209.85.243.73) 49.541 ms 209.85.243.77 (209.85.243.77) 51.537 ms 50.119 ms
10 google-public-dns-a.google.com (8.8.8.8) 48.518 ms 49.924 ms 51.225 ms
so, fuck knows how they've managed to round-robin their IP cos I've *never* gotten <150ms on a transatlantic hop and yet 209.85.243.73 is in mountain view, CA.
That is insane - it's as quick as my ISP's DNS:
traceroute to 212.30.96.108 (212.30.96.108), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 1.799 ms 1.224 ms 1.270 ms
2 10.148.96-84.rev.gaoland.net (84.96.148.10) 32.612 ms 31.848 ms 37.496 ms
3 29.151.96-84.rev.gaoland.net (84.96.151.29) 31.952 ms 30.929 ms 30.562 ms
4 * * *
5 84.96.243.42 (84.96.243.42) 41.346 ms 42.552 ms 45.091 ms
6 5.155.39-62.rev.gaoland.net (62.39.155.5) 41.635 ms 42.623 ms 41.282 ms
7 V4072.core1.itx.gaoland.net (212.94.161.189) 42.075 ms 41.801 ms 41.352 ms
8 V4075.core1.cbv.gaoland.net (212.94.161.177) 45.126 ms 40.369 ms 42.050 ms
9 9massy1-1-sv-dnscache-1.9tel.net (212.30.96.108) 41.210 ms 42.214 ms 42.418 ms
For coding work - hit me up on andy // borkedcoder // com
(consider figuring out the email as test #1)
All models are wrong, but some are useful.George E.P. Box. p202
so, fuck knows how they've managed to round-robin their IP cos I've *never* gotten <150ms on a transatlantic hop and yet 209.85.243.73 is in mountain view, CA.
They could be doing something unorthodox like routing the same IP block to multiple destinations. BGP routing will generally prefer the fewest hops.
BTW, Mountain View CA is just the administrative address for that block - doesn't mean that traffic necessarily terminates there.
QFT. I seriously think Google is trying to snag as much of online info as possible to finally, one day, get rid of link-based systems of determining Site Trust/Authority level.
Talk about an end run against web spam, SEO as we currently know it, and their competition.
/taking off tinfoil hat
Put it back on, I think there's more to it than just a better search algorithm...
Google's accelerator was a bit of a half-assed flop, DNS is much more simple for the average person to change... and once it's done they'll probably just forget that G is seeing every new site they're connecting to.
Nah, its not that fast... they just advertise the same IP address in multiple places...
That same ip address can be in France, USA, australia, etc.
Originally posted by borked
OK, fuck it, I'm going into beta test mode - that is too damn nuts...
That's from a US server...
compared to a French location:
so, fuck knows how they've managed to round-robin their IP cos I've *never* gotten <150ms on a transatlantic hop and yet 209.85.243.73 is in mountain view, CA.
That is insane - it's as quick as my ISP's DNS:
"Youjizz: Henry, Thanks to you 1 in 150 people online at any given time are jerking off on my websites"
Comment