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
On 09/20/2011 03:06 PM, Chris Brookes 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
We are seeing a routing loop at Qwest at one of our sites. 5 ge-5-2-0-0.ATL01-BB-RTR1.verizon-gni.net (130.81.17.115) 16.142 ms 16.093 ms 16.101 ms 6 0.xe-7-1-0.BR3.ATL4.ALTER.NET (152.63.80.73) 16.682 ms 16.254 ms 16.232 ms 7 204.255.168.222 (204.255.168.222) 16.412 ms 22.460 ms 21.343 ms 8 eug-core-02.inet.qwest.net (67.14.32.33) 100.977 ms 99.921 ms 101.427 ms 9 eug-edge-04.inet.qwest.net (205.171.150.38) 99.565 ms 98.840 ms 100.322 ms 10 207.109.242.6 (207.109.242.6) 112.195 ms 110.977 ms 112.466 ms 11 eug-edge-04.inet.qwest.net (207.109.242.5) 110.768 ms 111.701 ms 111.362 ms 12 207.109.242.6 (207.109.242.6) 117.494 ms 113.060 ms 113.308 ms 13 eug-edge-04.inet.qwest.net (207.109.242.5) 120.939 ms 120.411 ms 119.971 ms 14 207.109.242.6 (207.109.242.6) 125.842 ms 122.599 ms 122.036 ms 15 eug-edge-04.inet.qwest.net (207.109.242.5) 120.446 ms 118.881 ms 119.204 ms 16 207.109.242.6 (207.109.242.6) 125.540 ms 125.478 ms 138.716 ms 17 eug-edge-04.inet.qwest.net (207.109.242.5) 138.225 ms 132.476 ms 131.683 ms 18 207.109.242.6 (207.109.242.6) 141.288 ms 142.909 ms 150.655 ms 19 eug-edge-04.inet.qwest.net (207.109.242.5) 148.538 ms 148.713 ms 148.130 ms 20 207.109.242.6 (207.109.242.6) 156.247 ms 152.812 ms 155.129 ms 21 eug-edge-04.inet.qwest.net (207.109.242.5) 156.888 ms 158.048 ms 156.072 ms 22 207.109.242.6 (207.109.242.6) 165.790 ms 165.101 ms 168.350 ms 23 eug-edge-04.inet.qwest.net (207.109.242.5) 166.783 ms 167.106 ms 165.928 ms 24 207.109.242.6 (207.109.242.6) 175.051 ms 176.857 ms 175.693 ms 25 eug-edge-04.inet.qwest.net (207.109.242.5) 176.788 ms 176.379 ms 175.867 ms 26 207.109.242.6 (207.109.242.6) 184.702 ms 184.590 ms 186.183 ms 27 eug-edge-04.inet.qwest.net (207.109.242.5) 186.509 ms 187.398 ms 185.913 ms 28 207.109.242.6 (207.109.242.6) 194.984 ms 196.161 ms 195.821 ms 29 eug-edge-04.inet.qwest.net (207.109.242.5) 196.193 ms 195.687 ms 196.331 ms 30 207.109.242.6 (207.109.242.6) 205.271 ms 205.732 ms 205.718 ms -- Stephen Clark *NetWolves* Sr. Software Engineer III Phone: 813-579-3200 Fax: 813-882-0209 Email: steve.clark@netwolves.com http://www.netwolves.com
On Tue, Sep 20, 2011 at 02:06:18PM -0500, Chris Brookes 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 The above address is is in Google IP space 14 13 ms 13 ms 13 ms 72.14.236.178 The above address is is in Google IP space 15 61 ms 61 ms 61 ms 216.239.43.80 The above address is is in Google IP space 16 72 ms 61 ms 62 ms 66.249.94.200 The above address is is in Google IP space 17 152 ms 145 ms 144 ms 216.239.43.213 The above address is is in Google IP space 18 148 ms 149 ms 150 ms 64.233.175.2 The above address is is in Google IP space 19 149 ms 150 ms 149 ms 66.249.94.34 The above address is is in Google IP space 20 212 ms 221 ms 212 ms 66.249.94.105 The above address is is in Google IP space 21 244 ms 244 ms 245 ms 66.249.94.75 The above address is is in Google IP space 22 244 ms 244 ms 244 ms 209.85.241.33 The above address is is in Google IP space 23 244 ms 243 ms 243 ms 74.125.236.52 The above address is is in Google IP space
Looks to me like the latency from Qwest to Google (chx-edge-03.inet.qwest.net [67.14.38.5] to 72.14.214.78) is quite tolerable, but the delay(s) inside Google are a tad bit high. I see much the same thing from work and from home to 74.125.236.52. As soon as I jump from my provider's upstream (Qwest at work, Cox at home) to Google, the times go up sharply along the route to 74.125.236.52. -- Mike Andrews, W5EGO mikea@mikea.ath.cx Tired old sysadmin
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
On 20 September 2011 14:24, PC <paul4004@gmail.com> wrote:
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
I mentioned qwest because when I checked via another path (HE) it was fine. Does appear to be a google issue, I guess, based on further testing. Ho hum..
participants (4)
-
Chris Brookes -
mikea -
PC -
Steve Clark