Ontario ROGERS users - Latency/Disconnecting

90 Troll Druid
8320
I only started having latency issues ~30 minutes ago (I'm with Rogers and in the GTA). The rest of the day/past couple days have been fine for the most part. This sucks. :(
Reply Quote
100 Human Paladin
4400
any news on when it will be fixed i cant queue for heroics or even do dailies : (
Reply Quote
90 Human Paladin
4860
Yea same I am in Ottawa as well using rogers was fine until about 3 hours ago. I have 500 home and 6k world it is unplayable. Sucks i was looking forward to a night playing with friends and explore the expansion
Reply Quote
90 Worgen Warlock
1970
09/29/2012 08:22 PMPosted by Angryeric
Looks like they're treating wow like a P2P file sharing program again .... I hate rogers, but the other Canadian telco's aren't any better .... Canadians really get the short end of the stick when it comes to internet services.


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.

http://promo.orderrogers.ca/trafficmanagement/en/?cm_mmc=Redirects-_-Consumer_Traffic_ENG-_-Traffic_2012-_-traffic
Reply Quote
09/29/2012 09:01 PMPosted by Kaldrax
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.


Says the traffic management has been removed in my area
Reply Quote
90 Orc Warrior
11960
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....
Reply Quote
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 206.16.118.151 (206.16.118.151), 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 7.48.164.1 (7.48.164.1) 8.121 ms 8.677 ms 7.852 ms
3 69.63.254.141 (69.63.254.141) 24.501 ms 20.817 ms 9.895 ms
4 gi-0-1-3.gw01.grnsbr.phub.net.cable.rogers.com (24.153.7.1) 18.925 ms 18.972 ms 20.194 ms
5 69.63.251.233 (69.63.251.233) 17.054 ms 19.114 ms 18.876 ms
6 69.63.248.89 (69.63.248.89) 34.380 ms 31.655 ms 30.425 ms
7 tengigabitethernet3-1.ar4.nyc1.gblx.net (67.17.156.109) 31.684 ms 32.104 ms 30.258 ms
8 192.205.32.137 (192.205.32.137) 136.280 ms 137.248 ms *
9 cr1.la2ca.ip.att.net (12.122.128.98) 151.756 ms 151.293 ms 147.598 ms
10 cr2.phmaz.ip.att.net (12.122.31.190) 149.117 ms 153.142 ms *
11 12.123.158.129 (12.123.158.129) 148.572 ms 148.310 ms *
12 12-122-254-50.attens.net (12.122.254.50) 307.556 ms 207.624 ms 207.532 ms
13 mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 153.070 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 149.005 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 150.317 ms
14 * * *

30ms to 130ms~ with some packets being dropped.

NetRange: 192.205.0.0 - 192.205.255.255
CIDR: 192.205.0.0/16
OriginAS:
NetName: NETBLK-ATT
NetHandle: NET-192-205-0-0-1
Parent: NET-192-0-0-0-0
NetType: Direct Allocation
RegDate: 1992-08-03
Updated: 2012-04-02
Ref: http://whois.arin.net/rest/net/NET-192-205-0-0-1

OrgName: AT&T Services, Inc.
Reply Quote
90 Human Priest
8815
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 206.16.118.151 (206.16.118.151), 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 7.48.164.1 (7.48.164.1) 8.121 ms 8.677 ms 7.852 ms
3 69.63.254.141 (69.63.254.141) 24.501 ms 20.817 ms 9.895 ms
4 gi-0-1-3.gw01.grnsbr.phub.net.cable.rogers.com (24.153.7.1) 18.925 ms 18.972 ms 20.194 ms
5 69.63.251.233 (69.63.251.233) 17.054 ms 19.114 ms 18.876 ms
6 69.63.248.89 (69.63.248.89) 34.380 ms 31.655 ms 30.425 ms
7 tengigabitethernet3-1.ar4.nyc1.gblx.net (67.17.156.109) 31.684 ms 32.104 ms 30.258 ms
8 192.205.32.137 (192.205.32.137) 136.280 ms 137.248 ms *
9 cr1.la2ca.ip.att.net (12.122.128.98) 151.756 ms 151.293 ms 147.598 ms
10 cr2.phmaz.ip.att.net (12.122.31.190) 149.117 ms 153.142 ms *
11 12.123.158.129 (12.123.158.129) 148.572 ms 148.310 ms *
12 12-122-254-50.attens.net (12.122.254.50) 307.556 ms 207.624 ms 207.532 ms
13 mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 153.070 ms
mdf002c7613r0002-gig-10-1.phx1.attens.net (63.241.130.206) 149.005 ms
mdf002c7613r0001-gig-12-1.phx1.attens.net (63.241.130.210) 150.317 ms
14 * * *

30ms to 130ms~ with some packets being dropped.

NetRange: 192.205.0.0 - 192.205.255.255
CIDR: 192.205.0.0/16
OriginAS:
NetName: NETBLK-ATT
NetHandle: NET-192-205-0-0-1
Parent: NET-192-0-0-0-0
NetType: Direct Allocation
RegDate: 1992-08-03
Updated: 2012-04-02
Ref: http://whois.arin.net/rest/net/NET-192-205-0-0-1

OrgName: AT&T Services, Inc.


Same results here it's some AT&T routers that need fixing or bypassing...
Reply Quote
90 Blood Elf Hunter
5300
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
Reply Quote
97 Orc Death Knight
12360
Just tossing my name into the hat. Ottawa user on Rogers, unplayable latency as of about an hour or two ago.

Because what I really needed was another reason to hate Rogers.
Reply Quote
Hping3 TCP SYN packet to port 3724 206.16.118.151

HPING 206.16.118.151 (eth0 206.16.118.151): S set, 40 headers + 0 data bytes
len=46 ip=206.16.118.151 ttl=44 id=11852 sport=3724 flags=SA seq=0 win=5840 rtt=153.4 ms
len=46 ip=206.16.118.151 ttl=44 id=27426 sport=3724 flags=SA seq=1 win=5840 rtt=148.2 ms
len=46 ip=206.16.118.151 ttl=44 id=27668 sport=3724 flags=SA seq=3 win=5840 rtt=151.0 ms
len=46 ip=206.16.118.151 ttl=44 id=49736 sport=3724 flags=SA seq=5 win=5840 rtt=150.3 ms
len=46 ip=206.16.118.151 ttl=44 id=47442 sport=3724 flags=SA seq=6 win=5840 rtt=148.4 ms
len=46 ip=206.16.118.151 ttl=44 id=43537 sport=3724 flags=SA seq=2 win=5840 rtt=4347.2 ms
len=46 ip=206.16.118.151 ttl=44 id=24403 sport=3724 flags=SA seq=7 win=5840 rtt=151.9 ms
len=46 ip=206.16.118.151 ttl=44 id=56108 sport=3724 flags=SA seq=4 win=5840 rtt=4144.4 ms
len=46 ip=206.16.118.151 ttl=44 id=12914 sport=3724 flags=SA seq=8 win=5840 rtt=149.2 ms
len=46 ip=206.16.118.151 ttl=44 id=33551 sport=3724 flags=SA seq=9 win=5840 rtt=150.3 ms
len=46 ip=206.16.118.151 ttl=44 id=3362 sport=3724 flags=SA seq=11 win=5840 rtt=149.5 ms
len=46 ip=206.16.118.151 ttl=44 id=15468 sport=3724 flags=SA seq=12 win=5840 rtt=151.0 ms
len=46 ip=206.16.118.151 ttl=44 id=865 sport=3724 flags=SA seq=10 win=5840 rtt=3146.0 ms
len=46 ip=206.16.118.151 ttl=44 id=60211 sport=3724 flags=SA seq=13 win=5840 rtt=148.4 ms
len=46 ip=206.16.118.151 ttl=44 id=3613 sport=3724 flags=SA seq=14 win=5840 rtt=148.9 ms
len=46 ip=206.16.118.151 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
Reply Quote
90 Human Hunter
8595
Ottawa reporting in, lagging like a madman. Appears to be AT&T for me:

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

1 <1 ms <1 ms <1 ms READYSHARE [192.168.1.1]
2 8 ms 7 ms 7 ms 7.45.232.1
3 11 ms 11 ms 11 ms 24.156.151.101
4 16 ms 14 ms 27 ms so-4-0-0.gw02.ym.phub.net.cable.rogers.com [66.1
85.82.125]
5 16 ms 15 ms 15 ms so-2-0-0.gw02.mtnk.phub.net.cable.rogers.com [66
.185.80.185]
6 29 ms 30 ms 31 ms 69.63.248.97
7 28 ms 28 ms 29 ms tengigabitethernet3-4.ar4.nyc1.gblx.net [64.208.
169.149]
8 84 ms 82 ms 84 ms te-9-4-10G.ar2.CHI2.gblx.net [64.208.110.162]
9 86 ms 86 ms 87 ms cr2.cgcil.ip.att.net [12.122.132.158]
10 84 ms 82 ms 86 ms gar3.cgcil.ip.att.net [12.122.132.213]
11 * 86 ms 84 ms 12.122.251.50
12 85 ms 84 ms * 63.240.130.214
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
....
30 * * * Request timed out.

Trace complete.

IP lookup for 63.240.130.214 lists it as being registered to CERFNet, which is a part of AT&T.
Reply Quote
90 Tauren Hunter
13845
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
Reply Quote
Does anyone know if this will be fixed? Or is 'this' just how things are going to be now?
Reply Quote
90 Human Hunter
8595
09/29/2012 10:38 PMPosted by Andore
Does anyone know if this will be fixed? Or is 'this' just how things are going to be now?

That's up to AT&T. Their servers are the ones causing the problems.
Reply Quote
92 Tauren Warrior
13715
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.

Edit:
Does anyone know if this will be fixed? Or is 'this' just how things are going to be now?

That's up to AT&T. Their servers are the ones causing the problems.


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
Reply Quote
90 Tauren Hunter
13845
Maybe it's a herald of the end of the world! IPv4 ADDRESSES ARE ALL GONE!

GG guys, gg.
Reply Quote
100 Human Paladin
4400
Will this be fixed anytime soon im relapsing over here.
Reply Quote
90 Night Elf Druid
8320
Is this on Rogers end or Blizzards?
Reply Quote
Noticed its a lot better now, not 100% playable, sitting at around 200/300 home/world ms.

Down from the quad digits.
Reply Quote

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]