High Latecy, modem speeds DSL

[suprn3rd]

Our service has been rock solid the last 6 years.  For the last week, especially since last wednesday.  The speeds have been horrible.  We are talking modem speed here.  Packet loss of 15-25%.  Latency of 60ms - 600ms.  That's with only one computer plugged into a westell 6100.

Verizon techs wanted to replace the modem, the dlink 2750b made matters worse.  They are sending a 784.  I'm not convinced that the modem is the problem.  When I would give ping, traceroute, and packet loss stats, they would just ignore them. 

Tranceiver stats:

Transceiver Revision:	7.2.3.0
Vendor ID Code:	4
Line Mode:	G.DMT Mode
Data Path:	Interleaved
Transceiver Information	Downstream Path	Upstream Path
DSL Speed (Kbits/Sec)	3360	864
Margin (dB)	20.0	10.0
Line Attenuation (dB)	23.0	14.0
Transmit Power (dBm)	7.6	11.9

I should also be able to get 7mbps as well, but verizon says no.

Any help/suggestions would be awesome!

[smith6612]

I suspect this is a congestion issue if this only occurs at night. If it occurs at all times and it is not due to something running on your network, then this is entirely on Verizon's end.

For 7.1Mbps, I'd say it's a go. We need to find out from Verizon what gear you're on that makes them say yes or no.

Keep pestering Verizon for help, and indicate that this isn't a modem problem. Those 6100s were some of the best modems Verizon every handed out, especially if you have the old C90-6100. Those things were built well and last forever. If you have any trouble with Verizon let me know and I'll see if I can get you to someone who can help.

[suprn3rd]

Smith6612, Thank you for the reply. It's completely sporadic and it's definitely not on my end. Got the new router last night (the second one) and like I thought service was worse than before. So I reverted back to the good old 6100. Some things I've noticed. Traffic that gets routed over level3 to the west coast has high latency and sometimes the first hop latency to Verizon routers is unusually high for only some traffic. It also seems like when more than one machine is browsing on my home network the latency goes through the roof, when before it would handle the traffic no problem. All speeds tests show the bandwidth is approximately what it should be, but the latency is bringing things to a halt. I've spoken to some others in the area and some, not all, are experiencing the same issue. And for everyone that is having the issue it started at the same time as the problems I'm having. It began after a hard rain and heavy wind in the area. So I'm thinking there is an issue with the gear at a distribution point somewhere. Do you have any suggestions how I can bypass the outsourced support and speak with an engineer that is closer to the problem and can look at congestion, utilization, hardware, and local lines on the Verizon side. (my home lines are OK) I refuse to spend 3 hours on the phone with entry level support telling me it's my computer that's the problem. THANKS!

[suprn3rd]

Well Verizon tier 2 support was supposed to call Friday night......no call. No call over the weekend or yesterday. I guess I'll have to call in or chat yet again. Very frustrated in trying to get this issue fixed now for over two weeks. Getting someone to listen to stats and where the problem might be has been impossible. As well as getting an answer to the 7mbps service, since my stats suggest that I possibly could. Can't even get my service switched to fast path......frustrating.

[teammandb]

I'd be interested if you get a response to this.  I have been having the same issues and was supposed to get a phone call tonight (10/28) from tier 2, but no phone call.  Back on chat, but I'm sure I'm going to have to call at this point. 

I have absolutely terrible pings and download speeds for many places.  Netflix is completley unwatchable, I can't login to, less yet play any internet games, and my mail program continuously disconnects from the mail servers.  I am getting ping times to places that routinely were in the 100 ms range and are now well over a second.  I've done every single troubleshooting thing they list and more.  

Example traceroute:

traceroute to cyclingnews.com (89.167.142.15), 64 hops max, 52 byte packets
 1  verizon (192.168.1.1)  0.997 ms  0.547 ms  0.581 ms
 2  10.30.8.1 (10.30.8.1)  1188.390 ms  1372.710 ms  1185.809 ms
 3  p1-2.ronkva-lcr-02.verizon-gni.net (130.81.193.166)  1195.445 ms  1262.539 ms  1318.383 ms
 4  xe-1-0-2-0.res-bb-rtr2.verizon-gni.net (130.81.199.48)  1337.661 ms  1349.616 ms  1447.429 ms
 5  * * *
 6  * * *
 7  0.ae4.xt2.dca5.alter.net (140.222.225.207)  918.417 ms  1000.142 ms  900.246 ms
 8  0.xe-9-0-0.xl2.iad8.alter.net (152.63.7.66)  599.221 ms  512.433 ms  365.396 ms
 9  0.xe-9-2-0.gw9.iad8.alter.net (152.63.36.30)  401.746 ms
    0.xe-11-2-0.gw9.iad8.alter.net (152.63.41.254)  471.470 ms
    0.xe-11-3-1.gw9.iad8.alter.net (152.63.42.10)  561.761 ms
10  tinet-gw.customer.alter.net (152.179.50.30)  629.297 ms  737.557 ms  804.091 ms
11  xe-1-2-3.lon11.ip4.gtt.net (141.136.106.153)  878.889 ms
    xe-0-0-0.lon11.ip4.gtt.net (89.149.180.46)  1006.477 ms  1110.339 ms
12  future-publishing-gw.ip4.gtt.net (141.136.103.6)  1218.672 ms  1278.691 ms  1250.760 ms
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *

At this point I just gave up and stopped waiting for it to reach the server.   It eventually reaches max number of hops and never gets there.