-
Here is an example of my cable woes. This is a trace route to my primary DNS server. And remember this is on a cable connection that is costing a lot of money, and is happening when I REALY want to play a game. It may not be so bad if it was at least a steady high ping but it goes all over the place most of the time so the game shows way too many laggy effects and the ocational disconnect.
Tracing route to ns1.attbi.com [204.127.198.4]
over a maximum of 30 hops:
1 178 ms 117 ms 158 ms 10.130.96.1
2 87 ms 145 ms 89 ms 12.244.80.1
3 159 ms 110 ms 156 ms 12.244.72.2
4 160 ms 69 ms 163 ms gbr2-p60.st6wa.ip.att.net [12.123.44.118]
5 89 ms 156 ms 183 ms gbr3-p80.st6wa.ip.att.net [12.122.5.165]
6 176 ms 297 ms 227 ms gbr4-p40.sffca.ip.att.net [12.122.2.197]
7 167 ms 130 ms 128 ms gbr3-p60.sffca.ip.att.net [12.122.1.133]
8 328 ms 334 ms 135 ms idf26-gsr12-1-pos-6-0.rwc1.attens.net [12.122.25
5.222]
9 199 ms 225 ms 238 ms rwcsbix12-1-4.attbi.com [63.241.85.246]
10 144 ms 237 ms 193 ms ns1.attbi.com [204.127.198.4]
Trace complete.
Still have not heard back from the email. I guess I need to find some time to call them and start the painful runaround with support and maybe at least get the problem reported.