Re: [TWC] Any ideas, how to get this lag fixed? (again) in Road Runner

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Mon, 26 May 2008 00:12:48 EDT

said by Karsh :

I'm having the same issues while playing on tichondrius. 300-500 ping usually.

game sever issues

good luck

Hob
--
"A foolish consistency is the hobgoblin of little minds."
- Ralph Waldo Emerson

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Sun, 25 May 2008 23:34:05 EDT

anon : I'm having the same issues while playing on tichondrius. 300-500 ping usually.

Tracing route to 12-129-225-110.attens.net [12.129.225.110]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.1.1
2 39 ms 36 ms 25 ms 10.52.0.1
3 21 ms 23 ms 20 ms gig-2-0-nycmnyp-rtr1.nj.rr.com [24.168.128.17]
4 28 ms 29 ms 33 ms gig-0-2-nycmnyp-ubr7.nj.rr.com [24.168.128.182]

5 31 ms 30 ms 33 ms gig-0-2-nycmnyp-ubr12.nj.rr.com [24.168.128.186]

6 26 ms 23 ms 29 ms gig-0-3-nycmnyp-ubr8.nj.rr.com [24.168.128.206]

7 24 ms 28 ms 26 ms gig-2-3-nycmnyp-rtr2.nj.rr.com [24.168.128.190]

8 29 ms 23 ms 22 ms pos-3-0-nycmnyc-rtr1.nyc.rr.com [24.29.101.245]

9 * * 29 ms tengig-2-0-0-nycmnyrdc-rtr2.nyc.rr.com [24.29.11
9.142]
10 24 ms 29 ms 23 ms tenge-0-0-0-nycsnyoo-rtr1.nyc.rr.com [24.29.119.
102]
11 29 ms 28 ms 30 ms te-4-1.car3.NewYork1.Level3.net [4.78.182.45]
12 * 34 ms 29 ms ggr2-p360.n54ny.ip.att.net [192.205.33.93]
13 189 ms 187 ms 188 ms tbr1.n54ny.ip.att.net [12.123.0.90]
14 176 ms 201 ms 213 ms cr2.n54ny.ip.att.net [12.122.16.141]
15 186 ms 179 ms 184 ms cr2.wswdc.ip.att.net [12.122.3.38]
16 180 ms * 192 ms cr1.attga.ip.att.net [12.122.1.173]
17 199 ms 197 ms 192 ms cr2.dlstx.ip.att.net [12.122.28.174]
18 192 ms 194 ms 202 ms cr2.la2ca.ip.att.net [12.122.28.178]
19 198 ms * 198 ms tbr2.la2ca.ip.att.net [12.122.19.230]
20 208 ms 208 ms 194 ms 12.127.3.189
21 184 ms 188 ms 198 ms 12.122.255.74
22 193 ms 209 ms 209 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Thu, 22 May 2008 08:50:10 EDT

Gts : Thanks again KP for the response. I've emailed Blizzard, telling them this issue. And they keep telling me to contact my ISP. I dunno what else to do anymore, is there something else i could try?

thanks again.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Thu, 22 May 2008 08:15:08 EDT

K Patterson : LA via DC, Atlanta and Dallas in 100ms is not bad. The large lag at 12.129.193.242 may or may not be ATT's problem. My guess is that the router belongs to the gaming folks and that the problem is that they have purchased inadequate bandwidth for the demand.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Thu, 22 May 2008 07:58:45 EDT

Gts : Still having issues. I'm pulling my hair out =(

Tracing route to 12.129.233.47 over a maximum of 30 hops1    <1 ms    <1 ms    <1 ms  192.168.1.12     6 ms     7 ms     5 ms  10.65.96.13     5 ms     5 ms     5 ms  gig3-0-nycmnyw-rtr1.nyc.rr.com [24.29.101.69]4     7 ms     5 ms     5 ms  pos-6-2-nycmnyrdc-rtr1.nyc.rr.com [24.29.119.29] 5     9 ms     7 ms     8 ms  tenge-0-0-0-nwrknjmd-rtr.nyc.rr.com [24.29.119.94]6     7 ms    19 ms    27 ms  4.79.188.377    15 ms    17 ms    17 ms  ae-31-53.ebr1.Newark1.Level3.net [4.68.99.94]8    19 ms    17 ms    18 ms  ae-2.ebr1.NewYork1.Level3.net [4.69.132.97]9    19 ms    18 ms    17 ms  ae-71-71.csw2.NewYork1.Level3.net [4.69.134.70] 10     7 ms     7 ms    12 ms  ae-23-79.car3.NewYork1.Level3.net [4.68.16.69]11     7 ms     7 ms     9 ms  att-level3-oc192.NewYork1.Level3.net [4.68.127.150]12   114 ms   111 ms   111 ms  tbr2.n54ny.ip.att.net [12.123.0.94]13   111 ms   113 ms   111 ms  cr2.n54ny.ip.att.net [12.122.16.205]14   110 ms   114 ms   112 ms  cr2.wswdc.ip.att.net [12.122.3.38]15   112 ms   111 ms   112 ms  cr1.attga.ip.att.net [12.122.1.173]16   112 ms   112 ms   114 ms  cr2.dlstx.ip.att.net [12.122.28.174]17   111 ms   113 ms   117 ms  cr2.la2ca.ip.att.net [12.122.28.178]18   111 ms   117 ms   112 ms  tbr2.la2ca.ip.att.net [12.122.19.222]19   110 ms   111 ms   111 ms  12.127.3.18920   112 ms   111 ms   111 ms  12.122.255.7421   113 ms   111 ms   113 ms  mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242]

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Sun, 11 May 2008 06:45:35 EDT

Gts : thanks for the info KP. Im emailing back and fourth with their tech department. They're telling me like usual, my ISP needs to be contacted because its a peering issue with them and Level3, and level3 than has to contact ATT. They're taking zero responsibilty in this.

I've contacted ATT, Level3 and RR. All 3 tell me 3 different things, and im just at a lost now =/

thanks again KP!
--
The more you talk, the less you listen.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Sat, 10 May 2008 18:52:50 EDT

K Patterson : Actually, those 100 ms times are not too bad. What is happening is that the route back to you is via California, starting with the first ATT router with high ping times. If that were not the case, you would see a progressive increase in the latency as you went from NY to Washingto to Dallas, etc. The minimum possible latency for that path is around 50 ms.

The final router, mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242], is not an ATT router. It belongs to the gaming company or their ISP. It is assigned an ATT IP because it has to be on the same subnet as the outgoing port of the preceeding router. The big jump in latency there suggest that ATT's customer has not purchased adequate bandwidth.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Sat, 10 May 2008 17:00:40 EDT

Smith6612 : For Reference as well, here's what I'm getting on Frontier DSL as well, a connection almost 3 miles away from my house (which has the Verizon connection I ran a traceroute on before to the same location).

Tracing route to 12.129.233.110 over a maximum of 30 hops   1     1 ms     1 ms     1 ms  192.168.1.1  2     1 ms     1 ms     1 ms  192.168.254.254  3    13 ms    13 ms    14 ms  dsl1.hol.ny.frontiernet.net [70.98.90.254]  4    16 ms    16 ms    16 ms  at-1-3-0--132.gw03.roch.eli.net [70.98.90.253]  5    16 ms    17 ms    17 ms  ge-1-0-0--0.cr01.roch.ny.frontiernet.net [74.40.4.225]  6    24 ms    23 ms    23 ms  so-0-0-0--0.cr01.nwrk.nj.frontiernet.net [74.40.3.233]  7    25 ms    25 ms    27 ms  so-3-0-0--0.cr02.nwrk.nj.frontiernet.net [74.40.3.202]  8    30 ms    30 ms    32 ms  so-0-0-0--0.cr02.mcln.va.frontiernet.net [74.40.3.253]  9    32 ms    33 ms    35 ms  so-3-0-0--0.br01.asbn.va.frontiernet.net [74.40.4.110] 10    34 ms    32 ms    37 ms  12.118.132.33 11   102 ms   101 ms   101 ms  tbr2.wswdc.ip.att.net [12.123.8.46] 12   101 ms   101 ms   101 ms  cr2.wswdc.ip.att.net [12.122.16.77] 13   101 ms   103 ms   101 ms  cr1.attga.ip.att.net [12.122.1.173] 14   103 ms   101 ms   107 ms  cr2.dlstx.ip.att.net [12.122.28.174] 15   101 ms   100 ms   100 ms  cr2.la2ca.ip.att.net [12.122.28.178] 16   103 ms   103 ms   100 ms  tbr2.la2ca.ip.att.net [12.122.19.222] 17   102 ms   101 ms   100 ms  12.127.3.189 18   100 ms   101 ms   100 ms  12.122.255.74 19   318 ms   221 ms   207 ms  mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242] 20    Time outs...

Again, it's nearly the same spot as my Verizon connection, nd AT&T hop, as Frontier and Verizon appear to be possibly taking the same routes, while Frontier is taking a path through a different router. If the first router itself is fine, but the next hop after the AT&T router is where the lag starts, it's got to be a router that's under load. So yes, AT&T problem. Here's more to add if you'd like it.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Thu, 08 May 2008 20:45:36 EDT

Gts : the realm is boulderfist. I've also tried playing on a closer server in boston, and once i hit the first hop on any ATT network, my latency jumps from 10-20ms to 150+ during primetime.

att was sent a bunch of tracerts, and they still stick to having blizzard contacting them. Blizzard is saying its my ISP and i should have them forward it to ATT.

dunno anymore.
--
The more you talk, the less you listen.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Thu, 08 May 2008 18:37:21 EDT

Smith6612 : Here's my trace route on my DSL.

tracert 12.129.233.110 Tracing route to 12.129.233.110 over a maximum of 30 hops   1   <10 ms   <10 ms   <10 ms  WRT54GX [192.168.2.1]  2     1 ms     1 ms     1 ms  Fedorabox [192.168.1.1]  3     8 ms     8 ms     9 ms  10.15.3.1  4    10 ms    13 ms    12 ms  so-1-1-0-0.CORE-RTR2.****.verizon-gni.net [130.**.**.**]  5    15 ms    17 ms    16 ms  130.81.20.106  6    20 ms    20 ms    23 ms  0.so-3-1-0.XT1.NYC8.ALTER.NET [152.63.10.33]  7    20 ms    23 ms    21 ms  0.so-6-3-0.XL3.NYC4.ALTER.NET [152.63.0.69]  8    27 ms    29 ms    28 ms  0.ge-4-2-0.BR3.NYC4.ALTER.NET [152.63.3.126]  9    27 ms    28 ms    29 ms  192.205.34.49 (AT&T Hop) 10   109 ms   107 ms   108 ms  tbr1.n54ny.ip.att.net [12.122.105.46] 11   109 ms   107 ms   107 ms  cr2.n54ny.ip.att.net [12.122.16.133] 12   109 ms   107 ms   108 ms  cr2.wswdc.ip.att.net [12.122.3.38] 13   110 ms   109 ms   111 ms  cr1.attga.ip.att.net [12.122.1.173] 14   107 ms   105 ms   108 ms  cr2.dlstx.ip.att.net[12.122.28.174] 15   107 ms   109 ms   107 ms  cr2.la2ca.ip.att.net [12.122.28.178] 16   110 ms   108 ms   107 ms  tbr2.la2ca.ip.att.net [12.122.19.198] 17   102 ms   103 ms   102 ms  12.127.3.189 18   106 ms   108 ms   108 ms  12.122.255.74 19   105 ms   105 ms   105 ms  mdf001c7613r0003-gig-10-1.lax1.attens.net [12.129.193.242] 20     *        *        *     Request timed out.

After hop 20, everything else times out. Hope this helps.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Thu, 08 May 2008 07:40:28 EDT

dadarkside : What World of Warcraft realm is this?
Is there a thread at »forums.worldofwarcraft.com/board···10&sid=1

I'm certain other players are experiencing this. There is strength in numbers you know.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Thu, 08 May 2008 04:42:31 EDT

NormanS : Unlike you, I don't see the latency spike until well into the AT&T Worldnet Services (ATTW) transit network:
Southern California does not, normally, show very high latency from the S.F. Bay Area:

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Wed, 07 May 2008 20:28:06 EDT

Gts : sure post it, i will send in a email tonight.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Wed, 07 May 2008 20:15:45 EDT

Smith6612 : I'm not a Roadrunner user, I am a Verizon DSL user, but if you guys would like for e-mail trace routes to AT&T, I can give you guys my trace route. I am seeing the same lagging problem when trace routing to that server on AT&T's network on the same hop as well. I do game myself on Blizzard's servers every now and again and have noticed some lagging lately. Just in case if you guys want them.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Wed, 07 May 2008 20:11:46 EDT

Lowtarget : Try sending a tracert to ATT about it. Looks like thats your only choice I hate to say.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Wed, 07 May 2008 19:33:26 EDT

Gts : Since posting this, the issue has gotten much worse. I am at wits end here =( anything else i can possibly do?

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Thu, 01 May 2008 11:11:54 EDT

Gts : You're right K Patterson, ATT will not take any of my calls, or emails. They asked me to have blizzard contact them directly and open a ticket. But this has been going on for 2 weeks already, and its driving me nuts.

Darkside, blizzard wont run a reverse tracert to my location, all they keep telling me is to contact my ISP. They repeat this over and over again.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Thu, 01 May 2008 09:46:34 EDT

dadarkside : What does an end to end ping look like?

(Traceroute is not the best choice to diagnose network congestion, it should always be used in association with end to end ping testing)

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Thu, 01 May 2008 05:57:11 EDT

K Patterson : No good ideas. Unfortunately, neither you nor Road Runner have any standing to ask a company to correct a problem when you aren't a customer. If ATT wants to tolerate poor latency, that is their choice.

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Wed, 30 Apr 2008 19:36:45 EDT

Gts : another night, bad latency =/

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Tue, 29 Apr 2008 21:00:01 EDT

Gts : att? because i just got a support number, and i dont have a customer number lol =(

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Tue, 29 Apr 2008 20:58:38 EDT

punker : tell them the lag is on there network

Re: [TWC] Any ideas, how to get this lag fixed? (again)

Tue, 29 Apr 2008 20:53:34 EDT

Gts : i contacted ATT and Blizzard, both of them told me its my ISP. I called road runner, they said the problem is with ATT, and i need to have blizzard contact them =/

any ideas?

[TWC] Any ideas, how to get this lag fixed? (again)

Tue, 29 Apr 2008 20:52:47 EDT

Gts : Tracing route to 12.129.233.110 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 192.168.1.1
2 7 ms 9 ms 7 ms 10.65.96.1
3 8 ms 6 ms 13 ms gig3-0-nycmnyw-rtr1.nyc.rr.com [24.29.101.69]
4 15 ms 6 ms 8 ms pos-6-2-nycmnyrdc-rtr1.nyc.rr.com [24.29.119.29]

5 9 ms 10 ms 12 ms gig1-0-0-nwrknjmd-rtr1.nyc.rr.com [24.29.130.182
]
6 7 ms 7 ms 9 ms 4.79.188.37
7 16 ms 18 ms 17 ms ae-32-54.ebr2.Newark1.Level3.net [4.68.99.126]
8 9 ms 18 ms 18 ms ae-1-100.ebr1.Newark1.Level3.net [4.69.132.21]
9 12 ms 17 ms 18 ms ae-2.ebr1.NewYork1.Level3.net [4.69.132.97]
10 20 ms 18 ms 17 ms ae-81-81.csw3.NewYork1.Level3.net [4.69.134.74]

11 10 ms 9 ms 9 ms ae-33-89.car3.NewYork1.Level3.net [4.68.16.133]

12 20 ms 9 ms 27 ms ggr2-p360.n54ny.ip.att.net [192.205.33.93]
13 385 ms 385 ms 289 ms tbr1.n54ny.ip.att.net [12.123.3.106]
14 288 ms 386 ms 292 ms cr2.n54ny.ip.att.net [12.122.16.149]
15 488 ms 288 ms 192 ms cr2.wswdc.ip.att.net [12.122.3.38]
16 198 ms 186 ms 181 ms tbr1.wswdc.ip.att.net [12.122.16.6]
17 180 ms 178 ms 177 ms tbr1.sl9mo.ip.att.net [12.122.10.30]
18 188 ms 180 ms 179 ms tbr2.sl9mo.ip.att.net [12.122.9.142]
19 177 ms 172 ms 170 ms tbr2.la2ca.ip.att.net [12.122.10.14]
20 188 ms 191 ms 189 ms 12.127.3.189
21 262 ms 203 ms 202 ms 12.122.255.74
22 482 ms 380 ms 484 ms mdf001c7613r0003-gig-10-1.lax1.attens.net [12.12
9.193.242]
--
Dr. Ron Paul 2008
God is my co-pilot, but the Devil is my bombardier! -Anon-