nanog mailing list archives

Re: lots of latency on qwest to google?


From: PC <paul4004 () gmail com>
Date: Tue, 20 Sep 2011 13:24:55 -0600

You can traceroute from all their POPS here if you'd like:

https://kai02.centurylink.com/PtapRpts/Public/BackboneReport.aspx

Having said that, that IP has similar horrible latency from my non-qwest
connection.  Additionally, google does not resolve to that IP for me, which
is expected.  It does look like poor routing on google's network.  There's
one hop counting for 100 latency, then another adding another 100ms latency,
with little latency increases at other intermediary hops.  I suspect
something heading overseas and back between hop 5-6 and 7-8.

 3. google.com.any2ix.coresite.com
0.0%    97    1.0   4.0   0.7  67.1  12.1
 4.
64.233.174.31
0.0%    97    0.9   7.7   0.8  87.2  19.1
 5.
64.233.174.192
0.0%    97    1.2   1.5   1.0  10.8   1.3
 6.
64.233.174.177
0.0%    96  108.0 113.6 107.8 201.0  13.4
 7.
66.249.94.107
0.0%    96  108.7 113.7 108.4 157.9   9.8
 8.
66.249.94.105
0.0%    96  171.8 175.3 171.6 247.9  12.8
 9.
66.249.94.75
0.0%    96  203.4 204.5 203.1 251.7   6.9
10.
209.85.241.33
0.0%    96  204.7 203.9 203.4 206.6   0.5
11.
74.125.236.52
0.0%    96  204.2 203.8 203.2 204.7   0.4




On Tue, Sep 20, 2011 at 1:06 PM, Chris Brookes <cbrookes () gmail com> wrote:

Anyone else seeing a lot of latency to google via qwest?

..

11     2 ms     2 ms     2 ms  min-edge-12.inet.qwest.net [207.225.128.1]
12    15 ms    13 ms    12 ms  chx-edge-03.inet.qwest.net [67.14.38.5]
13    12 ms    21 ms    13 ms  72.14.214.78
14    13 ms    13 ms    13 ms  72.14.236.178
15    61 ms    61 ms    61 ms  216.239.43.80
16    72 ms    61 ms    62 ms  66.249.94.200
17   152 ms   145 ms   144 ms  216.239.43.213
18   148 ms   149 ms   150 ms  64.233.175.2
19   149 ms   150 ms   149 ms  66.249.94.34
20   212 ms   221 ms   212 ms  66.249.94.105
21   244 ms   244 ms   245 ms  66.249.94.75
22   244 ms   244 ms   244 ms  209.85.241.33
23   244 ms   243 ms   243 ms  74.125.236.52




Current thread: