I bought 25/25 FiOS back in Feburary. It was running well for two weeks until the connection had suffered high latency. I called Tech Support numerous times. Some have told me that they blame the ONT and some for the router. I have a replacement router but that has not solved the issue at all. In fact, it made the download and upload speed much lower than the given service. (Verizon Speed Test even reported 4.5 Down/ 41.5 Up). The router that I have is Rev. I, and the replacement router is Rev. F. I am going to send back the replacement router. Should I call up a technician to my house?
@You might want to post traceroutes so we can take a look, also do a speedtest @ http://speedtest.verizon.net and then cut and paste the results PLUS the analysis. same page you will see a small link for analysis
@Vigz wrote:I bought 25/25 FiOS back in Feburary. It was running well for two weeks until the connection had suffered high latency. I called Tech Support numerous times. Some have told me that they blame the ONT and some for the router. I have a replacement router but that has not solved the issue at all. In fact, it made the download and upload speed much lower than the given service. (Verizon Speed Test even reported 4.5 Down/ 41.5 Up). The router that I have is Rev. I, and the replacement router is Rev. F. I am going to send back the replacement router. Should I call up a technician to my house?
I do not have the replacement router since I already sent it out. This the log for the Rev. I router. One tech agent said that the technicians had seen high packet loss as well as high latency.
Analysis information: Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done SendBufferSize set to [261360] running 10s outbound test (client to server) . . . . . 25.03Mb/s running 10s inbound test (server to client) . . . . . . 21.68Mb/s ------ Client System Details ------ OS data: Name = Windows 7, Architecture = x86, Version = 6.1 Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_31 ------ Web100 Detailed Analysis ------ Client Receive Window detected at 495104 bytes. 45 Mbps T3/DS3 link found. Link set to Half Duplex mode Information: throughput is limited by other network traffic. Good network cable(s) found Normal duplex operation found. Web100 reports the Round trip time = 29.53 msec; the Packet size = 1452 Bytes; and There were 240 packets retransmitted, 1340 duplicate acks received, and 1500 SACK blocks received The connection stalled 1 times due to packet loss The connection was idle 0.24 seconds (2.18%) of the time This connection is receiver limited 5.11% of the time. This connection is sender limited 55.58% of the time. This connection is network limited 39.30% of the time. Web100 reports TCP negotiated the optional Performance Settings to: RFC 2018 Selective Acknowledgment: ON RFC 896 Nagle Algorithm: ON RFC 3168 Explicit Congestion Notification: OFF RFC 1323 Time Stamping: OFF RFC 1323 Window Scaling: ON Information: Network Middlebox is modifying MSS variable Server IP addresses are preserved End-to-End Information: Network Address Translation (NAT) box is modifying the Client's IP address
Speed Test for the North East region
We have finished your connection speed test for NY - New York.
Where shall I run tracerts to?
Why is the NDT test saying you're running a Half Duplex connection? That may very well be your issue if that's the case with latency. Check your computer's NIC to ensure it is on Auto Detect mode, and not something such as 100Mbps Full Duplex or 100Mbps Half Duplex. On many adapters forcing the mode to 100Mbps Full Duplex will cause the adapter to actually use half duplex instead. Gigabit NICs should only be able to be set to Full Duplex and should use that mode as such.
just from experience, I wouldn't trust vz tech support to talk intelligently about latency. a handful of their agents might be able to, on whole though, I would take it with a grain of salt.
If you can post a traceroute to yahoo.com that would also be helpful and it would clearly show any latency if there was any and also where the latency was.
start > run > type cmd and hit enter
then type tracert www.yahoo.com
also try to get the verizon analysis posted here too,
http://speedtest.verizon.net and then cut and paste the results PLUS the analysis.
Thanks, but unfortunately channels 6 and 11 did not change the latency. If I go to PingTest.net the ping will spike up to about 40ms ping 32ms jitter and it will slowly bring itself down to 14ms with 3ms jitter. Even though it goes back to normal, the lag spike shows up in applications like Xbox Live, PSN, and Skype. The technician is saying that the old coax splitters are the problem. So, he is going to use the Ethernet WAN connection instead of Coax which is going to be an exception since buisnesses only use the ethernet for heavy download and upload speeds.
Oh, btw. Congrats on your MVP status!
thanks, and definetely come back and let us know if the tech was able to fix it 🙂
He said he would talk to his boss to see if he can do it. He probably might do it next week.
Was this issue ever resolved? I am having this problem with a website I design for. I spoke to the tech at verizon who told me that there was nothing they could do because the speed test came back fine. Wouldn't listen to me about how my pings were 90 ms and higher. Didn't even care that my 3g connection was faster then their service. I am not a network wiz so I'm not 100% sure where the issue is in the traceroute. Any help would be appreciated.
traceroute results
traceroute to awesome-con.com (69.195.106.242), 64 hops max, 52 byte packets
1 wireless_broadband_router (192.168.1.1) 0.788 ms 0.452 ms 0.491 ms
2 l100.bltmmd-vfttp-35.verizon-gni.net (96.244.133.1) 7.822 ms 6.653 ms 7.095 ms
3 g0-2-4-0.bltmmd-lcr-21.verizon-gni.net (100.41.205.12) 12.970 ms 9.367 ms 12.751 ms
4 ae20-0.res-bb-rtr1.verizon-gni.net (130.81.151.112) 70.260 ms
so-1-1-0-0.res-bb-rtr1.verizon-gni.net (130.81.199.2) 12.681 ms 12.607 ms
5 0.xe-5-1-0.br1.iad8.alter.net (152.63.37.69) 11.565 ms 11.926 ms
0.xe-5-3-0.br1.iad8.alter.net (152.63.37.49) 12.543 ms
6 te0-3-0-14.ccr41.iad02.atlas.cogentco.com (154.54.13.137) 24.573 ms 24.286 ms
te0-6-0-14.ccr41.iad02.atlas.cogentco.com (154.54.10.225) 25.646 ms
7 be2177.ccr22.dca01.atlas.cogentco.com (154.54.41.206) 24.543 ms
be2112.mpd22.dca01.atlas.cogentco.com (154.54.5.234) 25.211 ms
be2113.mpd21.dca01.atlas.cogentco.com (154.54.6.170) 25.013 ms
8 be2154.ccr41.ord01.atlas.cogentco.com (154.54.30.198) 36.698 ms
be2155.ccr42.ord01.atlas.cogentco.com (154.54.31.78) 36.546 ms
be2153.ccr42.ord01.atlas.cogentco.com (154.54.30.126) 36.898 ms
9 be2156.ccr21.mci01.atlas.cogentco.com (154.54.6.85) 49.209 ms 50.040 ms
be2157.ccr22.mci01.atlas.cogentco.com (154.54.6.117) 50.048 ms
10 be2130.ccr22.den01.atlas.cogentco.com (154.54.26.121) 62.388 ms
be2128.ccr21.den01.atlas.cogentco.com (154.54.25.173) 61.602 ms
be2130.ccr22.den01.atlas.cogentco.com (154.54.26.121) 62.288 ms
11 be2126.ccr21.slc01.atlas.cogentco.com (154.54.25.66) 84.277 ms 84.673 ms
be2127.ccr21.slc01.atlas.cogentco.com (154.54.25.70) 90.402 ms
12 38.104.174.198 (38.104.174.198) 81.408 ms 82.181 ms 94.622 ms
13 rtr-a.unifiedlayer.com (199.58.199.114) 84.858 ms * 81.487 ms
14 69-195-106-242.unifiedlayer.com (69.195.106.242) 89.278 ms 89.954 ms 90.370 ms
I am not sure what happened with the original poster, but looking at your traceroutes, you're going from MD to Denver? if that's true than the 90ms, might not be all that bad, or at least not amazingly bad.
The first set of hops that I put in bold are the hops that Verizon is responsible for, meaning they own it and maintain it.
The red ones are a company called Cogent, who not surprisingly is the leading problem company that is causing a lot of the Netflix issues that you may or may not be hearing about.
You're problem occurs really in the green, right when your traffic gets into Denver Proper. And then it progressively gets worse. 90 is not terribly high though. It's a smidge high, but not as bad as it could be.
Are you wireless, can you try it while you are wired into the router for a test. You really want to make sure that it's not just a wireless problem, 90 ms round trip from MD to Denver shouldn't be too noticeable unless you have other problems on top of it.
@Boogalah wrote:Was this issue ever resolved? I am having this problem with a website I design for. I spoke to the tech at verizon who told me that there was nothing they could do because the speed test came back fine. Wouldn't listen to me about how my pings were 90 ms and higher. Didn't even care that my 3g connection was faster then their service. I am not a network wiz so I'm not 100% sure where the issue is in the traceroute. Any help would be appreciated.
traceroute results
traceroute to awesome-con.com (69.195.106.242), 64 hops max, 52 byte packets
1 wireless_broadband_router (192.168.1.1) 0.788 ms 0.452 ms 0.491 ms
2 l100.bltmmd-vfttp-35.verizon-gni.net (96.244.133.1) 7.822 ms 6.653 ms 7.095 ms
3 g0-2-4-0.bltmmd-lcr-21.verizon-gni.net (100.41.205.12) 12.970 ms 9.367 ms 12.751 ms
4 ae20-0.res-bb-rtr1.verizon-gni.net (130.81.151.112) 70.260 ms
so-1-1-0-0.res-bb-rtr1.verizon-gni.net (130.81.199.2) 12.681 ms 12.607 ms
5 0.xe-5-1-0.br1.iad8.alter.net (152.63.37.69) 11.565 ms 11.926 ms
0.xe-5-3-0.br1.iad8.alter.net (152.63.37.49) 12.543 ms
6 te0-3-0-14.ccr41.iad02.atlas.cogentco.com (154.54.13.137) 24.573 ms 24.286 ms
te0-6-0-14.ccr41.iad02.atlas.cogentco.com (154.54.10.225) 25.646 ms
7 be2177.ccr22.dca01.atlas.cogentco.com (154.54.41.206) 24.543 ms
be2112.mpd22.dca01.atlas.cogentco.com (154.54.5.234) 25.211 ms
be2113.mpd21.dca01.atlas.cogentco.com (154.54.6.170) 25.013 ms
8 be2154.ccr41.ord01.atlas.cogentco.com (154.54.30.198) 36.698 ms
be2155.ccr42.ord01.atlas.cogentco.com (154.54.31.78) 36.546 ms
be2153.ccr42.ord01.atlas.cogentco.com (154.54.30.126) 36.898 ms
9 be2156.ccr21.mci01.atlas.cogentco.com (154.54.6.85) 49.209 ms 50.040 ms
be2157.ccr22.mci01.atlas.cogentco.com (154.54.6.117) 50.048 ms
10 be2130.ccr22.den01.atlas.cogentco.com (154.54.26.121) 62.388 ms
be2128.ccr21.den01.atlas.cogentco.com (154.54.25.173) 61.602 ms
be2130.ccr22.den01.atlas.cogentco.com (154.54.26.121) 62.288 ms
11 be2126.ccr21.slc01.atlas.cogentco.com (154.54.25.66) 84.277 ms 84.673 ms
be2127.ccr21.slc01.atlas.cogentco.com (154.54.25.70) 90.402 ms
12 38.104.174.198 (38.104.174.198) 81.408 ms 82.181 ms 94.622 ms
13 rtr-a.unifiedlayer.com (199.58.199.114) 84.858 ms * 81.487 ms
14 69-195-106-242.unifiedlayer.com (69.195.106.242) 89.278 ms 89.954 ms 90.370 ms
Start a new topic or ask questions in the open forum.
