For past few days crazy rubberband lag on a powerful rig with 10ms/70+ Mbps connect..

[Desypher]

This is through Verizon Fios, in the Carrollton, TX area... Getting BAD amounts of rubber band lag on an extremely good pc rig (i7 max processor, 16gig ram, 4gig vid card current gen...

its applying to whole game but really bad in pvp and trials which makes things unplayable....

Can you please notify FIOS to have them update their route??




Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\.....>tracert 199.91.189.57

Tracing route to 199.91.189.57 over a maximum of 30 hops

1 16 ms 1 ms 7 ms Wireless_Broadband_Router.home [192.168.1.1]
2 21 ms 8 ms 15 ms L100.DLLSTX-VFTTP-49.verizon-gni.net [173.64.199
.1]
3 27 ms 16 ms 24 ms G0-5-4-1.DLLSTX-LCR-21.verizon-gni.net [130.81.1
84.181]
4 44 ms 16 ms 24 ms ae3-0.DFW9-BB-RTR1.verizon-gni.net [130.81.199.5
8]
5 28 ms 9 ms 22 ms 0.xe-3-1-2.BR2.DFW13.ALTER.NET [152.63.99.241]
6 19 ms 15 ms 16 ms ae8.edge10.dallas3.level3.com [4.68.62.33]
7 71 ms 65 ms 66 ms vlan70.csw2.Dallas1.Level3.net [4.69.145.126]
8 81 ms 72 ms 74 ms ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138]

9 70 ms 65 ms 133 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

10 80 ms 67 ms 73 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]

11 78 ms 68 ms 72 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
12 67 ms * * ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

13 72 ms 66 ms 66 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
14 86 ms 82 ms 74 ms 192.34.76.10
15 86 ms 83 ms 183 ms 199.91.189.242
16 81 ms 100 ms 81 ms 199.91.189.57

Trace complete.

C:\Users\Patrick>

[Raist]

This is through Verizon Fios, in the Carrollton, TX area... Getting BAD amounts of rubber band lag on an extremely good pc rig (i7 max processor, 16gig ram, 4gig vid card current gen...

its applying to whole game but really bad in pvp and trials which makes things unplayable....

Can you please notify FIOS to have them update their route??




Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\.....>tracert 199.91.189.57

Tracing route to 199.91.189.57 over a maximum of 30 hops

1 16 ms 1 ms 7 ms Wireless_Broadband_Router.home [192.168.1.1]
2 21 ms 8 ms 15 ms L100.DLLSTX-VFTTP-49.verizon-gni.net [173.64.199
.1]
3 27 ms 16 ms 24 ms G0-5-4-1.DLLSTX-LCR-21.verizon-gni.net [130.81.1
84.181]
4 44 ms 16 ms 24 ms ae3-0.DFW9-BB-RTR1.verizon-gni.net [130.81.199.5
8]
5 28 ms 9 ms 22 ms 0.xe-3-1-2.BR2.DFW13.ALTER.NET [152.63.99.241]
6 19 ms 15 ms 16 ms ae8.edge10.dallas3.level3.com [4.68.62.33]
7 71 ms 65 ms 66 ms vlan70.csw2.Dallas1.Level3.net [4.69.145.126]
8 81 ms 72 ms 74 ms ae-71-71.ebr1.Dallas1.Level3.net [4.69.151.138]

9 70 ms 65 ms 133 ms ae-14-14.ebr2.Chicago2.Level3.net [4.69.151.117]

10 80 ms 67 ms 73 ms ae-1-100.ebr1.Chicago2.Level3.net [4.69.132.113]

11 78 ms 68 ms 72 ms ae-6-6.ebr1.Chicago1.Level3.net [4.69.140.189]
12 67 ms * * ae-10-10.car2.Montreal2.Level3.net [4.69.153.86]

13 72 ms 66 ms 66 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
14 86 ms 82 ms 74 ms 192.34.76.10
15 86 ms 83 ms 183 ms 199.91.189.242
16 81 ms 100 ms 81 ms 199.91.189.57

Trace complete.

C:\Users\Patrick>

May stand a better chance of getting action taken if you contact them yourself, since you are paying Verizon for their services and not SE. The problem appears to lie more in the realm of Level3's control, who your ISP has partnered with to carry your data off their local segments and across the US/Canada to SE's ISP (Ormuco). At best, SE could work with Ormuco if there are problems at their end, but anything outside of those last few hops, it really falls to your ISP to negotiate with their partners to resolve issues. You pay Verizon, and they pay Level3--so in a round-a-bout way, you are contributing to their paycheck and not SE. So they really have no incentive to respond to any requests from SE.

[txfeinbergs]

This has nothing to do with Verizon. Ever since the latest patch update on the 24th, things have been horrible. I live not far from you in Allen, with Time Warner cable, and it isn't even playable right now.

[Desypher]

cool thanks for confirmation txfienbergs, it definitely was NEVER an issue before this patch, i think when they broke of their segments into seperate data centers they didnt do any optimization of routes through their WAN links.... 16 hops seems pretty excessive...

Either way i even tried 'just for $hits and giggles' to disable various troublesome effects in MMO's (shaders, shadows, AA, etc) and didnt help.... just seems to be network related somehow...

will contact verizon tech support, but doubt they will do anything either, just trying to raise awareness..

[Shados]

It is network related, and while its not verizon directly, it has to do with who Verizon hooks up to, to route traffic all the way to SE, as someone already mentionned. A disproportionate amount of Fios users (along with a few other ISPs, or portion of subscribers of ISPs, depending on region) have that same issue. Lots of threads about it on this forum.

It affects people during peek times. One can only assume it started again with 2.1 because there's more users (as people came back). It was almost completely gone before 2.1 hit.

[Felicity]

cool thanks for confirmation txfienbergs, it definitely was NEVER an issue before this patch, i think when they broke of their segments into seperate data centers they didnt do any optimization of routes through their WAN links.... 16 hops seems pretty excessive...

Either way i even tried 'just for $hits and giggles' to disable various troublesome effects in MMO's (shaders, shadows, AA, etc) and didnt help.... just seems to be network related somehow...

will contact verizon tech support, but doubt they will do anything either, just trying to raise awareness..

Please let me know how your conversation with them goes as I am having the same issue and am on Verizon in Irving, TX.

[Tanama]

I am having the same issue as well with Verizon FiOS up here in the northeast.

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


Tracing route to 199.91.189.30 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 6 ms 8 ms L100.BSTNMA-VFTTP-132.verizon-gni.net [98.118.103.1]
3 9 ms 6 ms 8 ms G0-10-4-7.BSTNMA-LCR-22.verizon-gni.net [130.81.218.42]
4 6 ms 9 ms 6 ms ae4-0.BOS-BB-RTR2.verizon-gni.net [130.81.151.84]
5 17 ms 16 ms 17 ms 0.xe-9-0-0.BR1.NYC1.ALTER.NET [152.63.19.213]
6 * 28 ms 29 ms ae11.edge2.NewYork.Level3.net [4.68.62.41]
7 37 ms 39 ms 36 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8 38 ms 36 ms 41 ms ae-46-46.ebr2.NewYork1.Level3.net [4.69.201.29]

9 39 ms 39 ms 41 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
10 26 ms 26 ms 25 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

11 40 ms 44 ms 41 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
12 40 ms 42 ms 44 ms 192.34.76.10
13 39 ms 42 ms 41 ms 199.91.189.242
14 44 ms 41 ms 44 ms 199.91.189.30

Trace complete.

---------------------------------------------------------------------

Tracing route to 199.91.189.30 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 7 ms 6 ms 6 ms L100.BSTNMA-VFTTP-132.verizon-gni.net [98.118.103.1]
3 8 ms 6 ms 9 ms G0-10-4-7.BSTNMA-LCR-22.verizon-gni.net [130.81.218.42]
4 8 ms 8 ms 7 ms ae4-0.BOS-BB-RTR2.verizon-gni.net [130.81.151.84]
5 18 ms 16 ms 19 ms 0.xe-9-0-0.BR1.NYC1.ALTER.NET [152.63.19.213]
6 29 ms 31 ms 31 ms ae11.edge2.NewYork.Level3.net [4.68.62.41]
7 43 ms 42 ms 41 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8 39 ms 36 ms 39 ms ae-46-46.ebr2.NewYork1.Level3.net [4.69.201.29]

9 93 ms 206 ms 208 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
10 24 ms 24 ms 26 ms ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

11 40 ms 39 ms 41 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.74]
12 40 ms 41 ms 43 ms 192.34.76.10
13 45 ms 39 ms 42 ms 199.91.189.242
14 43 ms 44 ms 46 ms 199.91.189.30

Trace complete.

[Katagai]

I'm in central Florida and also having the same issues with Verizon FiOS. It's been progressively getting worse since patch 2.1 came out and as of today, the game is nearly unplayable.

Not sure if it'll be of any help, but here is my tracert log:


Tracing route to 199.91.189.57 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 5 ms 6 ms L100.TAMPFL-VFTTP-134.verizon-gni.net [96.254.111.1]
3 11 ms 12 ms 10 ms G0-9-2-3.TAMPFL-LCR-22.verizon-gni.net [130.81.140.60]
4 6 ms 9 ms 10 ms ae2-0.TPA01-BB-RTR2.verizon-gni.net [130.81.199.82]
5 13 ms 13 ms 12 ms 0.ae2.BR1.MIA19.ALTER.NET [152.63.87.178]
6 56 ms 57 ms 56 ms 204.255.168.30
7 58 ms 56 ms 59 ms be2054.ccr21.mia01.atlas.cogentco.com [154.54.80.41]
8 82 ms 80 ms 75 ms be2122.ccr21.atl01.atlas.cogentco.com [154.54.24.193]
9 89 ms 93 ms 93 ms be2168.ccr21.dca01.atlas.cogentco.com [154.54.31.94]
10 93 ms 97 ms 98 ms be2148.ccr21.jfk02.atlas.cogentco.com [154.54.31.118]
11 96 ms 92 ms 99 ms be2106.ccr21.ymq02.atlas.cogentco.com [154.54.3.50]
12 136 ms 137 ms 141 ms 38.122.42.34
13 73 ms 73 ms 110 ms 192.34.76.10
14 74 ms 73 ms 73 ms 199.91.189.242
15 73 ms 75 ms 72 ms 199.91.189.57

Trace complete.

[Cryptix_Durden]

Problem: Experiencing lagging through the entire game. Primal fights are unbearable to play.
ISP: Verizon Fios
Location: New Jersey
World: Diabolos

Tracing route to Diabolos server.

Tracing route to 199.91.189.38 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 6 ms 7 ms L100.NWRKNJ-VFTTP-91.verizon-gni.net [96.242.79.
1]
3 9 ms 7 ms 7 ms G0-5-5-3.NWRKNJ-LCR-21.verizon-gni.net [130.81.1
84.94]
4 8 ms 6 ms 7 ms 130.81.199.14
5 11 ms 11 ms 12 ms 0.xe-3-0-1.BR1.NYC1.ALTER.NET [152.63.5.149]
6 * 12 ms 14 ms ae11.edge2.NewYork.Level3.net [4.68.62.41]
7 21 ms 19 ms 23 ms vlan52.ebr2.NewYork2.Level3.net [4.69.138.254]
8 21 ms 22 ms 21 ms ae-45-45.ebr2.NewYork1.Level3.net [4.69.141.21]

9 15 ms 17 ms 16 ms ae-5-5.car1.Montreal2.Level3.net [4.69.141.5]
10 20 ms 19 ms * ae-11-11.car2.Montreal2.Level3.net [4.69.141.1]

11 19 ms 20 ms 19 ms ORMUCO-COMM.car2.Montreal2.Level3.net [4.59.178.
74]
12 41 ms 41 ms 42 ms 192.34.76.10
13 41 ms 41 ms 42 ms 199.91.189.242
14 33 ms 32 ms 31 ms 199.91.189.38

Trace complete.

[Solarak]

Hello. I've been having the same problems, it only started today December 25th. Last night (Dec.24th) I played just fine. However this afternoon i've been having constant freezing and 3-4 seconds of speeding up to catch up.

My ISP is Verizon FIOS, in New York.