- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The only problem is this is not an issue of home equipment nor would sending a tech out do anything. It is clearly an issue of verizon's backbone being overtaxed during peak hours as seen in the traceroutes.
This issue is happening all over the U.S. - in NJ, NY, CA, there are multiple posts about it on dslreports forums and every single person with this issue has traced it to over subscribed backbone verizon uses. Traceroutes show extremely high latency and timeouts.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm still having this issue. I called tech support and all they attempted to do was switch the channel I was on at the central office. While this did improve my ping slightly, I still am not back to where I was 3 weeks ago. Sometime around Jan 15th my pings more than doubled and never recovered. Time of day has no effect on this issue either. I went from pings between 60-80ms to 160-220ms. Now after calling tech support I'm seeing 130-150ms, however the server I'm connecting to is in Toronto and I live in Massachusetts.
As a comparison I've run a tracert to the same server from my work computer which is less than a mile from my house. Here is the results:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Bryan>tracert 70.42.29.65
Tracing route to 70.42.29.65 over a maximum of 30 hops
1 1 ms 1 ms 1 ms static-72-248-212-9.ct.onecommunications.net [72.248.212.9]
2 9 ms 9 ms 9 ms lo0.wrcsma05-gsr-03.onecommunications.net [64.69.99.131]
3 12 ms 11 ms 12 ms ge-0-1-0-5.wrcmankgs04.onecommunications.net [64.69.98.50]
4 149 ms 150 ms 16 ms te-3-1.nycnyzrr101.onecommunications.net [64.69.99.238]
5 16 ms 16 ms 16 ms 165.121.238.178
6 16 ms 16 ms 22 ms ge-5-0-1.ar5.jfk1.gblx.net [64.214.141.253]
7 30 ms 30 ms 39 ms te8-1-10G.asr1.YYZ1.gblx.net [67.16.131.186]
8 29 ms 29 ms 29 ms 64.210.12.62
9 29 ms 30 ms 30 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.196]
10 32 ms 31 ms 33 ms 70.42.29.65
Trace complete.
I'm pretty sure the service at work is Earthlink and I can ping the same server in Toronto at 30ms??? Verizon really needs to take a look at "tinet-gw.customer.alter.net" as this is where the horrific latency starts. I'll post a tracert from my home pc later today. Please fix this Verizon!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Also having major ping issues since mid-January. The primary game I play has seen pings more than double from its normal 72ms to 180-200ms.
It returns to normal, slowly, after 10pm EST. All other hours has this ping issue, and many others have had this issue, with the same node. for example, my tracert:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\> tracert www.mwomercs.com
Tracing route to www.mwomercs.com [70.42.29.74]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter.westell.com [192.168.1.1]
2 40 ms 40 ms 41 ms 10.29.29.1
3 42 ms 42 ms 41 ms P15-1.SCTNPA-LCR-01.verizon-gni.net [130.81.197.
64]
4 46 ms 46 ms 46 ms xe-4-1-8-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
209.194]
5 86 ms 56 ms 56 ms xe-1-0-2-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.23.184]
6 59 ms 60 ms 59 ms 0.so-7-0-0.XT1.NYC4.ALTER.NET [152.63.17.89]
7 60 ms 59 ms 63 ms TenGigE0-7-2-0.GW8.NYC4.ALTER.NET [152.63.21.129
]
8 151 ms 152 ms 152 ms tinet-gw.customer.alter.net [152.179.72.122]
9 186 ms 185 ms 178 ms xe-4-3-0.tor10.ip4.tinet.net [89.149.184.110]
10 181 ms 185 ms 187 ms internap-gw.ip4.tinet.net [77.67.70.94]
11 217 ms 209 ms 205 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.1
96]
Look at the jump from 7 to 8. Just look at it. That tinet-gw.customer.alter.net is really horrendous and the pingsj ust get worse from there. This is the same node everyone's been complaining about, and alter.net is Verizon's backbone. Why is this happening, and is there anything we can do?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm in the Dallas/FW, TX area and having similar issues. Tracerts with loss starting 3-4 hops out, high ping times...extremely frustrating. Also started around mid-january.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm sure a lot of us who are experiencing this problem are frustrated. Verizon FiOS at its best in 2013 with high latency issues at all times while we pay in full monthly with no compensations.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm in Trenton, NJ. Also playing MWO and I'm also having the same problem! I've contacted Verizon more than a dozen times on it and I keep getting tech support in India which is worthless.
Thier response to me on this is that after 5 hops on the traceroute it is out of their network and can't help us. I think we all know this is bull. I hate to say it but I'm ready to switch internet providers after being with verizon/ATT/Bell Atlantic for 16 years. If they can't provide us the service and support we are paying for, they don't deserve my money.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It has been over two weeks since this problem has arised and there has been no feedback from the department that should be handling this. Bit ridiculous if you ask me.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@clampdown26 wrote:Also having major ping issues since mid-January. The primary game I play has seen pings more than double from its normal 72ms to 180-200ms.
It returns to normal, slowly, after 10pm EST. All other hours has this ping issue, and many others have had this issue, with the same node. for example, my tracert:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\> tracert www.mwomercs.com
Tracing route to www.mwomercs.com [70.42.29.74]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dslrouter.westell.com [192.168.1.1]
2 40 ms 40 ms 41 ms 10.29.29.1
3 42 ms 42 ms 41 ms P15-1.SCTNPA-LCR-01.verizon-gni.net [130.81.197.
64]
4 46 ms 46 ms 46 ms xe-4-1-8-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
209.194]
5 86 ms 56 ms 56 ms xe-1-0-2-0.NY5030-BB-RTR1.verizon-gni.net [130.8
1.23.184]
6 59 ms 60 ms 59 ms 0.so-7-0-0.XT1.NYC4.ALTER.NET [152.63.17.89]
7 60 ms 59 ms 63 ms TenGigE0-7-2-0.GW8.NYC4.ALTER.NET [152.63.21.129
]
8 151 ms 152 ms 152 ms tinet-gw.customer.alter.net [152.179.72.122]
9 186 ms 185 ms 178 ms xe-4-3-0.tor10.ip4.tinet.net [89.149.184.110]
10 181 ms 185 ms 187 ms internap-gw.ip4.tinet.net [77.67.70.94]
11 217 ms 209 ms 205 ms border1.te9-1-bbnet2.tor001.pnap.net [70.42.24.1
96]Look at the jump from 7 to 8. Just look at it. That tinet-gw.customer.alter.net is really horrendous and the pingsj ust get worse from there. This is the same node everyone's been complaining about, and alter.net is Verizon's backbone. Why is this happening, and is there anything we can do?
While you are having the tinet routing issue, as you're on DSL we can also cut down on some of the latency by getting your line moved from Interleaved to FastPath if it is running clean enough. That can get your second hop latency from where you're at now, down to about 15ms to even as low as 6ms.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Any pointers you can give me Smith to making that happen? I talked with one of the agents in chat and they seemed to have no idea what I was talking about!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
5 Pages and not 1 tech response. I love this customer service!