High Latency related to Battlegroup?

Technical Support
Prev 1 87 88 89 101 Next
TO ALL CANADIANS, NAMELY WEST COAST ONES BUT LET'S HOPE ALL:

I raided Tuesday and Wednesday evening from a town about 40 minutes outside of Vancouver. The highest spike I got was 800 world, 80 home. It caused slight ability lag on both nights.

Tuesday night I got crushed by Garalon standing about 10 yds from his inner ring. What makes this weird is I never moved from my spot when he crushed as I thought I was out.. low and behold I didn't get one shot.

Ability lag was again, slight. I had one time where I lost probably 2 full rotations in a spike and that was it.

I'd like to say that more ports have been opened by Cogentco resulting in less lag, but at the same time, the lag is still present. I'm used to 30/30-60/60.. not 82/82 at all times with spikes as high as 18000 at peak times.

To conclude, and leave a hopefully positive vibe, I can raid. I can lead my team, I can play my main and do my dailies and LFR's etc etc with little to no lag shown. Hopefully this is spilling over to other Telus users around my area or in Canada for that matter.. and other ISP's having this issue. Unfortunately we can't yell at anyone about it as nothing can be done any quicker than they're already trying it seems.. (doesn't feel like they're trying hard but meh, what can ya do as the consumer right.. un-sub.. no thanks). Good luck fellow Canadians, I hope you're having the same break-throughs I am.
02/10/2013 04:07 PMPosted by Skhy
The problem does not clear up till 11pm my time which is time for bed .


Clears up for me around then too, which reinforces the aforementioned Concengo node congestion problem.
I am still experiencing lag. Very bad lag. Disconnecting multiple times a day.

Also, I am on the west coast.
just using smoothping here till whatever issue there is with congestion eventually resolves itself..these issues with connecting to wow usually last months. over the course of playing wow for over 8 years u learn u have to either use smoothping during the times where its lagging or ull miss out on ALOT of playtime over many months.

no amount of reporting the issue to any company ever does anything. give a tunneling service your money or be prepared to not play wow during the laggy time for many months.

coming here to complain to blizz just ends up in them pointing the finger at an ISP. complaining to ANY isp ends up in pointing the finger at blizzard (or they just say anything to get you to go away).

edit: its funny tho, the last time i had to use smoothping was Feb 2010 (i skipped most of cata) and now its Feb 2013 and i gotta use it again. wierd. i guess we were due for some more latency issues!
Ugh, I thought I solved this issue when I switched providers. LIterally my ping was down to 89ms almost always.

couple of days ago, it's back upt o 150 to 300.... sigh....
Blizzard does not care they keep getting their money from us ...all we can do is complain
I finally canceled my sub because of this issue.
It's not Blizzard's fault. It's some dumb!@#$ company Cognet who is literally "breaking the internet"
Alright, another update for West Coast Canadians:

I raided for 3 hours tonight. Had around 5 lag spikes leading to ability lag and slight chat lag. Never bad, losing around 1/4 to 1/2 of a priority rotation each time. Never happened more than once per fight. I showed a constant 180/120.. sometimes getting as high as 300/200. Other than that, I was once again able to lead my raid and play the game effectively. Still not perfectly, but effectively.
Alright, another update for West Coast Canadians:

I raided for 3 hours tonight. Had around 5 lag spikes leading to ability lag and slight chat lag. Never bad, losing around 1/4 to 1/2 of a priority rotation each time. Never happened more than once per fight. I showed a constant 180/120.. sometimes getting as high as 300/200. Other than that, I was once again able to lead my raid and play the game effectively. Still not perfectly, but effectively.


Mine was as bad, or worse, than ever tonight. Now in addition to the massive lag and packet loss, I'm getting disconnected. Traces at peak hours still have Cogentco and AT&T squarely in the middle of the trainwreck.

It's pretty bad when I start considering 'playable' to be anything with less that 4+ digits of latency.
High Latency for 5 days now canceled sub peace
Not sure where else to put my pathping. But the results have been the same for last week or so. I lose 100% of data between hop 6 and 7. Can't isolate the ip address, so hopefully blizz can contact these folks and get it fixed.

Anyway, here's my pathping, tracert follows pathping:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\cmb2dogs>pathping 63.240.104.93

Tracing route to 63.240.104.93 over a maximum of 30 hops

0 cmb2dogs-PC.Belkin [192.168.2.2]
1 router.Belkin [192.168.2.1]
2 10.230.192.1
3 173-219-253-126-link.sta.suddenlink.net [173.219.253.126]
4 173-219-253-234-link.sta.suddenlink.net [173.219.253.234]
5 ae0-203.was14.ip4.tinet.net [216.221.157.173]
6 192.205.37.193
7 cr1.wswdc.ip.att.net [12.122.88.174]
8 cr2.phlpa.ip.att.net [12.122.4.53]
9 gar1.pitpa.ip.att.net [12.122.107.85]
10 12.122.251.2
11 mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
12 * * *
Computing statistics for 275 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 cmb2dogs-PC.Belkin [192.168.2.2]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% router.Belkin [192.168.2.1]
0/ 100 = 0% |
2 7ms 0/ 100 = 0% 0/ 100 = 0% 10.230.192.1
0/ 100 = 0% |
3 8ms 0/ 100 = 0% 0/ 100 = 0% 173-219-253-126-link.sta.suddenlin
k.net [173.219.253.126]
0/ 100 = 0% |
4 15ms 0/ 100 = 0% 0/ 100 = 0% 173-219-253-234-link.sta.suddenlin
k.net [173.219.253.234]
0/ 100 = 0% |
5 16ms 0/ 100 = 0% 0/ 100 = 0% ae0-203.was14.ip4.tinet.net [216.2
21.157.173]
0/ 100 = 0% |
6 20ms 0/ 100 = 0% 0/ 100 = 0% 192.205.37.193
100/ 100 =100% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.wswdc.ip.att.net [12.122.88.17
4]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr2.phlpa.ip.att.net [12.122.4.53]

0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% gar1.pitpa.ip.att.net [12.122.107.
85]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.2
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-12-1.nyc3.att
ens.net [63.240.65.14]

Trace complete.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\cmb2dogs>tracert 63.240.65.14

Tracing route to mdf001c7613r0004-gig-12-1.nyc3.attens.net [63.240.65.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms router.Belkin [192.168.2.1]
2 6 ms 5 ms 5 ms 10.230.192.1
3 6 ms 5 ms 5 ms 173-219-253-126-link.sta.suddenlink.net [173.219
.253.126]
4 14 ms 13 ms 15 ms 173-219-253-234-link.sta.suddenlink.net [173.219
.253.234]
5 12 ms 13 ms 13 ms ae0-203.was14.ip4.tinet.net [216.221.157.173]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
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 *

Just stopped at hop 26 because there was no need to continue with the Timed Out items.
Apparently a Blizzard customer service rep said that this issue "should" be fixed and to call our ISPs and have them reroute around the cogentco issue if we're still having issues... gonna try that today and see if it works.
02/11/2013 10:55 AMPosted by Athenä
Apparently a Blizzard customer service rep said that this issue "should" be fixed and to call our ISPs and have them reroute around the cogentco issue if we're still having issues... gonna try that today and see if it works.


If you do, let me know how it went. I talked to my ISP about it for 20 minutes last night and they had no idea what Blizzard was talking about. They can't re-route traffic like that. It goes through Cogent and that's that is what they told me. It's not my ISP's equipment or connection, they just show it as an outage for World of Warcraft and continue about their day. They have NO plans to make any fixes they told me.
Cancelled my account that has been in place consistently since the release of this game due to this.
yeah, this problem is far from being fixed, still getting high ms at peak hours and unable to heal properly as im still getting random spikes of 1500+ and giving me delays
02/11/2013 11:23 AMPosted by Shiiana
Apparently a Blizzard customer service rep said that this issue "should" be fixed and to call our ISPs and have them reroute around the cogentco issue if we're still having issues... gonna try that today and see if it works.


If you do, let me know how it went. I talked to my ISP about it for 20 minutes last night and they had no idea what Blizzard was talking about. They can't re-route traffic like that. It goes through Cogent and that's that is what they told me. It's not my ISP's equipment or connection, they just show it as an outage for World of Warcraft and continue about their day. They have NO plans to make any fixes they told me.


I called my ISP about this. However the person seemed to ignore what I said and just had me do multiple power cycles with my units. Really irritated me. I told them that I spoke to Blizzard about it and offered a solution but I didn't get any acknowledgement with it. Hopefully it isn't this way with everyone.
Jonathan in India is going to run through the script of credential confirmations, power cycles, and modem factory resets until your ears bleed and you're gonna like it.
02/11/2013 04:34 PMPosted by Haiwon


If you do, let me know how it went. I talked to my ISP about it for 20 minutes last night and they had no idea what Blizzard was talking about. They can't re-route traffic like that. It goes through Cogent and that's that is what they told me. It's not my ISP's equipment or connection, they just show it as an outage for World of Warcraft and continue about their day. They have NO plans to make any fixes they told me.


I called my ISP about this. However the person seemed to ignore what I said and just had me do multiple power cycles with my units. Really irritated me. I told them that I spoke to Blizzard about it and offered a solution but I didn't get any acknowledgement with it. Hopefully it isn't this way with everyone.


"your friend in the digital age" my !@#. customer service from blizz and cox are so garbage I just call them and now and say hi. Game is unplayable, FML
As of late I haven't been playing much since this has been an issue for me since last year but ultimately exploded into what I call "Cogento-AT&T-Blizz Gate" around January 6th 2013.

Anywhos, when I do play, anywhere from 8pm EST till whenever, latency seems to have gone down but ability delays are had all through the night. I may hit the yellow around this time, but its certainly tolerable (but barely).
It is not till 11pm EST, when all the pacific players hit their peak hours, that I eventually get into the red latencys. And unfortunately, if I don't get teh chance to get on during just EST peak times, the game is unplayable for a good 2 hours (11pm-1am EST).

Could this be coincidence, maybe. But in all honesty, since they started to introduce CRZ and then the shift to standardized time zones with PST, the game has caused nothing but issues for me. ATM, Dalaran has no chat channels, my pet doesn't show up in the login screen if I log at the Shrine in the Vale and of course all this latency that several players across the world are experiencing.

Join the Conversation

Return to Forum