High Latency related to Battlegroup?

(Locked)

90 Blood Elf Priest
7240
here is something to think about...

I am in AZ on a gaming laptop..

when at my brothers house (Cox Cable) i hit 7 Cogent servers and have 300-3000 latency

Tracing route to 63.240.161.189 RAMPAGE battlegroup

1 10.54.160.1
2 172.21.0.160
3 chndcorc01-pos--0-3-0-0.ph.ph.cox.net [70.169.72.48]
4 70.169.75.153
5 68.1.5.139
6 te0-7-0-21.ccr22.lax05.atlas.cogentco.com [154.54.13.129]
7 te0-0-0-2.mpd22.lax01.atlas.cogentco.com [154.54.6.229]
8 te0-2-0-3.ccr22.iah01.atlas.cogentco.com [154.54.45.1]
9 te0-0-0-1.ccr22.dfw01.atlas.cogentco.com [154.54.25.221]
10 te0-3-0-6.ccr22.mci01.atlas.cogentco.com [154.54.46.209]
11 te0-7-0-33.ccr22.ord01.atlas.cogentco.com [154.54.30.102]
12 te0-6-0-0.ccr22.ord03.atlas.cogentco.com [154.54.29.22]

now that i'm over at a buddies house who uses CentryLink, same laptop, same Battlegroup I DON'T HIT ANY Cogent servers and i played with 70-80 ms all day peak hours inc.

Tracing route to 63.240.161.189 RAMPAGE battle group

1 1 ms 1 ms 1 ms 192.168.0.1
2 22 ms 20 ms 21 ms phnx-dsl-gw53-245.phnx.qwest.net [67.40.227.245]
3 21 ms 20 ms 20 ms phnx-agw1.inet.qwest.net [75.160.237.161]
4 31 ms 31 ms 32 ms lap-brdr-03.inet.qwest.net [67.14.22.78]
5 34 ms 34 ms 34 ms 63.146.27.102
6 77 ms 79 ms 77 ms cr2.la2ca.ip.att.net [12.123.30.150]
7 75 ms 76 ms 80 ms cr1.slkut.ip.att.net [12.122.30.29]
8 77 ms 75 ms 78 ms cr2.dvmco.ip.att.net [12.122.30.26]
9 77 ms 79 ms 78 ms cr1.cgcil.ip.att.net [12.122.31.86]
10 74 ms 74 ms 75 ms gar2.clboh.ip.att.net [12.122.133.197]

I did get a couple lag spikes but they went away almost instanly and seemed to be mostly Dungeon / Battleground related.

last we talked to Cox, they said they were not able to route around Cogent???

I would be curious if any other laptop users could try other ISP's like i did for comparison.
01/31/2013 09:54 PMPosted by Héélz
I would be curious if any other laptop users could try other ISP's like i did for comparison.


I have. Any connection routing through Cogentco to att12.122.*.* at two different ISPs (one of them being mine at sptc.net-Lubbock see major problems during prime to the point of being unplayable to moderate latency during off-hours. No issues otherwise, or to other datacenters.

Any connection that avoids Cogento to Rampage is great.
100 Troll Mage
SY
8670
Can we please get a blue post update with some substance on this issue? I am to the point if this isn't fixed in two weeks, I am canceling my subscription. This is going on for entirely too long.
Edited by False on 2/1/2013 12:02 AM PST
90 Night Elf Warrior
7340
The problem won't be solved in a couple days. All the latency issues are probably going to continue until Cogentco is able to reinforce their services. Which by guess is probably closer to a month. I've asked not only my ISP, but a couple of IT friends about it, and "The problem isn't fixable over night. They'd have to reinforce all their fibre lines, which usually involves hundreds of feet of trenches, laying, and then testing." It's likely that the problem will be fixed, but if I had to guess we're looking at somewhere close to a month +, It's not Blizzards fault directly, its not your ISP's. Its the company relaying it all and they have been >told< about this, and they are working on it. But unfortunately its pretty big, its not just as simple as "turning off this switch and turning on this other one." Alot of ISP's do have partner services that CAN route you around (if you're lucky, I wasn't) so it is worth mentioning to them. As for the long awaited blue post that everyone wants to hear, I'd personally guess that the reason its being delayed, or they havent -really- said anything about it is because they know roughly the time frame of how long something like this is going to take so they wouldn't risk losing more subscribers. I mean hell it is a business, why not keep us on a leash for another month hoping that "tomorrow will be better." instead of losing a large player base for that period of time, however long it actually is.

Keep in mind this is a personal opinion and just here say between a few IT friends and my ISP trying to give me a good guess on when its actually going to be solved.

P.S. Yes I have asked blizzard about it, alot of "ASAP" and "We're not too sure." nonsense going on like I'm sure most of you have gotten.
92 Night Elf Mage
8730
ISP: MI-Connection
Mooresville, NC

Quite possibly the most uncooperative ISP.

Good luck and thank you for at least trying.
90 Blood Elf Paladin
7515
I hope Cogent gets its stuff right, in the last 24h Cogent is having packetloss problems with pretty much ALL the other bandwidth providers.

http://www.internetpulse.net/Main.aspx?Period=RH24
Edited by Necroholic on 2/1/2013 9:37 AM PST
So four weeks and counting.
85 Human Mage
3325
I was just about to spend several frustrating hours trying to figure out what was wrong with my connection. Thankfully my friend here in Az told me about this thread.

Add me to the list of frustrated Cox Communications clients!

Chandler, Az
Edited by Serranus on 2/1/2013 9:23 PM PST
90 Blood Elf Paladin
9365
Just got back into wow this past month after a 1 1/2 year hiatus, I'm in New Albany also and I've had crazy lag through Metrocast. I have a feeling Netflix and other popular games are getting throttled at the port
87 Human Warrior
3390
02/01/2013 12:01 AMPosted by False
Can we please get a blue post update with some substance on this issue? I am to the point if this isn't fixed in two weeks, I am canceling my subscription. This is going on for entirely too long.


There have been a lot of blue posts already. Blizz has stated multiple times that it's not their fault, it's on the fault of ISP's, but I believe it's strictly Cogentco's fault. When I called them, the guy was pretty ticked already it seemed, and he was being snappy with me as if he knew there was an issue and he was sick of hearing about it and he wouldn't admit to it being their fault but he didn't say it wasn't their fault. I believe that it's not Blizzard's fault. And I don't think Cogentco really cares because it's just a game... Even though we are probably a lot of their revenue, noobs.

I feel your pain though friend! Hopefully it fixes soon.. Path of Exile ftw for the times when it's just too crappy haha.
90 Troll Hunter
9230
Facing similar issue from India. Disconnects very frequently - sometimes immediately on logging into the world.

Realm: US-Burning Legion
City: Kolkata
State, Country: West Bengal, India
ISP: Wishnet

Pathping:

Tracing route to 63.240.161.189 over a maximum of 30 hops

0 Bhaswar-PC [172.16.111.25]
1 host_bb.wishnetkolkata.com [172.16.111.1]
2 172.30.1.17
3 172.30.1.21
4 172.30.1.29
5 172.30.1.57
6 host_bb.wishnetkolkata.com [223.223.152.1]
7 121.241.208.241.static-kolkata.vsnl.net.in [121.241.208.241]
8 172.31.17.13
9 if-3-1.mcore3.L78-London.as6453.net [195.219.144.117]
10 if-0-0-2-0.tcore1.L78-London.as6453.net [80.231.130.49]
11 if-7-2.tcore1.NJY-Newark.as6453.net [66.198.70.25]
12 if-2-2.tcore2.NJY-Newark.as6453.net [66.198.70.2]
13 if-3-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.9]
14 192.205.34.245
15 cr2.wswdc.ip.att.net [12.122.84.82]
16 cr1.cgcil.ip.att.net [12.122.18.21]
17 gar2.clboh.ip.att.net [12.122.133.197]
18 12.122.251.50
19 63.240.130.214
20 * * *
Computing statistics for 475 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Bhaswar-PC [172.16.111.25]
1/ 100 = 1% |
1 1ms 2/ 100 = 2% 1/ 100 = 1% host_bb.wishnetkolkata.com [172.16.111.1]
0/ 100 = 0% |
2 2ms 1/ 100 = 1% 0/ 100 = 0% 172.30.1.17
0/ 100 = 0% |
3 2ms 1/ 100 = 1% 0/ 100 = 0% 172.30.1.21
0/ 100 = 0% |
4 1ms 1/ 100 = 1% 0/ 100 = 0% 172.30.1.29
0/ 100 = 0% |
5 1ms 1/ 100 = 1% 0/ 100 = 0% 172.30.1.57
0/ 100 = 0% |
6 5ms 3/ 100 = 3% 2/ 100 = 2% host_bb.wishnetkolkata.com [223.223.152.1]
0/ 100 = 0% |
7 9ms 2/ 100 = 2% 1/ 100 = 1% 121.241.208.241.static-kolkata.vsnl.net.in [121.241.208.241]
0/ 100 = 0% |
8 41ms 1/ 100 = 1% 0/ 100 = 0% 172.31.17.13
0/ 100 = 0% |
9 170ms 1/ 100 = 1% 0/ 100 = 0% if-3-1.mcore3.L78-London.as6453.net [195.219.144.117]
1/ 100 = 1% |
10 173ms 3/ 100 = 3% 1/ 100 = 1% if-0-0-2-0.tcore1.L78-London.as6453.net [80.231.130.49]
0/ 100 = 0% |
11 248ms 2/ 100 = 2% 0/ 100 = 0% if-7-2.tcore1.NJY-Newark.as6453.net [66.198.70.25]
0/ 100 = 0% |
12 247ms 2/ 100 = 2% 0/ 100 = 0% if-2-2.tcore2.NJY-Newark.as6453.net [66.198.70.2]
1/ 100 = 1% |
13 246ms 3/ 100 = 3% 0/ 100 = 0% if-3-2.tcore2.AEQ-Ashburn.as6453.net [216.6.87.9]
0/ 100 = 0% |
14 297ms 3/ 100 = 3% 0/ 100 = 0% 192.205.34.245
97/ 100 = 97% |
15 --- 100/ 100 =100% 0/ 100 = 0% cr2.wswdc.ip.att.net [12.122.84.82]
0/ 100 = 0% |
16 --- 100/ 100 =100% 0/ 100 = 0% cr1.cgcil.ip.att.net [12.122.18.21]
0/ 100 = 0% |
17 --- 100/ 100 =100% 0/ 100 = 0% gar2.clboh.ip.att.net [12.122.133.197]
0/ 100 = 0% |
18 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.50
0/ 100 = 0% |
19 --- 100/ 100 =100% 0/ 100 = 0% 63.240.130.214

Trace complete.
Edited by Xailoh on 2/1/2013 10:15 PM PST
100 Undead Priest
17420
Realm: US-Ner'zhul
Location: Stillwater, Oklahoma
ISP: Oklahoma State University

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms ro-peterson.peterson.rl [10.192.59.254]
2 <1 ms <1 ms <1 ms 139.78.255.38
3 1 ms 1 ms <1 ms 139.78.255.32
4 1 ms 1 ms 1 ms thor-thorfw2.net.okstate.edu [139.78.1.161]
5 <1 ms 2 ms 1 ms 164.58.10.65
6 2 ms 2 ms 2 ms 164.58.246.125
7 2 ms 2 ms 2 ms 164.58.245.234
8 2 ms 2 ms 2 ms te4-4.1052.ccr01.tul01.atlas.cogentco.com [38.104.198.69]
9 8 ms 8 ms 8 ms te0-2-0-7.ccr22.dfw01.atlas.cogentco.com [154.54.5.13]
10 13 ms 13 ms 13 ms te0-1-0-7.ccr22.iah01.atlas.cogentco.com [154.54.0.205]
11 49 ms 49 ms 49 ms te0-1-0-6.ccr22.lax01.atlas.cogentco.com [66.28.4.238]
12 49 ms 49 ms 50 ms te0-6-0-2.ccr22.lax05.atlas.cogentco.com [154.54.88.193]
13 92 ms 91 ms 85 ms 192.205.35.5
14 92 ms 85 ms 87 ms cr2.la2ca.ip.att.net [12.122.84.218]
15 89 ms 82 ms 86 ms gar29.la2ca.ip.att.net [12.122.129.241]
16 198 ms 216 ms 93 ms 12.122.251.190
17 90 ms 88 ms 82 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
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 12.129.209.68 over a maximum of 30 hops

0 Drew-PC.v738.osu [10.192.58.74]
1 ro-peterson.peterson.rl [10.192.59.254]
2 139.78.255.38
3 139.78.255.32
4 thor-thorfw2.net.okstate.edu [139.78.1.161]
5 164.58.10.65
6 164.58.246.125
7 164.58.245.234
8 te4-4.1052.ccr01.tul01.atlas.cogentco.com [38.104.198.69]
9 te0-2-0-7.ccr22.dfw01.atlas.cogentco.com [154.54.5.13]
10 te0-1-0-7.ccr22.iah01.atlas.cogentco.com [154.54.0.205]
11 te0-1-0-6.ccr22.lax01.atlas.cogentco.com [66.28.4.238]
12 te0-6-0-2.ccr22.lax05.atlas.cogentco.com [154.54.88.193]
13 192.205.35.5
14 cr1.la2ca.ip.att.net [12.122.84.202]
15 gar29.la2ca.ip.att.net [12.122.129.241]
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...
90 Blood Elf Priest
13150
If the problem isn't resolved in about a week when I have to renew SmoothPing, I'll likely be taking a break and/or quitting. I've completed this tier, and it's at least a couple months until the next. No point in wasting money on farm content. Guild Wars will be my casual (and possibly permanent) game for a while I think. With some Xbox live thrown in there.
100 Human Paladin
16775
Anyone had any luck getting through to their ISP that them routing around cogentco is the only viable solution? It's really hard to convince them that 1) it's not blizzards problem, and 2) that they are in fact capable of routing around the affected path.
100 Undead Priest
12620
I currently have a BBB complaint in that has been forwarded to the Cox Comm main office in Phoenix. The person I am in contact with is an engineer and claims to be working to fix this. I dont know if this is the actual case but this is what I am being told. Im going to forward them the information from another PC that is connecting via Century Link so they can see the problem. My ISP has stated that they know its an issue that rerouting can fix but that rerouting is not feasible at this time because this is the optimal route to get my data from the greater Tucson area to the Blizzard servers. If the person that I am talking to requires additional information I will post the email address that he asks me to email more tracerts to so that others can fill his email box with hate mail.
Edited by Jonthebaptst on 2/2/2013 1:44 AM PST
87 Blood Elf Hunter
7545
Not in AZ, but am unable to play effectively on servers connected to the Chicago and New York database. The issue started for me about a week and a half ago and is only gotten worse over time. The latency spikes up to 1000 and the game freezes now quite a bit. My internet is provided by comcast coming from Florida.

I have updated and gone to the length of removing addons without any luck there. I have tried turning down the graphics system so it is definitely not a computer related issue.

So far I didn't see any complaints relating to my state or provider, so in my case should I call comcast or is this in relation to the issues expressed on this thread?
90 Troll Hunter
14660
As an aside, maybe if players could see what their connection was like to a particular server at the Realm Selection screen, they would be more inclined to choose a server geographically closer to them which would reduce the likelihood of connection issues in the first place.

Adding this info and ratio of Horde to Alliance as well would be helpful for players to make an informed choice about where they want to play without digging up info on the net which may not even be accurate.

Just my two cents.
93 Draenei Warrior
13255
Not in AZ, but am unable to play effectively on servers connected to the Chicago and New York database. The issue started for me about a week and a half ago and is only gotten worse over time. The latency spikes up to 1000 and the game freezes now quite a bit. My internet is provided by comcast coming from Florida.

I have updated and gone to the length of removing addons without any luck there. I have tried turning down the graphics system so it is definitely not a computer related issue.

So far I didn't see any complaints relating to my state or provider, so in my case should I call comcast or is this in relation to the issues expressed on this thread?


If you run a tracer or path ping and see Cogentco servers in your hops then you are affected. I've complained to my ISP about rerouting and they say it isn't an option. So I guess I wait until Cogent fixes their stuff.
90 Worgen Warlock
14465
02/02/2013 06:22 AMPosted by Mal
I have tried turning down the graphics system so it is definitely not a computer related issue.


*headdesk*

Computer settings don't make you lag. They can cause screen tearing and FPS loss, but lag is almost entirely internet related.

#themoreyouknow
91 Human Rogue
11590
tracert 206.18.148.200

Tracing route to 206.18.148.200 over a maximum of 30 hops

3 9 ms 19 ms 12 ms 172.21.1.132
4 24 ms 23 ms 24 ms 70.169.73.24
5 13 ms 12 ms 11 ms 70.169.75.153
6 * * * Request timed out.
7 28 ms 25 ms 29 ms te0-7-0-21.ccr22.lax05.atlas.cogentco.com [154.5
4.13.129]
8 26 ms 25 ms 32 ms te0-1-0-1.mpd22.lax01.atlas.cogentco.com [154.54
.3.9]
9 61 ms 59 ms 61 ms te0-1-0-6.ccr22.iah01.atlas.cogentco.com [66.28.
4.237]
10 65 ms 66 ms 67 ms te0-3-0-5.ccr22.dfw01.atlas.cogentco.com [154.54
.24.26]
11 89 ms 81 ms 94 ms te0-3-0-2.ccr22.mci01.atlas.cogentco.com [154.54
.25.210]
12 90 ms 90 ms 92 ms te0-7-0-33.ccr22.ord01.atlas.cogentco.com [154.5
4.30.102]
13 91 ms 163 ms 110 ms te0-5-0-7.ccr22.ord03.atlas.cogentco.com [154.54
.44.166]
14 * 101 ms 179 ms att.ord03.atlas.cogentco.com [154.54.12.86]
15 120 ms 124 ms 104 ms cr2.cgcil.ip.att.net [12.122.84.94]
16 99 ms 101 ms 98 ms gar3.cgcil.ip.att.net [12.122.132.213]
17 101 ms 103 ms 114 ms 12.122.251.22
18 104 ms 100 ms 101 ms 63.240.130.210
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]