View original thread

---

Q u o t e:


That's just not true. Are you not aware of the problems Optonline and Midcontinent customers have been having too? Come on, there are like 100+ page threads going on for optonline, and you come to tell us this is only a Time Warner problem?

The problem is AT&T's servers in or leading to your Dallas, LA, and Seattle data centers... dozens of dozens of traceroutes i've seen on this board confirm this.

Yes, often the pings aren't crazy to these centers, but you'll still notice they're a lot higher than all other points in the route. They'll look something like this....

1 9ms 192.168.0.1
2 13ms somelocalnet.com
3 23ms somelocalnet.com
4 17ms somelocal net.com
5 82ms server.att.net
6 92ms server.att.net
7 *
8 *
9 *

And it seems from my experience actually trying to play, the latency of any one connection goes up over time.. I'll log on and my ping will be low, then after 2 minutes of playing it will climb to the hundreds, and then in another minute or 2 it will go to thousands. Then I'll dc.

So, i have a feeling all those hundreds of traceroutes that start in the teens and then hits 60 to 100 once it hits ATT servers in Dallas/LA/Seattle you look at and think are 'okay' really show the problem... that 60 to 100 ping on the ATT servers will increase over time the longer a connection is open.

If i do a traceroute to any server in the Dallas, LA, or Seattle data center, the pattern is the same.. low pings, like single digits or the teens, until it hits ATT servers then the pings are in the 60 to 120 range. If i do a trace to the Boston data center, or any other site in the US(google, etc) the pings are usually low with noplace it all of a sudden jumps 10-fold.

---