bigbearr
join:2003-11-16
Saint Louis, MO
| K, unfortunatly I missread the post and thought that you were in my area, but I have done some investigating and cameron119 is correct, the issue is related to ATT service.
We can detect this by doing as Sparky had suggested and I can traceroute to the IP provided and notice that the ATT hop is the problem.
When TWGandalf posted his traceroute, it shows that its almost the same IP causing the issue. Its off by 1 number.
1,10.16.x.x,9ms,None,----
2,24.217.x.x,15ms,charter-stl.com,----
3,24.217.63.193,16ms,None,----
4,12.124.129.97,14ms,None,----
5,12.123.25.30,17ms,gbr6-p40.sl9mo.ip.att.net,----
6,12.122.11.125,19ms,tbr2-p013601.sl9mo.ip.att.net,----
7,12.122.10.90,36ms,tbr2-cl6.dlstx.ip.att.net,----
8,12.122.9.161,28ms,tbr1-p013601.dlstx.ip.att.net,----
9,12.122.2.90,42ms,tbr2-cl1.attga.ip.att.net,----
10,12.122.12.34,43ms,gbr1-p20.attga.ip.att.net,----
11,12.123.21.1,42ms,gar1-p360.attga.ip.att.net,----
12,12.124.59.114,210ms,None,----
13,24.158.96.230,211ms,gw-swc2kngtn.chartertn.net,----
14,24.158.109.161,213ms,gw-cr1kngtn.chartertn.net,---- |
bigbearr, would you please run a tracert to 24.158.109.161 and post results.