Is this speed normal??

[LesleyH]

I have Verizon DSL in my home (I'd love to get FIOS but it's not available here) and the speeds have always been pretty slow. I chalked it up to my computer not being that great, and didn't worry about it... but I've recently upgraded to a MUCH faster and better computer, and the internet speeds are still dismal. 

Speeds tests have never even hit 1mbs for download...

I have called Verizon about this issue, and all they've ever had me do was double check that I have filters on all the other phone jacks, and reset my modem a bunch of times. 

Am I doomed to these speeds forever? If so, I'm gonna have to go to TWC.

[grm31]

You're likely stuck with the slow speed.  What plan/speed tier are you signed up for?

I'm on the 3 Mbps plan, but normally only see 1-1.5 Mbps.  If I call tech support, they reset the line (or whatever they do), and the speed goes to normal for a day or two.  But eventually, I'm right back down to 1-1.5 Mbps.

Welcome to Verizon "high" speed Internet.

[LesleyH]

I'm also signed up for the 3mbps plan. 

I had heard rumors that Verizon was intentionally screwing with DSL speeds to push more people towards FIOS, which is annoying on it's own, but EXTRA annoying for me, since I can't even get FIOS anyway. I like Verizon customer service, but I can't keep living with these speeds. >.< Is there really nothing I can do about it?

[dslr595148]

Step one: Visit http://www.giganews.com/line_info.html and post up the Traceroute the page shows, if you wish. Be aware that your non-bogan public IP Address will show up.  It might shown up as the final hop (bottom-most line of the trace)  might contain a hop with your IP address in it. Either remove that line or show only the first two octets. What I'm looking for is a line that mentions "ERX" in it's name towards the end. If for some reason the trace does not complete (two lines full of Stars), keep the trace route intact.

For example this what I saw when I was using Verizon

---

news.giganews.com

    traceroute to 71.242.*.* (71.242.*.*), 30 hops max, 60 byte packets
    1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 13 ms 13 ms 13 ms
    2 ash-bb1-link.telia.net (213.248.70.241) 39 ms 7 ms 7 ms
    3 TenGigE0-2-0-0.GW1.IAD8.ALTER.NET (63.125.125.41) 4 ms 4 ms GigabitEthernet2-0-0.GW8.IAD8.ALTER.NET (63.65.76.189) 4 ms
    4 so-7-1-0-0.PHIL-CORE-RTR1.verizon-gni.net (130.81.20.137) 6 ms 6 ms 6 ms
    5 P3-0-0.PHIL-DSL-RTR11.verizon-gni.net (130.81.13.170) 6 ms 6 ms 6 ms
    6 static-71-242-*-*.phlapa.east.verizon.net (71.242.*.*) 32 ms 32 ms 33 ms

---

Step two: Can you provide the Transceiver Statistics from your modem?

#3 If you don't know how to get that info:

a) What is the brand and model of your modem?

b) If you have a RJ-45 WAN port router connected to it: What is the brand and model of the RJ-45 WAN port router?

#4 If you have a RJ-45 WAN port router connected to the modem, even if you know how to get the Transceiver Statistics from the modem: What is the brand and model of the RJ-45 WAN port router?

[LesleyH]

Okay, here's the traceroute info:

news.giganews.com

traceroute to 71.189.89.225 (71.189.89.225), 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 106 ms 106 ms 106 ms
2 ash-bb1-link.telia.net (213.248.70.241) 0 ms 40 ms 40 ms
3 ash-b2-link.se.telia.net (80.91.245.223) 0 ms ash-b2-link.telia.net (80.91.245.107) 0 ms 0 ms
4 TenGigE0-0-0-10.GW1.IAD8.ALTER.NET (152.179.50.233) 3 ms 7 ms 7 ms
5 P1-0-0-0.LSANCA-LCR-21.verizon-gni.net (130.81.xxx.xx) 69 ms 69 ms 69 ms
6 P1-0.LSANCA-DSL-48.verizon-gni.net (130.81.xx.x) 69 ms 70 ms 70 ms
7 * * *
8 * * *
9 * * *
10 * * *
11 * * *
12 * Max number of unresponsive hops reached (firewall or filter?)

news-europe.giganews.com

traceroute to 71.189.89.225 (71.189.89.225), 30 hops max, 60 byte packets
1 vl201.gw1.ams.giganews.com (216.196.110.3) 0 ms 0 ms 0 ms
2 te7-7.ccr01.ams05.atlas.cogentco.com (149.11.104.9) 0 ms te7-8.ccr01.ams05.atlas.cogentco.com (149.11.104.17) 0 ms 0 ms
3 te0-7-0-25.mpd22.ams03.atlas.cogentco.com (154.54.36.214) 0 ms te0-7-0-25.mpd21.ams03.atlas.cogentco.com (130.117.0.85) 1 ms 1 ms
4 multi-use.cogentco.com (154.54.62.145) 8 ms be2183.ccr22.lpl01.atlas.cogentco.com (154.54.58.69) 10 ms be2185.ccr22.lpl01.atlas.cogentco.com (154.54.37.106) 11 ms
5 te0-7-0-10.ccr22.jfk02.atlas.cogentco.com (154.54.80.125) 87 ms te0-7-0-9.ccr22.bos01.atlas.cogentco.com (154.54.85.221) 76 ms te0-5-0-3.ccr22.bos01.atlas.cogentco.com (154.54.44.189) 76 ms
6 be2097.mpd22.jfk02.atlas.cogentco.com (154.54.30.117) 84 ms be2094.ccr21.jfk02.atlas.cogentco.com (154.54.30.13) 82 ms be2097.mpd22.jfk02.atlas.cogentco.com (154.54.30.117) 81 ms
7 be2148.ccr21.dca01.atlas.cogentco.com (154.54.31.117) 91 ms be2151.mpd22.dca01.atlas.cogentco.com (154.54.40.73) 88 ms be2150.mpd21.dca01.atlas.cogentco.com (154.54.31.129) 88 ms
8 uunet.iad01.atlas.cogentco.com (154.54.13.138) 87 ms be2112.ccr41.iad02.atlas.cogentco.com (154.54.5.233) 89 ms uunet.iad01.atlas.cogentco.com (154.54.13.138) 94 ms
9 uunet.iad01.atlas.cogentco.com (154.54.13.138) 91 ms 89 ms B100.LSANCA-LCR-22.verizon-gni.net (130.81.22.247) 167 ms
10 B100.LSANCA-LCR-22.verizon-gni.net (130.81.xx.xxx) 167 ms 167 ms B400.LSANCA-LCR-21.verizon-gni.net (130.81.199.91) 162 ms
11 P1-0.LSANCA-DSL-48.verizon-gni.net (130.81.xx.x) 158 ms P0-0.LSANCA-DSL-48.verizon-gni.net (130.81.44.5) 159 ms *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * Max number of unresponsive hops reached (firewall or filter?)

The Modem is a Westell 7500 and it has a built in router, so there is no separate one. If I knew how to get that other info, I would, sorry. >.<

[smith6612]

This page should give you the statistics we need on a 7500: http://192.168.1.1/htmlV/transtat.asp

Failing that, visit http://192.168.1.1/ and click System Monitoring, Advanced Monitoring, and then Transceiver Statistics.

If you need login information, try:

admin/password

admin/admin

admin/admin1

admin/password1

admin/verizon

admin/verizon1

[LesleyH]

Transceiver Statistics

Transceiver Revision A2pB020b3.d20h Vendor ID Code 4D54 Line Mode ADSL_G.dmt Data Path INTERLEAVED

Transceiver Information Down Stream Path Up Stream Path DSL Speed (Kbits/Sec) 1184 448 Margin (dB) 12.0 11.0 Line Attenuation (dB) 63.0 31.5 Transmit Power (dBm) 16.7 11.9

[dslr595148]

Ok.

#1 An original or very old style NID with a spark gap and ground wire can even get spiders in it that could cause an issue. Inspect the NID first before thinking of changes or wiring.

http://en.wikipedia.org/wiki/Network_interface_device

http://en.wikipedia.org/wiki/Demarcation_point

Running a good quality wire CAT5, no need for CAT6,  directly to the NID for the DSL modem jack may help. That is what I had done with mine. Depending on the number of loads or amount of wire in the house could also cause issues. But if the user's signal quality is not being pulled low due to a wiring issues, it would usually indicate a problem elsewhere. Unless there was noise being picked up on the premises wiring. Wire DSL directly to the NID and install a filter there for all other in house wiring may help. There used to be available what was called a NID Filter, and I am sure you can still get them.

Ideal Connection if house wiring is an issue, or very old, and lengthy. Install a filter / splitter at the NID.

Run CAT5 directly to the NID location, and install a dedicated jack for the DSL modem.

Remove all in house wiring from the NID.

Connect piece of CAT5 from the NID to the filter / splitter input

Connect all existing phone lines to the phone side of the filter output.

Connect the new DSL CAT5 directly to the NID before the filter / splitter, or to the DSL side of the filter / splitter, depending on the device purchased.

This will take all the existing premises wiring out of the picture unless there is a short circuit or excessive load somewhere in the house.

At this point all the single filters could be removed because the DSL is filtered at the NID.

http://www.homephonewiring.com/dsl.html

#2 You can test outbound to Giganews. But giganews has/had a test that will check your inbound connection from their servers to you.

I heard from another user that

---

Giganews is being watched very closely because of multipart binaries, and pirated material. MP3s and Video Content. 7 years ago you could get 10-20 MP3 albums in a single day, and that was with a 15/5 fios connection. So they started providing an encrypted connection service for an added fee. I have not messed with news groups for a very long time. Now with deep packet inspection, and other enforcement, I would not even think of it. No news I want there. But there may be content that people want? They may even be checking and limiting speed from that domain. Never tested. But let me see. It looks as if reverse trace routes and speed tests are being blocked by Verizon from Giganews to my router.

        Reverse Traceroute

        Tool news.giganews.com

        traceroute to *.*.*.*, 30 hops max, 60 byte packets
        1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
        2 te0-0-0-7.mpd22.iad02.atlas.cogentco.com (38.122.67.49) 0 ms 0 ms te0-7-0-9.mpd22.iad02.atlas.cogentco.com (38.122.62.193) 0 ms
        3 te0-0-0-4.ccr21.iad02.atlas.cogentco.com (154.54.31.105) 0 ms 0 ms te0-2-0-0.ccr21.iad02.atlas.cogentco.com (154.54.31.101) 0 ms
        4 uunet.iad01.atlas.cogentco.com (154.54.13.138) 28 ms verizon.iad01.atlas.cogentco.com (154.54.10.226) 40 ms uunet.iad01.atlas.cogentco.com (154.54.13.138) 28 ms
        5 0.ae1.RES-BB-RTR2.verizon-gni.net (152.63.32.157) 41 ms 41 ms 0.ae2.RES-BB-RTR1.verizon-gni.net (152.63.34.22) 13 ms
        6 * * *
        7 * * *
        8 * * *
        9 * * *
        10 * * *
        11 * * *
        12 * * *
        13 * * *
        14 * * *
        15 * * *
        16 * * Max number of unresponsive hops reached (firewall or filter?)

---

#3 Have the provider run a local loop test to see if any problems are indicated. If there are, then they could run the test with everything in the house disconnected, except the new DSL modem connection. If issues are still indicated, then the DSL provider needs to make connections on the local loop. Another user told me that they had issues when it rained, and it was because construction had left a splice box open on a line somewhere.

[LesleyH]

So if I'm understanding this right, the solution is to do some rewiring? I've had Verizon techs out here a couple years back because the internet was completely down, and they replaced a shredded wire... I asked them at the time if there was anything else that looked like it needed replacing or fixing, and they said no. 

Is this a thing that Verizon would come out and do? Setting up a dedicated jack for the DSL and all that? Because I gotta say, I have no idea how I would do that myself. >.<

[smith6612]

---

@LesleyH wrote:

So if I'm understanding this right, the solution is to do some rewiring? I've had Verizon techs out here a couple years back because the internet was completely down, and they replaced a shredded wire... I asked them at the time if there was anything else that looked like it needed replacing or fixing, and they said no. 

Is this a thing that Verizon would come out and do? Setting up a dedicated jack for the DSL and all that? Because I gotta say, I have no idea how I would do that myself. >.<

---

In most cases it's a good idea to get the dedicated jack set up (also called a "Homerun"). Microfilters add what appears to be length to the lines, and also can go bad over time causing problems. Away from that, why not get a direct connection for the modem? It can only help.

Otherwise, what DSLR is asking you to do is to get your transceiver statistics checked from your NID. If you're not able to do this, get Verizon to check the problem out. Just be sure to ask about what they can and can't do for free, as usually inside work requires additional charges (Homeruns should be free as a part of the DSL service, for as long as your existing wiring is good. Customers with 5+Mbps on their lines used to get these for free as soon as they ordered such a speed). Testing at the NID is a good way to get an idea of what could be going on inside of your home that is degrading service, but it is also another way to prove where a problem is for support. From there you can decide if you want to run wire.