Slow Advanced HSI In Brooklyn (Ocean Hill)

I have the High Speed Internet Advanced product from Verizon, rated between 4 and 7 Mbps.

Up until approximately 2 months ago I consistently received between 4.5 and 5.2 Mbps Internet speed. Since then the best I get is 3.5 Mbps. At times the service slows to a painful .5 Mbps.

Sunday Evening into Monday morning May 5/6 I spent on the phone with a Verizon 1st level support tech. She had me do all kinds of obvious things (checking for filters on all the phones, etc.)

The tech finally acknowledged the issue lies in the Verizon central office that services my area. The tech promised the problem with my Internet speed would be resolved.

It is now 10 days plus later. The speed I receive is still way below the minimum I should be getting. And, at times the speed slows down so badly, I can barely use The Internet at all. Obviously the problem at the central office remains.

Is anyone else in the Bed-Stuy/Ocean Hill/Browmsville area of Brooklyn having a similar issue with Verizon HSI?

Accepted answers

MAJ216ROCK

My service was out from Thursday morning June 6th until Monday morning June 10th. The techs in the Central Office had more work to do than previously thought. I called Verizon Monday morning to find out when my service would be restored.

A Verizon Tech in Ohio called and instructed me to do a hard reset on the DSL router.

Now I am consistently operating at over 6.5 Mbps! This is the highest speed I've ever had.

So, I'm very happy to report this issue resolved.

There is a cautionary tale out of all of this - if you are not receiving the speed that you PAY FOR, complain, complain, complain to Verizon until they fix it! It took me nearly two months to resolve this issue, but in the end I am getting the speeds I'm supposed to receive! Smiley Happy

All comments

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 the final hop (bottom-most line of the trace) might contain a hop with your IP address in it. Remove that line. 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.

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?

MAJ216ROCK

Here is the information you requested:

news.giganews.com

traceroute to ****Edited for privacy ****, 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (216.196.98.4) 0 ms 0 ms 0 ms
2 ash-bb1-link.telia.net (213.248.70.241) 0 ms 0 ms 0 ms
3 TenGigE0-2-0-0.GW1.IAD8.ALTER.NET (63.125.125.41) 19 ms 19 ms GigabitEthernet2-0-0.GW8.IAD8.ALTER.NET (63.65.76.189) 19 ms
4 0.xe-5-0-0.XL4.IAD8.ALTER.NET (152.63.36.50) 15 ms 15 ms 15 ms
5 0.so-9-3-0.RES-BB-RTR2.verizon-gni.net (152.63.37.122) 23 ms 24 ms 0.so-0-2-0.RES-BB-RTR2.verizon-gni.net (152.63.30.14) 17 ms
6 P0-8-0-0.NYCMNY-LCR-21.verizon-gni.net (130.81.22.17) 29 ms B200.NYCMNY-LCR-21.verizon-gni.net (130.81.209.111) 30 ms P0-8-0-0.NYCMNY-LCR-21.verizon-gni.net (130.81.22.17) 35 ms
7 * P13-0.NYCMNY-NYCKNYBR-ERXG04.verizon-gni.net (130.81.45.239) 28 ms 27 ms
8 * * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * Max number of unresponsive hops reached (firewall or filter?)

news-europe.giganews.com

traceroute to ****Edited for privacy ****, 30 hops max, 60 byte packets
1 vl201.gw1.ams.giganews.com (216.196.110.3) 0 ms 0 ms 0 ms
2 te7-8.ccr01.ams05.atlas.cogentco.com (149.11.104.17) 0 ms 0 ms 0 ms
3 te0-5-0-1.ccr22.ams03.atlas.cogentco.com (154.54.72.50) 0 ms te0-3-0-7.ccr22.ams03.atlas.cogentco.com (130.117.51.34) 0 ms te0-5-0-1.ccr22.ams03.atlas.cogentco.com (154.54.72.50) 0 ms
4 te0-4-0-0.mpd21.lon13.atlas.cogentco.com (154.54.60.201) 8 ms te0-5-0-0.ccr22.lon13.atlas.cogentco.com (154.54.61.154) 8 ms te0-2-0-0.mpd21.lon13.atlas.cogentco.com (130.117.38.125) 8 ms
5 154.54.77.234 (154.54.77.234) 14 ms te0-3-0-4.ccr22.bos01.atlas.cogentco.com (154.54.5.122) 81 ms te0-1-0-0.ccr21.lpl01.atlas.cogentco.com (154.54.60.98) 14 ms
6 te0-7-0-3.ccr22.jfk02.atlas.cogentco.com (154.54.44.53) 90 ms te0-7-0-9.ccr21.bos01.atlas.cogentco.com (154.54.85.209) 80 ms te0-4-0-2.ccr21.bos01.atlas.cogentco.com (154.54.44.197) 83 ms
7 te0-0-0-11.mpd21.jfk02.atlas.cogentco.com (154.54.44.17) 82 ms te0-7-0-11.mpd22.jfk02.atlas.cogentco.com (154.54.44.25) 89 ms te0-1-0-6.ccr21.jfk05.atlas.cogentco.com (154.54.3.166) 90 ms
8 te0-1-0-4.ccr21.jfk05.atlas.cogentco.com (154.54.31.6) 82 ms te0-1-0-2.ccr21.jfk05.atlas.cogentco.com (154.54.7.10) 90 ms 0.xe-10-3-0.BR2.NYC4.ALTER.NET (204.255.168.113) 130 ms
9 P0-0-0-0.NYCMNY-LCR-22.verizon-gni.net (130.81.151.225) 129 ms 0.xe-10-3-0.BR2.NYC4.ALTER.NET (204.255.168.113) 209 ms 0.xe-8-3-0.BR2.NYC4.ALTER.NET (204.255.168.109) 123 ms
10 P12-0.NYCMNY-NYCKNYBR-ERXG04.verizon-gni.net (130.81.45.237) 124 ms 125 ms 125 ms
11 P0-0-0-0.NYCMNY-LCR-22.verizon-gni.net (130.81.151.225) 126 ms P1-0-0-0.NYCMNY-LCR-22.verizon-gni.net (130.81.151.235) 127 ms P0-0-0-0.NYCMNY-LCR-22.verizon-gni.net (130.81.151.225) 125 ms
12 * P12-0.NYCMNY-NYCKNYBR-ERXG04.verizon-gni.net (130.81.45.237) 127 ms *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * * Max number of unresponsive hops reached (firewall or filter?)

Modem Information:

Westell VersaLink Model 327W

I do not have a RJ-45 WAN Port Router attached to the modem.

Thank you.

dslr595148

Visit http://192.168.1.1/ for me and do the following:

a) If you see a Blue and White Westell page, mouse over Troubleshooting, go to DSL, and choose Transceiver Statistics. Copy and paste the information on that page.

b) If using the Red and Black Firmware: Go to System Monitoring > Advanced Monitors > Transceiver Statistics. Copy and paste the information on that page.

c) Try visiting http://192.168.1.1/transtat.htm which is a direct link to the Stats on older modems.

d) If you need a Username and Password, try the following:

admin/password

admin/password1

admin/admin

admin/admin1

admin/Serial Number.

By Serial Number, I don't mean type in the words Serial Number. I mean find and type in the serial number found on the bottom of this router.

MAJ216ROCK

Hello,

Here are the transceiver stats you requested:

Transceiver Statistics

Transceiver Revision:	7.2.3.0
Vendor ID Code:	4
Line Mode:	ADSL2+ Mode
Data Path:	Interleaved

Transceiver Information	Downstream Path	Upstream Path
DSL Speed (Kbits/Sec)	3062	862
Margin (dB)	15.0	9.0
Line Attenuation (dB)	41.0	27.0
Transmit Power (dBm)	17.1	12.1

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.

MAJ216ROCK

I opened another trouble ticket with Verizon Monday morning May 27th. Verizon contacted me several times before I was home to receive the call. According to the tech that called my DSL line has been "optimized". The modem I'm using, a Westell 327W, is too old to make use of the "optimized" circuit. So, it slows the circuit down. Verizon is sending out a replacement modem at no cost. If after testing the new modem the slowness issue persists, they will then send out a tech. I'll update this thread with my results once I receive and install the new modem.

smith6612

I'm not sure what will come out of the newer modem. If the 327w is at the point where it cannot sync correctly, that's one thing. Otherwise the 327w is an ADSL2+ modem, so besides getting a faster CPU, more RAM, and better Wireless in the gateway, there is nothing stopping that old modem from getting any speed you want. The optimizer doesn't care what modem is in use; only the ADSL spec being used, line conditions, package speed range and stability logs.

MAJ216ROCK

Ok. I received the replacement modem - an Actiontec model. At first I was getting 5.03 Mbps. But, it wasn't long before I once again received terribly slow speeds again. The speed is all over the dial. So, the next step is for Verizon to send out a technician to my home to try and troubleshoot this issue. They say the Central Office setup is working properly. I hope this can be resolved soon. Trying to stream content over an unreliable circuit is nerve-wracking at best!