I have now placed 4 calls into support (last 2 being updates on my ticket)
I am not very happy right now as my ticket was 'closed' due to missing 1 call from a tier 1 tech asking if I was still having trouble. However, he indicated (while i was on the phone for 30 minutes) that he spoke with a tier 2 tech and they have from what he says recognized this as a widescale issue and they are working on it. He also let me know that I would receive a call back in the next 24 hours.
I basically purchased a 1 month proxy to redirect my traffic to induce some different routing which will hold me over for now. This is obviously not reasonable as I already pay a decent premium for my Verizon service. I have faith in their network engineers to resolve the issue, but I have already been having this issue for a month =\
01-21-2013 03:40 PM - edited 01-21-2013 03:40 PM
What proxy service did you select? I am also considering doing that. I very much appreciate that you keep posting here chzoom, your dedication to the phone is admirable, I'm not sure I have the patience for that.
I only have patience because I do this for a living myself. I know they can't just snap their fingers and fix it, especially if its a bandwidth or throughput issue with a core circuit or equipment.
If you want to private message me I can give you the service I use right now which works perfect(not exactly sure on the TOS of the boards, probably not a good idea to post the link for public view 🙂 )
01-21-2013 06:07 PM - edited 01-21-2013 06:09 PM
Having the same issue as well for the last month now, about a week before Christmas. Makes online gaming to and thru DC/Virginia almost unplayable. I got so fed up I also looked into a tunneling/ proxy service. I got a month's subscription which I hope I don't need to continue to use. Sometimes the spike on hop 8 goes to 175+ Thanks for the posts.
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 5 ms 5 ms L100.BLTMMD-VFTTP-61.verizon-gni.net [220.127.116.11]
3 4 ms 4 ms 4 ms G11-0-5-461.BLTMMD-LCR-04.verizon-gni.net [18.104.22.168]
4 8 ms 8 ms 8 ms so-6-0-3-0.PHIL-BB-RTR2.verizon-gni.net [22.214.171.124]
5 12 ms 11 ms 12 ms xe-9-1-4-0.NY5030-BB-RTR2.verizon-gni.net [126.96.36.199]
6 12 ms 12 ms 13 ms 0.so-0-0-0.XT2.NYC4.ALTER.NET [188.8.131.52]
7 12 ms 16 ms 15 ms TenGigE0-7-0-0.GW8.NYC4.ALTER.NET [184.108.40.206]
8 92 ms 124 ms 90 ms tinet-gw.customer.alter.net [220.127.116.11]
9 96 ms 95 ms 96 ms xe-1-3-1.was14.ip4.tinet.net [18.104.22.168]
10 105 ms 105 ms 104 ms peer1-gw.ip4.tinet.net [22.214.171.124]
11 102 ms 99 ms 95 ms 10ge-xe-1-0-1.wdc-sp225-sbdis-1.peer1.net [126.96.36.199]
12 107 ms 97 ms 94 ms wgn53.wolfservers.com [188.8.131.52]
01-21-2013 06:56 PM - edited 01-21-2013 06:58 PM
well I got a call from a supervisor - Long story short they claim the router isn't owned by Verizon and can provide me no additional assistance. As much as I hate to, I now need to find a way out of my contract because I can't continue to figure out ways around their issue. This is a wide scale issue that more than just myself or a couple people are experiencing 😐
I attempted to speak with technical support over the online chat earlier, but that was unproductive. After explaining my issue this was the response I recieved:
"I am running a test on the line and is coming good. Your issues is beyond our support
I apologize but we do not provide support for this issue. In an effort to educate you on what is supported, please visit http://support.verizon.com/boundary to see what support options are available. Links to the available support options are provided alongside the type of issue making it easy to use this resource.
However, we do have a group that can help with both hardware and software upgrades and issues. For any assistance with your personal equipment you can sign up for our Expert Care http://surround.verizon.net/Shop/Expertcare/default.aspx or contact your computer/device manufacturer. To add this feature by phone, please call Sales at 1-800-VERIZON (1-800-837-4966) and they will be able to add this feature to your account."
Of course I balked at being told that I would need an additional -paid- service to even talk to someone about the issue, so I asked for a supervisor. His response was
" She explained to me your issue and unfortunately that is out of our scope, here at the Technical Support Department. Indeed, we do have the PREMIUM TECH Support that handles this type of issues. Please give them a call they have a one time free assistance for this matter."
I doubt its worth my time to call and use my "one time free assistance" after you've done all this leg work.
01-23-2013 01:00 PM - edited 01-23-2013 01:08 PM
I just wanted to bump this with my own new latency issue.
In the NJ area, on FiOS and have had a recent jump.
My specific test case is a game called Mechwarrior Online. The game servers are located in eastern Canada.
Average ping for the past 6 months has been steady between 40-60ms.
Now average ping is consistenly 120-130. This is within the week around Christmas as many other reported.
This was tested with two machines inside the home one via WiFi one via CAT6.
Happy to conduct and post tracert's but It seems that further verifying the issue is not whats needed at this point.
if anyone wants me run one to a specific server as another datapoint let me know.
Thanks, and happy to be of assistance to this cause.
Unfortunately I doubt we are going to get any further help with the issue since of course this is a community driven board. Getting Verizon to recognize the issue and try and assist their customers is like pulling teeth. I explained the issue to probably 5+ different people and spent countless hours on the phone to be called and given a 15 second answer that basically told me to pound sand 🙂
I assume one day it will just magically go away and start working as it used to around xmas time.
While you're probably right I figured i'd toss up one trace, just for the heck of it.
Look familiar? 🙂
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 6 ms 14 ms L100.NWRKNJ-VFTTP-94.verizon-gni.net [98.109.1291] 3 11 ms 12 ms 13 ms 184.108.40.206
4 10 ms 9 ms 9 ms ae0-0.NWRK-BB-RTR2.verizon-gni.net [220.127.116.11] 5 10 ms 9 ms 12 ms xe-6-1-1-0.NY325-BB-RTR2.verizon-gni.net [130.8123.230] 6 12 ms 12 ms 11 ms 0.so-4-0-0.XT2.NYC4.ALTER.NET [18.104.22.168]
7 15 ms 16 ms 13 ms TenGigE0-7-2-0.GW8.NYC4.ALTER.NET [22.214.171.124 8 106 ms 108 ms 109 ms tinet-gw.customer.alter.net [126.96.36.199]
9 164 ms 131 ms 127 ms xe-4-3-0.tor10.ip4.tinet.net [188.8.131.52]
10 146 ms 142 ms 136 ms internap-gw.ip4.tinet.net [184.108.40.206]
11 137 ms 136 ms 142 ms border1.te9-1-bbnet2.tor001.pnap.net [220.127.116.11] 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out.