First, I'd like to say that I am a resident of Buffalo, NY. Prior to the new MI424WR-GEN3I firmware, 40.20.7, online gaming, specifically Black Ops 2, was unbearable. Now, with the new firmware, there is a noticeable difference in the connection. However, the latency for gaming in general is still incredibly sluggish and I constantly find myself looking like I have the reaction time of a snail and barely get off 2-3 shots in the killcams - this is especially frustrating when I could've sworn I emptied half my clip into that very same person. This issue is not "once in a blue moon". It is literally plagueing my online gaming experience and FPS games are near impossible to play. Customer service never has any answers, and I'm constantly told to just reset my router and the problem should be fixed.
I've been sent a new router twice, I've changed out the coax cables that were poor quality, and I have even tried to run a 3rd party router on a LAN-LAN with the Actiontec (I would use my own, but I subscribe to FiOS TV). Part of me wants to blame the high latency on the coax lines and FiOS TV, but a friend of mine has the exact same plan in NYC and has never seen a ping above 3ms. This surprised me, since I can't speedtest below 30ms ping... ever.
Any ideas on why I struggle with the ping on FiOS? I know a lot of you might not think 30-60ms ping is a lot, but I've played on connections that have near 0 pings and the connection was absolutely stunning. In no way am I trying to complain about it, if there isn't a way to "fix" it, then I'll have to make do with it and throw out FPS games, but if any help can be provided, it'd be greatly appreciated.
Speedtest, pingtest, and tracerts are below:
Toronto:
http://www.pingtest.net/result/84380146.png
http://www.pingtest.net/result/84380625.png
http://www.speedtest.net/result/2868907331.png
Buffalo:
http://www.speedtest.net/result/2868909311.png
NY:
http://www.pingtest.net/result/84380656.png
http://www.speedtest.net/result/2868910699.png
Tracerts:
Tracing route to b.resolvers.Level3.net [4.2.2.2]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 5 ms 5 ms L100.BFLONY-VFTTP-17.verizon-gni.net [108.17.5.1]
3 10 ms 10 ms 7 ms G0-1-1-6.BFLONY-LCR-21.verizon-gni.net [130.81.97.246]
4 80 ms 29 ms 19 ms xe-1-1-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.34]
5 20 ms 21 ms 20 ms 0.xe-10-1-0.BR1.NYC1.ALTER.NET [152.63.18.225]
6 22 ms 20 ms 20 ms ae11.edge2.NewYork.Level3.net [4.68.62.41]
7 21 ms 21 ms 21 ms vlan51.ebr1.NewYork2.Level3.net [4.69.138.222]
8 22 ms 35 ms 20 ms ae-4-4.ebr1.NewYork1.Level3.net [4.69.141.17]
9 23 ms 31 ms 22 ms ae-61-61.csw1.NewYork1.Level3.net [4.69.134.66]
10 21 ms 21 ms 20 ms ae-1-60.edge2.NewYork1.Level3.net [4.69.155.16]
11 22 ms 21 ms 21 ms b.resolvers.Level3.net [4.2.2.2]
Trace complete.
C:\Users\The Kurtis>tracert 8.8.8.8
Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 4 ms 4 ms L100.BFLONY-VFTTP-17.verizon-gni.net [108.17.5.1]
3 8 ms 7 ms 7 ms G0-1-1-6.BFLONY-LCR-21.verizon-gni.net [130.81.97.246]
4 16 ms 17 ms 22 ms xe-4-1-6-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.8]
5 20 ms 22 ms 20 ms 0.so-0-0-0.XT1.NYC4.ALTER.NET [152.63.1.41]
6 22 ms 22 ms 23 ms TenGigE0-4-0-0.GW8.NYC4.ALTER.NET [152.63.21.61]
7 20 ms 21 ms 20 ms Internet-gw.customer.alter.net [152.179.72.66]
8 19 ms 54 ms 23 ms 72.14.238.232
9 20 ms 19 ms 20 ms 72.14.236.206
10 26 ms 26 ms 26 ms 209.85.249.11
11 36 ms 35 ms 33 ms 72.14.235.10
12 33 ms 32 ms 33 ms 72.14.234.55
13 * * * Request timed out.
14 35 ms 33 ms 34 ms google-public-dns-a.google.com [8.8.8.8]
Trace complete.