Unless you fully understand what we have been talking about theres not really a way I can help you explain the problem to them. Their tier 1 techs who answer the phones just like any ISP are just any random joe schmo and in most cases have no clue about networking(not to say ALL of them are that way just the majority)
I could ask them for a ticket number next time I talk to them and ask if other fios users can file a complaint on the same issue in hopes of having it escalated to the highest techs.
On the plus side, Verizon called me back and their network engineers have agreed to review my ticket and are currently investigating the latency issues with those routers. I'll update here again when I have more information
wanted to give you guys something I came across. Another post on here talks about utilizing a proxy to get around the latency issues. I did try this and have confirmed my 150 ping is now 20 on VA and it has never been this smooth before. You can try it if you want they give a 30 day free trial and it was posted somewhere else on here previously.
I use the VA DC1 and installed qlprism to have the entire application going over the proxy. It does not actually hide your IP address, but it does fix the latency at least until Verizon does
Alright cool..looking forward to your udpates
I have used wtfast..it does help on TX but not much on other servers..and it doesn't even lower my ping all the times..it's all random..lol
For what it's worth, I have the same problem (although sometimes my ping drops to a usable 40ms), with the exact same router.
1 <1 ms <1 ms <1 ms DMZ.Home [192.168.1.1]
2 3 ms 2 ms 1 ms L100.NWRKNJ-VFTTP-159.verizon-gni.net [22.214.171.124]
3 3 ms 3 ms 4 ms G0-6-2-2.NWRKNJ-LCR-22.verizon-gni.net [126.96.36.199]
4 3 ms 5 ms 3 ms so-6-1-0-0.NWRK-BB-RTR2.verizon-gni.net [188.8.131.52]
5 6 ms 6 ms 6 ms 184.108.40.206
6 24 ms 32 ms 53 ms 0.so-4-0-1.XT2.NYC4.ALTER.NET [220.127.116.11]
7 5 ms 8 ms 6 ms TenGigE0-4-2-0.GW8.NYC4.ALTER.NET [18.104.22.168]
8 102 ms 102 ms 101 ms tinet-gw.customer.alter.net [22.214.171.124]
9 110 ms 143 ms 111 ms xe-2-1-2.was14.ip4.tinet.net [126.96.36.199]
10 113 ms 115 ms 113 ms peer1-gw.ip4.tinet.net [188.8.131.52]
11 110 ms 109 ms 110 ms 10ge-xe-1-0-1.wdc-sp225-sbdis-1.peer1.net [184.108.40.206]
12 110 ms 108 ms 108 ms . [220.127.116.11]
I really hope verizon does something to fix it - my ping used to be 15 to VA, now it's barely playable.
You are correct about the latency issue to alter.net _zoom. Thanks for finding this. Calling Verizon to let them know about the problem.
I mean I definitely urge any of you to call Verizon and complain. The problem is I spent hours on the phone with them explaining this issue over and over and over. I had to demand a supervisors assistance because all they offered to do was send someone out for "slow throughput". I had a 20 minute argument with a t1 tech that slow throughput and latency are not the same. Slow throughput could be caused by latency blah blah blah.
Anyways, I am still waiting to hear back from them but feel free to call in and give them my ticket number which is RIEH0511LY
Explain to them you are another concerned customer that is experiencing the same issues that I am and that I gave you my ticket number to reference and help push this along.
obviously you would want to make sure my ticket references latency with alter.net etc - who knows if they gave me the wrong ticket number
Last edited by _zoom; 01-17-2013 at 12:20 PM.
Originally Posted by chernobyl
Why did i put my ping test? Lemme put my tracert, so I can show i have the same problem.
Tracing route to . [18.104.22.168]
over a maximum of 30 hops:
1 1 ms 4 ms <1 ms 192.168.0.1
2 1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
3 5 ms 5 ms 5 ms L100.NYCMNY-VFTTP-200.verizon-gni.net [108.6.48.
4 7 ms 11 ms 7 ms G0-3-3-4.NYCMNY-LCR-22.verizon-gni.net [130.81.1
5 9 ms 9 ms 8 ms so-5-0-0-0.NY5030-BB-RTR1.verizon-gni.net [130.8
6 8 ms 9 ms 9 ms 0.xe-6-1-1.XT1.NYC4.ALTER.NET [22.214.171.124]
7 13 ms 10 ms 10 ms TenGigE0-4-0-0.GW8.NYC4.ALTER.NET [126.96.36.199]
8 99 ms 96 ms 96 ms tinet-gw.customer.alter.net [188.8.131.52]
9 138 ms 141 ms 119 ms xe-0-1-0.was14.ip4.tinet.net [184.108.40.206]
10 132 ms 132 ms 132 ms peer1-gw.ip4.tinet.net [220.127.116.11]
11 129 ms 129 ms 128 ms 10ge-xe-1-0-1.wdc-sp225-sbdis-1.peer1.net [216.1
12 123 ms 125 ms 128 ms . [18.104.22.168]
What I find interesting is that right after alter.net the text starts showing up slower.
They should just bring back NY servers