dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
share rss forum feed


Simba7
I Void Warranties

join:2003-03-24
Billings, MT
reply to koolkid1563

Re: Time outs at the exact same spot everytime

Why is it bouncing through at&t's backbone?


koolkid1563
Premium,MVM
join:2005-11-06
Powell, WY
Beats me. It goes to Nashville, TN then to Atlanta, GA to get to Google's servers there when CA via Google's Seattle PoP would be far closer both logically and physically...Especially since that is where Bresnan already built out to but I suspect ATT doesn't have a peering relationship with Google's PoP in Seattle. If it goes through Bresnan's Denver route (Lvl3) it goes to Google through Dallas.

TCT

traceroute to google.com (72.14.213.147), 30 hops max, 38 byte packets
1 sub-96-31-116-2.tctwest.net (96.31.116.2) 1.596 ms 7.131 ms 4.831 ms
2 sub-96-31-116-1.tctwest.net (96.31.116.1) 1.378 ms 0.991 ms 1.901 ms
3 brln-7606-t1-2.tctwest.net (72.21.79.189) 2.593 ms 1.957 ms 1.861 ms
4 blns-7606-g5-1.tctwest.net (67.215.22.42) 5.509 ms 5.748 ms 5.986 ms
5 209-193-109-252.mammothnetworks.com (209.193.109.252) 16.226 ms 16.141 ms 15.416 ms
6 VCN-SEA-1000M.demarc.spectrumnet.us (208.76.153.226) 36.507 ms 33.247 ms 34.464 ms
7 google-sttlwa-core-01.mammothnetworks.com (68.170.55.134) 47.391 ms 47.172 ms 46.519 ms
8 209.85.249.32 (209.85.249.32) 47.745 ms 46.997 ms 49.072 ms
9 66.249.94.199 (66.249.94.199) 47.927 ms 66.249.94.197 (66.249.94.197) 47.644 ms 66.249.94.201 (66.249.94.201) 60.372 ms
10 216.239.46.200 (216.239.46.200) 51.142 ms 50.831 ms 51.070 ms
11 64.233.174.99 (64.233.174.99) 50.925 ms 64.233.174.101 (64.233.174.101) 50.769 ms 216.239.48.141 (216.239.48.141) 53.442 ms
12 209.85.253.6 (209.85.253.6) 59.428 ms 209.85.253.2 (209.85.253.2) 50.861 ms 209.85.253.10 (209.85.253.10) 56.732 ms
13 pv-in-f147.1e100.net (72.14.213.147) 50.818 ms 51.018 ms 51.724 ms