Get the Desktop App for Battle.net Now
- All your games in 1 place
- Log in once
- Automatic game updates
For most people Rogers has still been consistently treating WoW traffic as P2P. Rogers has pledged to have everyone unthrottled starting 2013 and have been really slow to roll out the unthrottling.
You can check here to see if your area is still throttled by its old traffic management policy.
Says the traffic management has been removed in my area
My traffic management has been removed in the area, but it's lagging @ 2.5k MS and has made it currently next to unplayable aside from chatting in guild, and even then the delays are disgusting. Rogers sucks, but its unfortunately better than anything else around currently. We really have the bad end of the stick for internet providers and terms....
I'm in Ottawa on Rogers and seeing the same thing.
Looks like it's not even a rogers problem but on the AT&T core routers:
traceroute to 184.108.40.206 (220.127.116.11), 64 hops max, 52 byte packets
1 10.0.1.1 (10.0.1.1) 0.402 ms 0.377 ms 0.212 ms
2 18.104.22.168 (22.214.171.124) 8.121 ms 8.677 ms 7.852 ms
3 126.96.36.199 (188.8.131.52) 24.501 ms 20.817 ms 9.895 ms
4 gi-0-1-3.gw01.grnsbr.phub.net.cable.rogers.com (184.108.40.206) 18.925 ms 18.972 ms 20.194 ms
5 220.127.116.11 (18.104.22.168) 17.054 ms 19.114 ms 18.876 ms
6 22.214.171.124 (126.96.36.199) 34.380 ms 31.655 ms 30.425 ms
7 tengigabitethernet3-1.ar4.nyc1.gblx.net (188.8.131.52) 31.684 ms 32.104 ms 30.258 ms
8 184.108.40.206 (220.127.116.11) 136.280 ms 137.248 ms *
9 cr1.la2ca.ip.att.net (18.104.22.168) 151.756 ms 151.293 ms 147.598 ms
10 cr2.phmaz.ip.att.net (22.214.171.124) 149.117 ms 153.142 ms *
11 126.96.36.199 (188.8.131.52) 148.572 ms 148.310 ms *
12 12-122-254-50.attens.net (184.108.40.206) 307.556 ms 207.624 ms 207.532 ms
13 mdf002c7613r0001-gig-12-1.phx1.attens.net (220.127.116.11) 153.070 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (18.104.22.168) 149.005 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (22.214.171.124) 150.317 ms
14 * * *
30ms to 130ms~ with some packets being dropped.
NetRange: 126.96.36.199 - 188.8.131.52
NetType: Direct Allocation
OrgName: AT&T Services, Inc.
I'm in Ottawa on Rogers and seeing the same thing.
Same results here it's some AT&T routers that need fixing or bypassing...
Thanks for this info! I'm with Rogers, GTA Ontario and latency suddenly started spiking about an hour and a half ago, both world and home. Totally unplayable.
Checked my area and traffic management has not been removed yet
Edited by Moonmyst on 9/29/2012 9:25 PM PDT
Hping3 TCP SYN packet to port 3724 184.108.40.206
HPING 220.127.116.11 (eth0 18.104.22.168): S set, 40 headers + 0 data bytes
len=46 ip=22.214.171.124 ttl=44 id=11852 sport=3724 flags=SA seq=0 win=5840 rtt=153.4 ms
len=46 ip=126.96.36.199 ttl=44 id=27426 sport=3724 flags=SA seq=1 win=5840 rtt=148.2 ms
len=46 ip=188.8.131.52 ttl=44 id=27668 sport=3724 flags=SA seq=3 win=5840 rtt=151.0 ms
len=46 ip=184.108.40.206 ttl=44 id=49736 sport=3724 flags=SA seq=5 win=5840 rtt=150.3 ms
len=46 ip=220.127.116.11 ttl=44 id=47442 sport=3724 flags=SA seq=6 win=5840 rtt=148.4 ms
len=46 ip=18.104.22.168 ttl=44 id=43537 sport=3724 flags=SA seq=2 win=5840 rtt=4347.2 ms
len=46 ip=22.214.171.124 ttl=44 id=24403 sport=3724 flags=SA seq=7 win=5840 rtt=151.9 ms
len=46 ip=126.96.36.199 ttl=44 id=56108 sport=3724 flags=SA seq=4 win=5840 rtt=4144.4 ms
len=46 ip=188.8.131.52 ttl=44 id=12914 sport=3724 flags=SA seq=8 win=5840 rtt=149.2 ms
len=46 ip=184.108.40.206 ttl=44 id=33551 sport=3724 flags=SA seq=9 win=5840 rtt=150.3 ms
len=46 ip=220.127.116.11 ttl=44 id=3362 sport=3724 flags=SA seq=11 win=5840 rtt=149.5 ms
len=46 ip=18.104.22.168 ttl=44 id=15468 sport=3724 flags=SA seq=12 win=5840 rtt=151.0 ms
len=46 ip=22.214.171.124 ttl=44 id=865 sport=3724 flags=SA seq=10 win=5840 rtt=3146.0 ms
len=46 ip=126.96.36.199 ttl=44 id=60211 sport=3724 flags=SA seq=13 win=5840 rtt=148.4 ms
len=46 ip=188.8.131.52 ttl=44 id=3613 sport=3724 flags=SA seq=14 win=5840 rtt=148.9 ms
len=46 ip=184.108.40.206 ttl=44 id=59942 sport=3724 flags=SA seq=15 win=5840 rtt=149.3 ms
DAT LATENCY/PACKET LOSS BRO!
SORRY FOR THAT SYN FLOOD :( :(
Edited by Positif on 9/29/2012 10:05 PM PDT
Ottawa reporting in, lagging like a madman. Appears to be AT&T for me:
IP lookup for 220.127.116.11 lists it as being registered to CERFNet, which is a part of AT&T.
Yeah, I've been running Trace routes and it's just really frustrating to see this.
Problem is, I can't switch because Bell sucks just as bad, and TekSavvy borrows the infrastructure that Rogers owns.
Screw everything about Rogers.
...would be really nice for them to stop screwing with Warcraft; it's starting to piss me off.
Edited by Serahu on 9/29/2012 10:20 PM PDT
Seems like a wierd coincidence this specific problem with ISP is happening at the same time players from all over the US and other countries on different isp's have been experiencing massive world server latency (quadruple digits)
Hopefully for you Canadians, it IS an ISP issue and goes away once Rogers fixes their end. Unfortunately, the rest of us will prolly be SOL till Blizz ninja reverts/fixes whatever ent in on the last hotfix/patch that is making the game unplayable for the rest of us.
Does anyone know if this will be fixed? Or is 'this' just how things are going to be now?
There has to be more to is than an ISP side issue. I find it hard to believe that virtually every ISP in the US is having the same problem and it is only affecting WoW. US players reporting this massive world latency issue are on a host of differing ISP's using both cable and DSL in entirely different sections of the country.
And none of us are having any problems with any other online service or application. It's only affecting WoW.
Edited by Mookosh on 9/29/2012 11:35 PM PDT
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.