High Latency related to Battlegroup?

(Locked)

90 Blood Elf Mage
9530
I'm on ATT and still get lag issues..been having them for almost 2 weeks now...
90 Undead Rogue
6340
Yeah...AT&T is fine some nights and other nights its just bad. I have Comcast but something happens to the signal when it hits the AT&T network.

Traceroute has started…

traceroute to 12.129.209.68 (12.129.209.68), 64 hops max, 72 byte packets
1 10.0.1.1 (10.0.1.1) 0.516 ms 0.235 ms 0.141 ms
2 69.253.48.1 (69.253.48.1) 22.914 ms 16.321 ms 25.257 ms
3 xe-10-2-0-32767-sur01.torresdale.pa.panjde.comcast.net (68.85.78.185) 8.721 ms 9.894 ms 9.200 ms
4 xe-6-1-3-0-ar03.norristown.pa.panjde.comcast.net (69.139.192.85) 10.340 ms 9.129 ms 9.754 ms
5 ae-1-0-ar03.ivyland.pa.panjde.comcast.net (69.139.193.245) 32.668 ms 10.773 ms
so-6-0-0-0-ar03.ivyland.pa.panjde.comcast.net (68.86.211.49) 10.649 ms
6 pos-3-12-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.95.161) 16.866 ms
pos-3-14-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.95.169) 14.106 ms
pos-3-15-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.95.1) 17.403 ms
7 pos-1-4-0-0-pe01.111eighthave.ny.ibone.comcast.net (68.86.86.194) 15.449 ms 14.607 ms 13.229 ms
8 192.205.37.33 (192.205.37.33) 15.847 ms 14.903 ms 15.707 ms
9 cr1.n54ny.ip.att.net (12.122.131.86) 86.569 ms 83.708 ms 84.167 ms
10 cr2.cgcil.ip.att.net (12.122.1.2) 82.336 ms 85.237 ms 83.487 ms
11 cr1.cgcil.ip.att.net (12.122.2.53) 84.728 ms 83.739 ms 85.158 ms
12 cr2.dvmco.ip.att.net (12.122.31.85) 83.318 ms 83.438 ms 84.556 ms
13 cr1.slkut.ip.att.net (12.122.30.25) 83.212 ms 83.751 ms 82.683 ms
14 cr2.la2ca.ip.att.net (12.122.30.30) 83.508 ms 473.287 ms 82.524 ms
15 gar29.la2ca.ip.att.net (12.122.129.241) 81.673 ms 80.231 ms 80.651 ms
16 12-122-254-234.attens.net (12.122.254.234) 82.027 ms
12-122-254-238.attens.net (12.122.254.238) 82.220 ms 81.800 ms
17 mdf001c7613r0002.lax1.attens.net (206.16.68.54) 81.390 ms 82.194 ms 80.804 ms
18 *
Edited by Drakthul on 2/14/2013 6:15 PM PST
90 Tauren Druid
0
wow is pretty much hopeless for me right now and i have lost good raiders and guild members and my guild is dieing even after i transfered to a different battle group with out problems. it eventually found us again and is killing us
90 Night Elf Priest
13255
Shaw Cable
Going on 5th week of nightly massive lag

Tracing route to mdf1-bi8k-1-ve-87.phx1.attens.net [63.241.138.161]

over a maximum of 30 hops:

1 1 ms <1 ms <1 ms KENTEL [192.168.1.1]

2 16 ms 12 ms 18 ms 24.67.24.1

3 10 ms 23 ms 12 ms rd1ht-ge3-6-1.ok.shawcable.net [64.59.172.67]

4 14 ms 26 ms 15 ms rd2ht-tge2-1.ok.shawcable.net [66.163.72.162]

5 32 ms 35 ms 35 ms 66.163.76.50

6 28 ms 26 ms 33 ms 66.163.74.142

7 40 ms 29 ms 39 ms xe-11-0-0.edge1.Seattle3.Level3.net [4.59.232.85]

8 46 ms 41 ms 49 ms 192.205.36.153

9 84 ms 141 ms 438 ms cr1.st6wa.ip.att.net [12.122.146.50]

10 439 ms 157 ms 72 ms cr2.sffca.ip.att.net [12.122.31.194]

11 81 ms 89 ms 99 ms cr1.sffca.ip.att.net [12.122.3.69]

12 98 ms 79 ms 79 ms cr1.la2ca.ip.att.net [12.122.3.122]

13 78 ms 79 ms 79 ms cr2.phmaz.ip.att.net [12.122.31.190]

14 168 ms 69 ms 79 ms 12.123.158.133

15 79 ms 78 ms 86 ms 12-122-254-50.attens.net [12.122.254.50]

16 89 ms 70 ms 77 ms mdf002c7613r0002-gig-10-1.phx1.attens.net [63.241.130.206]

17 * * * Request timed out.

18 * * * Request timed out.

19 * * * Request timed out.

20 * * * Request timed out.

21 * * * Request timed out.

22 * * * Request timed out.

23 * * * Request timed out.

24 * * * Request timed out.

25 * * * Request timed out.

26 * * * Request timed out.

27 * * * Request timed out.

28 * * * Request timed out.

29 * * * Request timed out.

30 * * * Request timed out.

Trace complete.

90 Undead Rogue
11250
Haven't been on in like 3 weeks. my account expires soon so i just come here to see if this thread is still active and if it's even worth logging in. guess not.
90 Orc Hunter
11410
cogentco still gone, but lag problem is persisting

Tracing route to 206.18.98.185.tms-idc.com [206.18.98.185]
over a maximum of 30 hops:

1 33 ms 32 ms 34 ms 254-198-137-216.mtaonline.net [216.137.198.254]
2 30 ms 32 ms 35 ms 6506-1-er-po2.mtaonline.net [216.152.176.205]
3 32 ms 31 ms 43 ms 7606-1-er-ge1-1-3.mtaonline.net [216.152.176.133]
4 32 ms 31 ms 31 ms gi2-0-1268-cr15.nwc.acsalaska.net [69.162.209.129]
5 67 ms 65 ms 69 ms xe-11-1-0-r2.nwc.acsalaska.net [63.140.116.8]
6 68 ms 75 ms 65 ms xe-0-0-0-r2.sea.acsalaska.net [63.140.116.67]
7 65 ms 70 ms 66 ms xe-0-4-0-2.r05.sttlwa01.us.bb.gin.ntt.net [198.104.202.145]
8 66 ms 67 ms 72 ms ae-3.r04.sttlwa01.us.bb.gin.ntt.net [129.250.5.50]
9 66 ms 64 ms 62 ms 192.205.34.117
10 113 ms 143 ms 116 ms cr81.st0wa.ip.att.net [12.122.82.254]
11 113 ms 121 ms 114 ms cr2.st6wa.ip.att.net [12.122.5.198]
12 117 ms 121 ms 121 ms cr2.cgcil.ip.att.net [12.122.31.129]
13 147 ms 192 ms 112 ms gar3.cgcil.ip.att.net [12.122.132.213]
14 114 ms 115 ms 114 ms 12.122.251.22
15 116 ms 112 ms 111 ms 63.240.130.210
90 Human Rogue
14405
Alright I'm up here in BC using the Telus ISP the cogent node finally disappears from my tracert then I get this

Tracing route to 206.18.148.1 over a maximum of 30 hops

1 1 ms 1 ms <1 ms 192.168.0.1
2 154 ms 102 ms 56 ms dnsplaceholder.abccomm.com [208.181.70.126]
3 107 ms 87 ms 110 ms 10.188.128.201
4 194 ms 215 ms 158 ms ABCPGRGBC4A-S02-VL902.net.abccomm.com [10.188.128.12]
5 160 ms 443 ms 274 ms host129.204.108.206.in-addr.arpa [206.108.204.129]
6 230 ms 178 ms 140 ms 154.11.89.129
7 390 ms 260 ms 312 ms 75.154.216.250
8 86 ms 67 ms 80 ms 208.173.49.17
9 435 ms 223 ms 137 ms esr2-xe-11-1-0.ssd.savvis.net [204.70.224.30]
10 28 ms 25 ms 23 ms 208.173.48.18
11 218 ms 95 ms 121 ms cr81.st0wa.ip.att.net [12.122.82.254]
12 354 ms 135 ms 92 ms cr2.st6wa.ip.att.net [12.122.5.198]
13 242 ms 231 ms 427 ms cr2.cgcil.ip.att.net [12.122.31.129]
14 303 ms 322 ms 234 ms gar3.cgcil.ip.att.net [12.122.132.213]
15 190 ms 409 ms 386 ms 12.122.251.50
16 206 ms 189 ms 192 ms 63.240.130.210
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
It falls apart at the att network so it wasnt only cogent with a problem, its just they were masking att's problem quite well until we got rerouted now att's system is freaking the hell out.
90 Orc Hunter
11410
i see a few posts now stating that even with cogent gone they are still having issues when hitting att, we just moved from 1 problem to the next, first took over a month to fix, wonder how long this one will take.
90 Blood Elf Priest
17120
Back again, just wanted to report that I'm starting to see high latency again. Its no where near as bad as it was a week or so ago but its starting to climb. I'm sitting around 300ms.

Cox Communications in Chandler, Arizona.
90 Human Rogue
0
02/14/2013 11:08 PMPosted by Pwnykég
i see a few posts now stating that even with cogent gone they are still having issues when hitting att, we just moved from 1 problem to the next, first took over a month to fix, wonder how long this one will take.


Yea, all I have to say is, I noticed around 4-6 am when I run a trace route, my ping/etc. for my battlegroup (shadowburn) is just fine. It's durning maybe later morning to late night that it screws up to such a degree, I'm not sure why.

I'm sure people have already explained it before, but it's still weird. I can go on the PTR and have a steady 50-70 ping at most times, Diablo 3 about the same, but live realm of WoW everything just goes to crap. I had to stop doing arena with pretty much everyone I helped it was really frustrating. It felt like I paid for a game I couldn't play, so I havn't been on since and just waiting for something to get fixed.
90 Human Death Knight
16590
Transact - Canberra Australia - Cable conection
Netspeed.com.au is my ISP, Transact the network provider

Bad latency past 2 nights - of note is result for 192.205.33.45

Result of command > pathping 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Neptune [192.168.0.199]
1 10.100.101.5
2 10.100.101.9
3 10.10.118.1
4 ge-0-0-1-942.bdr01.syd01.nsw.VOCUS.net.au [114.31.205.10]
5 ge-0-1-0-0.cor01.cbr01.act.vocus.net.au [114.31.204.102]
6 ten-0-2-0-1.cor01.syd04.nsw.vocus.net.au [114.31.204.105]
7 ten-0-0-0-2.cor01.sjc01.ca.VOCUS.net [114.31.199.36]
8 ten-0-3-0.bdr02.sjc01.ca.VOCUS.net [114.31.199.189]
9 * 10gigabitethernet3-2.core1.sjc1.he.net [64.71.184.45]
10 10gigabitethernet2-1.core1.sjc2.he.net [72.52.92.118]
11 sjo-bb1-link.telia.net [213.248.67.105]
12 * 192.205.33.45
13 cr1.sffca.ip.att.net [12.122.200.10]
14 cr1.la2ca.ip.att.net [12.122.3.122]
15 gar20.la2ca.ip.att.net [12.122.128.181]
16 12-122-254-238.attens.net [12.122.254.238]
17 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
18 * * *
Computing statistics for 425 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Neptune [192.168.0.199]
0/ 100 = 0% |
1 3ms 0/ 100 = 0% 0/ 100 = 0% 10.100.101.5
0/ 100 = 0% |
2 6ms 0/ 100 = 0% 0/ 100 = 0% 10.100.101.9
17/ 100 = 17% |
3 10ms 18/ 100 = 18% 1/ 100 = 1% 10.10.118.1
0/ 100 = 0% |
4 8ms 18/ 100 = 18% 1/ 100 = 1% ge-0-0-1-942.bdr01.syd01.nsw.VOCUS.net.au [114.31.205.10]
0/ 100 = 0% |
5 9ms 24/ 100 = 24% 7/ 100 = 7% ge-0-1-0-0.cor01.cbr01.act.vocus.net.au [114.31.204.102]
0/ 100 = 0% |
6 13ms 23/ 100 = 23% 6/ 100 = 6% ten-0-2-0-1.cor01.syd04.nsw.vocus.net.au [114.31.204.105]
0/ 100 = 0% |
7 171ms 17/ 100 = 17% 0/ 100 = 0% ten-0-0-0-2.cor01.sjc01.ca.VOCUS.net [114.31.199.36]
1/ 100 = 1% |
8 171ms 25/ 100 = 25% 7/ 100 = 7% ten-0-3-0.bdr02.sjc01.ca.VOCUS.net [114.31.199.189]
0/ 100 = 0% |
9 174ms 18/ 100 = 18% 0/ 100 = 0% 10gigabitethernet3-2.core1.sjc1.he.net [64.71.184.45]
1/ 100 = 1% |
10 179ms 20/ 100 = 20% 1/ 100 = 1% 10gigabitethernet2-1.core1.sjc2.he.net [72.52.92.118]
0/ 100 = 0% |
11 175ms 19/ 100 = 19% 0/ 100 = 0% sjo-bb1-link.telia.net [213.248.67.105]
8/ 100 = 8% |
12 177ms 27/ 100 = 27% 0/ 100 = 0% 192.205.33.45
73/ 100 = 73% |
13 --- 100/ 100 =100% 0/ 100 = 0% cr1.sffca.ip.att.net [12.122.200.10]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.122.3.122]
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-238.attens.net [12.122.254.238]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0002.lax1.attens.net [206.16.68.54]

Trace complete.
Edited by Tarasind on 2/15/2013 3:00 AM PST
90 Blood Elf Priest
13575
yup.. been having the problem for a good 3 weeks + now, got replaced from my raid group the first week, logged in occasionally to check to see if its fixed.. just got fed up with it and unsubbed :\ sad it had to come to that
90 Human Rogue
0
Tbh I believe blizzard lost majority of their subscribers not because of the game content, but more so now because of connection issues to servers.

It sucks pretty bad for the people that already paid for transfers to different battlegroups as well just to encounter the same problem.
Edited by Arrepentido on 2/15/2013 10:18 AM PST
90 Blood Elf Mage
9530
They better get to fixing these problems or everyone will unsub and then the game will go to the trash
90 Tauren Druid
0
I agree i transfered my guild an my wife over to a new battlegroup with no lag hen bam it got us in the butt again but i do have to say it isnt going over 7k now but still unplayable and im losing great raiders and members from my once prosperus guild. It seems like it isnt worth playing any more. We may leave to find another game soon if this isnt fixed immediately its be 3 -4 months now
90 Human Warrior
4915
This problem is not solved!

Is this going to receive anymore attention or what...?
This problem is not solved!

Is this going to receive anymore attention or what...?


These kinds of things take a good amount of time or a work around to fix. The AT&T server I was having issues with seems to have been taken offline or routed around.

The issue is allot like your neighbors tree blocking your sun. Sure you can ask them to cut it down, but do they have the money for it at the house? Do they have to get a permit from the city to do it? etc etc

Everyone is super adverse to quick changes on high end infrastructure.

Cudos to the guys for working with us through this issue, Above and beyond service!
90 Human Paladin
14710
US-Sargeras
Baltimore, MD
Verizon FIOS
Latency up/down and getting 0.5-1sec lag spikes fairly frequently.


Tracing route to 63.240.161.189 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 6 ms 6 ms L100.BLTMMD-VFTTP-32.verizon-gni.net [96.234.147.1]
3 6 ms * 8 ms G0-10-0-6.BLTMMD-LCR-22.verizon-gni.net [130.81.217.22]
4 13 ms 13 ms 12 ms so-6-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.199.4]
5 14 ms 16 ms 13 ms 0.xe-7-3-0.BR1.IAD8.ALTER.NET [152.63.3.125]
6 16 ms 16 ms 17 ms 192.205.36.141
7 65 ms 63 ms 62 ms cr2.wswdc.ip.att.net [12.122.81.250]
8 38 ms 39 ms 38 ms cr1.cgcil.ip.att.net [12.122.18.21]
9 42 ms 40 ms 43 ms gar2.clboh.ip.att.net [12.122.133.197]
10 60 ms 64 ms 43 ms 12.122.251.50
11 39 ms 38 ms 38 ms 63.240.130.210
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.



Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Craig-PC.home [192.168.1.8]
1 Wireless_Broadband_Router.home [192.168.1.1]
2 L100.BLTMMD-VFTTP-32.verizon-gni.net [96.234.147.1]
3 * G0-10-0-6.BLTMMD-LCR-22.verizon-gni.net [130.81.217.22]
4 so-6-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.199.4]
5 0.xe-7-3-0.BR1.IAD8.ALTER.NET [152.63.3.125]
6 192.205.36.141
7 cr2.wswdc.ip.att.net [12.122.81.250]
8 cr1.cgcil.ip.att.net [12.122.18.21]
9 gar2.clboh.ip.att.net [12.122.133.197]
10 12.122.251.22
11 63.240.130.210
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Craig-PC.home [192.168.1.8]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% Wireless_Broadband_Router.home [192.168.1.1]
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% L100.BLTMMD-VFTTP-32.verizon-gni.net [96.234.147.1]
0/ 100 = 0% |
3 8ms 6/ 100 = 6% 6/ 100 = 6% G0-10-0-6.BLTMMD-LCR-22.verizon-gni.net [130.81.217.22]
0/ 100 = 0% |
4 43ms 9/ 100 = 9% 9/ 100 = 9% so-6-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.199.4]
0/ 100 = 0% |
5 17ms 0/ 100 = 0% 0/ 100 = 0% 0.xe-7-3-0.BR1.IAD8.ALTER.NET [152.63.3.125]
0/ 100 = 0% |
6 17ms 0/ 100 = 0% 0/ 100 = 0% 192.205.36.141
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.81.250]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% gar2.clboh.ip.att.net [12.122.133.197]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.22
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.210

Trace complete.
90 Orc Hunter
11410
you have a dropped packet on hop 3, which is still in your ISP network, i would call them
90 Human Warrior
4915
just did a trace route...

still having a problem with cogentco, blizzard......

coltontel is my isp

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 1 ms <1 ms 1 ms mygateway1.ar7 [192.168.3.1]
2 28 ms 28 ms 28 ms ftth-38-126-76-65.colton.com [38.126.76.65]
3 32 ms 29 ms 28 ms c7200-gi02-rtr.colton.com [38.103.162.1]
4 29 ms 29 ms 30 ms gi1-32.ccr01.pdx01.atlas.cogentco.com [38.104.105.53]
5 121 ms 202 ms 204 ms te3-4.ccr01.pdx02.atlas.cogentco.com [154.54.0.90]
6 41 ms 48 ms 41 ms te7-3.ccr01.boi01.atlas.cogentco.com [154.54.40.102]
7 48 ms 48 ms 48 ms te0-7-0-8.ccr21.slc01.atlas.cogentco.com [154.54.40.93]
8 141 ms 207 ms 243 ms te2-1.ccr02.den01.atlas.cogentco.com [154.54.87.21]
9 70 ms 71 ms 72 ms te0-3-0-7.ccr22.mci01.atlas.cogentco.com [154.54.87.94]
10 132 ms 89 ms 95 ms te0-2-0-5.ccr21.ord01.atlas.cogentco.com [154.54.82.142]
11 83 ms 111 ms 114 ms te0-1-0-3.ccr22.ord03.atlas.cogentco.com [154.54.1.2]
12 115 ms 98 ms 97 ms 192.205.37.173
13 100 ms 98 ms 99 ms cr2.cgcil.ip.att.net [12.122.84.94]
14 121 ms 96 ms 107 ms gar3.cgcil.ip.att.net [12.122.132.213]
15 97 ms 98 ms 99 ms 12.122.251.22
16 97 ms 96 ms 97 ms 63.240.130.214
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.
This topic is locked.

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]