Google Ping Update

Update: here’s the traceroute when ping performance is 50+ msec:

1 pfsense.nw 1.578 ms
2 * * *
3 * * *
4 tge7-2.ausbtx5202h.texas.rr.com 22.567 ms
5 tge8-5.ausbtx5201h.texas.rr.com 18.703 ms
6 tge0-12-0-6.ausutxla01r.texas.rr.com 15.788 ms
7 agg22.dllatxl301r.texas.rr.com 21.964 ms
8 107.14.17.136 21.865 ms
9 ae1.pr1.dfw10.tbone.rr.com (107.14.17.234)
10 207.86.210.125 (207.86.210.125) 26.794 ms
11 207.88.14.182.ptr.us.xo.net 21.649 ms
12 207.88.14.189.ptr.us.xo.net 17.312 ms
13 ip65-47-204-58.z204-47-65.customer.algx.net 20.543 ms
14 72.14.233.85 24.646 ms
15 72.14.237.219 24.955 ms
16 209.85.243.178 27.354 ms
17 72.14.239.136 43.774 ms
18 216.239.50.237 48.918 ms
19 209.85.243.55 44.747 ms
20 ord08s11-in-f20.1e100.net 43.592 ms

Four extra hops. Hitting a google server presumably somewhere in Chicago instead of Dallas. ORD is the Chicago O’Hare airport code; I don’t really know whether the google data centers are in fact at/near airports or whether they are just using airport codes as a convenient naming scheme for a general area.

So, sometimes I get directed to Dallas, sometimes to Chicago. Will report if I ever see any other server locations.

As an aside, “1e100.net” is google’s clever name for their network.

Leave a Reply

Your email address will not be published. Required fields are marked *