High Latency related to Battlegroup?

Technical Support
Prev 1 95 96 97 101 Next
Getting highly unusual latency (started a few weeks ago). I live on the east coast and play on Kilrogg.

Tracing route to 12.129.254.164 over a maximum of 30 hops

1 <1 ms <1 ms 1 ms vl304.fq-core-2.gw.pitt.edu [130.49.44.1]
2 24 ms 52 ms 25 ms vl371.fq-core-2.gw.pitt.edu [136.142.172.209]
3 47 ms 45 ms 51 ms xe-1-0-0-713.externals-cl.gw.pitt.edu [136.142.2.169]
4 27 ms 28 ms 33 ms xe-1-0-0-716.externals-fq.gw.pitt.edu [136.142.2 53.174]
5 47 ms 56 ms 48 ms 173.225.48.73
6 23 ms 25 ms 22 ms te-3-1.car2.Pittsburgh3.Level3.net [4.49.110.85]
7 58 ms 54 ms 57 ms ae-3-3.ebr1.Chicago1.Level3.net [4.69.135.250]
8 59 ms 56 ms 51 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
9 34 ms 37 ms 35 ms 4.69.158.137
10 50 ms 55 ms 52 ms 192.205.37.149
11 157 ms 139 ms 270 ms cr1.cgcil.ip.att.net [12.122.133.162]
12 101 ms 99 ms 104 ms cr2.dvmco.ip.att.net [12.122.31.85]
13 103 ms 111 ms 108 ms cr1.slkut.ip.att.net [12.122.30.25]
14 142 ms 152 ms 151 ms cr2.la2ca.ip.att.net [12.122.30.30]
15 140 ms 135 ms 225 ms gar29.la2ca.ip.att.net [12.122.129.241]
16 146 ms 119 ms 147 ms 12-122-254-234.attens.net [12.122.254.234]
17 144 ms 150 ms 146 ms 206.16.68.46
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.
Raiding is completely unplayable from 6pm-11pm EST for the past 3 weeks. Latency spikes with dropped packets during those times, it's like someone flips a switch and says NO WOW FOR YOU!

traceroute to 206.18.98.208 (206.18.98.208), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 0.804 ms 1.588 ms 0.607 ms
2 24.98.200.1 (24.98.200.1) 100.974 ms 21.213 ms 39.260 ms
3 xe-10-0-0-32767-sur01.g1norcross.ga.atlanta.comcast.net (68.85.173.61) 10.556 ms 10.301 ms 9.403 ms
4 xe-13-0-1-0-ar01.b0atlanta.ga.atlanta.comcast.net (68.86.106.1) 10.702 ms 11.176 ms 13.239 ms
5 pos-5-12-0-0-cr01.56marietta.ga.ibone.comcast.net (68.86.93.125) 15.736 ms
pos-5-13-0-0-cr01.56marietta.ga.ibone.comcast.net (68.86.95.197) 15.567 ms
pos-5-11-0-0-cr01.56marietta.ga.ibone.comcast.net (68.86.93.205) 30.485 ms
6 pos-0-2-0-0-pe01.56marietta.ga.ibone.comcast.net (68.86.86.166) 15.838 ms 32.504 ms 22.491 ms
7 as7018-pe01.56marietta.ga.ibone.comcast.net (75.149.228.86) 119.264 ms 187.907 ms 119.267 ms
8 cr2.attga.ip.att.net (12.122.117.98) 141.191 ms 147.212 ms 145.231 ms
9 cr1.nsvtn.ip.att.net (12.122.28.106) 142.293 ms 144.930 ms 196.839 ms
10 cr2.nsvtn.ip.att.net (12.122.28.70) 146.452 ms 168.324 ms *
11 cr1.cl2oh.ip.att.net (12.122.28.74) 169.010 ms 142.130 ms 140.446 ms
12 cr1.cgcil.ip.att.net (12.122.2.205) 139.125 ms 142.471 ms 148.875 ms
13 gar2.clboh.ip.att.net (12.122.133.197) 139.314 ms 136.742 ms 143.568 ms
14 12.122.251.50 (12.122.251.50) 146.994 ms
12.122.251.22 (12.122.251.22) 164.920 ms 139.705 ms
15 63.240.130.210 (63.240.130.210) 139.765 ms
63.240.130.214 (63.240.130.214) 138.925 ms
63.240.130.210 (63.240.130.210) 143.038 ms
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
39 * * *
40 * * *
41 * * *
42 * * *
43 * * *
44 * * *
45 * * *
46 * * *
47 * * *
48 * * *
49 * * *
50 * * *
51 * * *
52 * * *
53 * * *
54 * * *
55 * * *
56 * * *
57 * * *
58 * * *
59 * * *
60 * * *
61 * * *
62 * * *
63 * * *
64 * * *
Yep, trying to level now. This game is completely unplayable. FIX THIS NOW. I'm talking 24/7 round the clock people on site to fix these busted servers and packet losses on the backbone. kkthx.
Incorrect, unless we manage to luck out and contact a gaming fan with pull at an ISP, we have no voice at all. Remember, assuming they'd pay for Internet anyway, ISPs make no money from having their customers play our games (or anyone elses). Quite the opposite actually, as most ISPs hate having their customers play intensive online games. Intensive online games have high packet integrity requirements that normal Internet usage does not.


I'm not from Az so I made my own thread, but i read this and I felt I should add that I have some pull with my ISP as I allow them to have a tower set on my property. I've worked with them before for free, using my spare time helping them fix connection problems when they are understaffed or can't get out to this location in time, I'd change wires,do power cycles and what not. My ISP may not be the one you want to talk to (Surewest communications) but if there is anything I can do let me know, I will have them do it.
bump bump.. .anyone seen an improvement?
i have seen a little bit of an improvment on thrall during peak hours but still have the moderately high latency but at least i can move around now lol. But the down part is im still having to use the proxifier to raid :(
02/28/2013 05:23 AMPosted by Murred
bump bump.. .anyone seen an improvement?


Too early to say for certain yet, but I've had low latency for about 30 minutes now. It's been about a week since the blue's post, and he said the ETA was about a week.
Too early to say for certain yet, but I've had low latency for about 30 minutes now. It's been about a week since the blue's post, and he said the ETA was about a week.


Yeppers! I just received confirmation that the first wave of upgrades has went live in Chicago! I don't have an ETA yet on wave two, but this first one will hopefully help out a fair bit. In the meanwhile, we're still recommending that other ISPs reroute when possible. The lighter we can make the load on the affected nodes, the more effective the upgrades will be.

We're also taking advantage of the attention focused on this backbone problem to try to make more contacts at ISPs that we can poke when we spot issues. As I mentioned earlier in the thread, many ISPs aren't very receptive to our requests, but we try to build relationships where we can. Nothing like a national issue to help ISPs pay more attention, eh? :)
My usual low latency is 40-50ms, I will say it's hitting 70-90 now but it hasn't gone above 100 at least, so it is helping. Didn't start going up until around 7 whereas without the fix it was spiking up as early as 3pm.

PS: Good to know it's live, thanks.
I've been experiencing periodic bouts of lag spikes since transferring to Bleeding Hollow in January. The lag flares up worst during evenings, but is recurrent during daytime. Raiding is becoming impossible in the current state.

1 1 ms <1 ms <1 ms Home
2 28 ms 16 ms 14 ms c-98-224-48-1.hsd1.fl.comcast.net [98.224.48.1]
3 10 ms 37 ms 38 ms te-1-2-ur01.arlington.fl.jacksvil.comcast.net [68.85.94.33]
4 11 ms 10 ms 11 ms te-9-1-ur01.ftcaroline.fl.jacksvil.comcast.net [68.86.168.6]
5 15 ms 14 ms 11 ms te-0-4-0-10-ar02.westside.fl.jacksvil.comcast.net [68.85.225.69]
6 23 ms 23 ms 22 ms pos-1-2-0-0-cr01.charlotte.nc.ibone.comcast.net [68.86.95.61]
7 29 ms 27 ms 122 ms pos-3-10-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.86.221]
8 30 ms 27 ms 26 ms pos-0-10-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.88.182]
9 44 ms 43 ms 46 ms as7018-pe01.56marietta.ga.ibone.comcast.net [75.149.228.86]
10 66 ms 67 ms 67 ms cr2.attga.ip.att.net [12.122.117.98]
11 72 ms 73 ms 68 ms cr1.nsvtn.ip.att.net [12.122.28.106]
12 68 ms 71 ms 71 ms cr2.nsvtn.ip.att.net [12.122.28.70]
13 74 ms 77 ms 74 ms cr1.cl2oh.ip.att.net [12.122.28.74]
14 80 ms 76 ms 75 ms cr1.cgcil.ip.att.net [12.122.2.205]
15 73 ms 73 ms 72 ms gar2.clboh.ip.att.net [12.122.133.197]
16 76 ms 73 ms 74 ms 12.122.251.22
17 76 ms 75 ms 105 ms 63.240.130.210
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.
i can confirm it is AT&T's routers, using smoothping to bypass them completely during 8-11pm EST completely resolves any lagging. when u tracert during these times u can see at&t's routers get bogged down. they have been pretty good for the past week but the issue still crops up on random days. still only between 8-11pm EST.

i believe i said earlier in the thread that at&t doesnt do anything about their routing and the only thing u can do is wait till it clears up on its own. problems like this take months to clear up. 3 months so far, dang im good.
Heyo,

Guildmates of mine have been having MS/Lag issues since the beginning of this problem(2months ago?) so myself and other officers have been keeping track of it, but I myself have had no aberrant behavior.
Tonight however, myself and several other previously unaffected people I know have been having a large amount of lag. Personally I am hitting MS rates over 800(both home and world).

I am assuming this is an issue because of the new "upgrades" in Chicago(I am on Ruin residing in NH). Either rerouting people to the path I have been using or moving me onto a different path is my lame guess.

Is 206.18.98.208 still the IP for Bleeding Hollow? And if so is Blizzard masking on there end because I can't get a TraceRT all the way there anymore :[
I am happy to say that on Arthas for me this problem seems to be resolved. I dont know what happened but I went from getting 400 ms down to 59 ms. This is quite an improvement obviously. Whatever is taking place I hope it is permanent and everyone will see its effects soon.
Hello I might be the only cableone isp here but from Arizona. Since last week I've noticed huge lag spikes at random and need a fix it appears to happen more during evening but can't confirm this.

1. Doomhammer US
2. Snowflake, Arizona
3. Cableone
4. Trace Route

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 1 ms <1 ms <1 ms 192.168.1.1

2 7 ms 8 ms 7 ms 10.104.176.1

3 10 ms 9 ms 10 ms 192.168.3.77

4 13 ms 15 ms 16 ms 192.168.103.37

5 15 ms 15 ms 15 ms xe-11-3-0.bar1.Phoenix1.Level3.net [4.28.80.133]

6 17 ms 16 ms 18 ms ae-0-11.bar2.Phoenix1.Level3.net [4.69.148.114]

7 28 ms 26 ms 26 ms ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]

8 31 ms 29 ms 27 ms ae-92-92.csw4.LosAngeles1.Level3.net [4.69.137.30]

9 * * * Request timed out.

10 119 ms 81 ms 78 ms ae-6-6.ebr1.Tustin1.Level3.net [4.69.153.222]

11 132 ms 128 ms 110 ms ae-108-3508.bar2.Tustin1.Level3.net [4.69.158.110]

12 31 ms 30 ms 94 ms 192.205.37.145

13 134 ms 88 ms 85 ms cr2.la2ca.ip.att.net [12.122.129.106]

14 84 ms 87 ms 91 ms cr1.slkut.ip.att.net [12.122.30.29]

15 86 ms 132 ms 86 ms cr2.dvmco.ip.att.net [12.122.30.26]

16 85 ms 87 ms 97 ms cr1.cgcil.ip.att.net [12.122.31.86]

17 85 ms 137 ms 92 ms cr1.cl2oh.ip.att.net [12.122.2.206]

18 86 ms 87 ms 93 ms cr2.cl2oh.ip.att.net [12.122.2.126]

19 86 ms 132 ms 94 ms cr2.phlpa.ip.att.net [12.122.2.210]

20 87 ms 83 ms 82 ms gar1.pitpa.ip.att.net [12.122.107.85]

21 90 ms 92 ms 128 ms 12.122.251.2

22 150 ms 108 ms 90 ms mdf001c7613r0003-gig-10-1.nyc3.attens.net [63.240.65.10]

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.

Pathping.


No resources
Same as it was a few days ago, from ~8PMEST - ~1AMEST lags annoyingly:

Tracing route to 12.129.254.164 over a maximum of 30 hops

1 1 ms <1 ms <1 ms vl304.fq-core-2.gw.pitt.edu [130.49.44.1]
2 21 ms 26 ms 24 ms vl371.fq-core-2.gw.pitt.edu [136.142.172.209]
3 51 ms 53 ms 59 ms xe-1-0-0-713.externals-cl.gw.pitt.edu [136.142.2.169]
4 30 ms 30 ms 31 ms xe-1-0-0-716.externals-fq.gw.pitt.edu [136.142.253.174]
5 47 ms 49 ms 46 ms 173.225.48.73
6 30 ms * 25 ms te-3-1.car2.Pittsburgh3.Level3.net [4.49.110.85]
7 54 ms 61 ms 47 ms ae-3-3.ebr1.Chicago1.Level3.net [4.69.135.250]
8 51 ms 52 ms 49 ms ae-6-6.ebr1.Chicago2.Level3.net [4.69.140.190]
9 77 ms 71 ms 92 ms 4.69.158.137
10 50 ms 52 ms 56 ms 192.205.37.149
11 144 ms 150 ms 150 ms cr1.cgcil.ip.att.net [12.122.133.162]
12 100 ms 111 ms 100 ms cr2.dvmco.ip.att.net [12.122.31.85]
13 103 ms 107 ms 107 ms cr1.slkut.ip.att.net [12.122.30.25]
14 133 ms 142 ms 129 ms cr2.la2ca.ip.att.net [12.122.30.30]
15 123 ms 126 ms 124 ms gar29.la2ca.ip.att.net [12.122.129.241]
16 135 ms 135 ms 135 ms 12-122-254-238.attens.net [12.122.254.238]
17 127 ms 138 ms 133 ms 206.16.68.46
18 * * * Request timed out.
19 * * * Request timed out.
20 ETC
Since I'm not getting any help on my other thread, maybe someone here can.
I use Comcast, in VA
Azgalor server

Get lag spikes during the nighttime

racing route to 63.240.161.189 over a maximum of 30 hops

1 1 ms 1 ms 1 ms 63.240.161.189
2 41 ms 30 ms 29 ms 71.57.199.1
3 12 ms 178 ms 12 ms te-1-2-ur01.culpeper.va.richmond.comcast.net [68.86.200.9]
4 44 ms 36 ms 17 ms xe-5-1-3-0-ar02.staplesmllrd.va.richmond.comcast.net [68.86.173.109]
5 28 ms 55 ms 23 ms pos-0-6-0-0-cr01.charlotte.nc.ibone.comcast.net [68.86.91.149]
6 30 ms 32 ms 32 ms pos-3-13-0-0-cr01.56marietta.ga.ibone.comcast.net [68.86.86.225]
7 30 ms 60 ms 49 ms pos-0-11-0-0-pe01.56marietta.ga.ibone.comcast.net [68.86.88.186]
8 101 ms 103 ms 131 ms as7018-pe01.56marietta.ga.ibone.comcast.net [75.149.228.86]
9 145 ms 128 ms 127 ms cr2.attga.ip.att.net [12.122.117.98]
10 130 ms 131 ms 133 ms cr1.nsvtn.ip.att.net [12.122.28.106]
11 127 ms 151 ms 128 ms cr2.nsvtn.ip.att.net [12.122.28.70]
12 151 ms 127 ms 127 ms cr1.cl2oh.ip.att.net [12.122.28.74]
13 126 ms 152 ms 122 ms cr1.cgcil.ip.att.net [12.122.2.205]
14 158 ms 124 ms 134 ms gar2.clboh.ip.att.net [12.122.133.197]
15 116 ms 117 ms 118 ms 12.122.251.22
16 134 ms 132 ms 268 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.
1) Realm: Illidan
2) City and State: Maricopa, Arizona
3) ISP (Internet Service Provider): Orbitel
4) A trace route and pathping:

Tracing route to 63.240.161.189 over a maximum of 30 hops

1 1 ms 1 ms 1 ms www.asusnetwork.net [192.168.1.1]
2 11 ms 13 ms 9 ms 10.8.52.1
3 14 ms 12 ms 10 ms 10.200.1.1
4 12 ms 13 ms 11 ms 208-95-94-249.gilanet.net [208.95.94.249]
5 11 ms 15 ms 14 ms xe-10-0-3.bar2.Phoenix1.Level3.net [4.28.82.25]
6 28 ms 26 ms 23 ms ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
7 27 ms 22 ms 26 ms ae-82-82.csw3.LosAngeles1.Level3.net [4.69.137.26]
8 23 ms 22 ms 25 ms ae-83-83.ebr3.LosAngeles1.Level3.net [4.69.137.41]
9 24 ms 27 ms 25 ms ae-7-7.ebr2.Tustin1.Level3.net [4.69.153.226]
10 24 ms 23 ms 27 ms ae-206-3606.bar2.Tustin1.Level3.net [4.69.158.118]
11 27 ms 29 ms 25 ms 192.205.37.145
12 261 ms 248 ms 246 ms cr2.la2ca.ip.att.net [12.122.129.106]
13 239 ms 228 ms 225 ms cr1.slkut.ip.att.net [12.122.30.29]
14 237 ms 235 ms 224 ms cr2.dvmco.ip.att.net [12.122.30.26]
15 245 ms 261 ms 269 ms cr1.cgcil.ip.att.net [12.122.31.86]
16 247 ms 239 ms 301 ms gar2.clboh.ip.att.net [12.122.133.197]
17 249 ms 253 ms 247 ms 12.122.251.22
18 251 ms 239 ms 248 ms 63.240.130.214
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.
I'm in Tucson, Az with Cox Cable
about this time last week my connection of Kilrogg was shot to hell! i struggled to do even the simplest of dailies. i figured i would try the usual suggested fix of deleting the files in the WoW folder. that seemed to work, around monday and tuesday my connection was doing fine, until wednesday night came around, and it was down the crapper again!
i would post the tracer routes like everyone else, but im not the most technically inclined and dont know how. but trust when i tell you that my MS is bad! from the moment i log on its 3000+, yes! 3000+, i do not exaggerate! i can barely check my mail, if anything at all!
Jacksonville Florida getting any upgrades? It is really bad here.

Join the Conversation

Return to Forum