Post a Comment On: mo.notono.us

Seriously, how can someone as big and distributed as Google have network issues?  (And when my blog is on Google, how can I gripe about it?) This morning’s tracert (and confirmed via a quick twitter search): C:\Users\oskar.austegard>tracert google.com Tracing route to google.com [209.85.171.100] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1] 2 6 ms 4 ms 4 ms xx.xxx.xx.xx 3 6 ms 5 ms 8 ms xxxxxxx.verizon-gni.net [130.81.xxx.xxx] 4 6 ms 8 ms 5 ms so-3-0-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.29.0] 5 8 ms 5 ms 6 ms 0.so-1-2-0.XL3.IAD8.ALTER.NET [152.63.37.117] 6 12 ms 14 ms 7 ms 0.ge-6-0-0.BR2.IAD8.ALTER.NET [152.63.41.149] 7 9 ms 8 ms 9 ms te-11-3-0.edge1.Washington4.level3.net [4.68.63.169] 8 10 ms 16 ms 17 ms vlan69.csw1.Washington1.Level3.net [4.68.17.62] 9 11 ms 9 ms 10 ms ae-62-62.ebr2.Washington1.Level3.net [4.69.134.145] 10 28 ms 35 ms 28 ms ae-2-2.ebr2.Chicago2.Level3.net [4.69.132.69] 11 27 ms 27 ms 29 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113] 12 54 ms 55 ms 54 ms ae-3.ebr2.Denver1.Level3.net [4.69.132.61] 13 103 ms 92 ms 104 ms ae-2.ebr2.Seattle1.Level3.net [4.69.132.53] 14 92 ms 92 ms 92 ms ae-21-52.car1.Seattle1.Level3.net [4.68.105.34] 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 369 ms * * 64.233.174.125 19 * * 285 ms 64.233.174.99 20 * * * Request timed out. 21 375 ms 347 ms * 74.125.30.134 22 * * * Request timed out. 23 * * 350 ms cg-in-f100.google.com [209.85.171.100] Trace complete.