$540 via promo credit when you add a new smartphone line with your own 4G/5G smartphone on postpaid Unlimited Plus plan between 5/18/23 - 5/31/23 & port-in req'd. Promo credit applied over 36 months; promo credits end if eligibility requirements are no longer met.
As the year wound down so to did my DSL speeds. I got lots of drop outs when it rained, uploads so slow they crippled the possibility actually using the internet. Sometimes I was getting 32Kbps uploads and that isn't enough to send ACK packets back for the downloads. Looking at the status in the modem there were tons of HEC Errors and others.
I decided to get it straight this year. I redid my house phone wiring. In wall wiring - everything. I bought new phone jacks. I replaced all phone cords. The one that really made a difference was the cord that went to the DSL modem and probably came with it.
This improved things. I still had some errors and could hear clicky noise on the line intermittantly. Especially after weather. The noise was bad enough to interfere with important calls and was jacking up the internet. I got a service call schedualed and a sevrice man came out. He tracked down a bad/old splice on the line and did a great job.
Now the phone is clear and the connection looks a lot cleaner. However I am not getting the speeds I hoped for. My DSL status looks like this from the command line:
>adsl info --stats
adsl: ADSL driver and PHY status
Status: Showtime Retrain Reason: 1
Channel: INTR, Upstream rate = 288 Kbps, Downstream rate = 1792 Kbps
Link Power State: L0
Line Status: No Defect
Training Status: Showtime
SNR (dB): 29.1 31.0
Attn(dB): 57.0 23.0
Pwr(dBm): 17.1 11.9
Max(Kbps): 5344 1196
Rate (Kbps): 1792 288
K: 57(0) 10
R: 16 16
S: 4 16
😧 16 4
MSGc: 1 1
B: 56 9
M: 4 16
T: 1 1
R: 16 16
S: 4.0000 16.0000
L: 488 88
😧 16 4
SF: 57641 57626
SFErr: 0 0
RS: 979910 244910
RSCorr: 0 0
RSUnCorr: 0 0
HEC: 0 0
OCD: 0 0
LCD: 0 0
Total Cells: 4141556 0
Data Cells: 87079 0
Drop Cells: 436
Bit Errors: 0 0
ES: 21 0
SES: 9 0
UAS: 177 177
INP: 2.09 2.90
PER: 1.75 1.75
delay: 16.00 16.00
OR: 32.00 32.00
Bitswap: 0 0
I am paying for 3Mbps/384K. It seems almost in reach but I've been stuck with a celing of 1792 / 288 for a while. Attainable rates have been up in the 5000/1000 area but I don't get provisioned close to that. Is there something in place to limit my speed back when the line was noisy/ unreliable?
I would like to reset/reprovision this line. Is there an automated way to do this? I think I found it earlier - a check the connection on verizon's support site before but can't find it now.
I am far for the CO and there is a lot of attenuation but I wanna get this to work as best as I can.
#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.
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.
#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.
traceroute to *.*.*.*, 30 hops max, 60 byte packets
1 gw1-g-vlan201.dca.giganews.com (126.96.36.199) 0 ms 0 ms 0 ms
2 te0-0-0-7.mpd22.iad02.atlas.cogentco.com (188.8.131.52) 0 ms 0 ms te0-7-0-9.mpd22.iad02.atlas.cogentco.com (184.108.40.206) 0 ms
3 te0-0-0-4.ccr21.iad02.atlas.cogentco.com (220.127.116.11) 0 ms 0 ms te0-2-0-0.ccr21.iad02.atlas.cogentco.com (18.104.22.168) 0 ms
4 uunet.iad01.atlas.cogentco.com (22.214.171.124) 28 ms verizon.iad01.atlas.cogentco.com (126.96.36.199) 40 ms uunet.iad01.atlas.cogentco.com (188.8.131.52) 28 ms
5 0.ae1.RES-BB-RTR2.verizon-gni.net (184.108.40.206) 41 ms 41 ms 0.ae2.RES-BB-RTR1.verizon-gni.net (220.127.116.11) 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.
Verizon uses a system made by ASSIA to examine the DSL lines and adjust the provisioning of the line. Sometimes this system is overly aggressive. Other times, it's not aggressive at all.
For your line, have Verizon manually provision your line to 2200kbps down, 640kbps up and have it remain there to see how stable the circuit is. If it remains stable, get your downstream bumped by 400kbps to see how that behaves. Chances are, you'll start to see the line error around that mark given the attenuation.
Getting Verizon to do this won't be easy, since most techs rely on an automated system to do provisioning, but for those who have access to the line card, and provided you are not on a Litespan DSLAM with a Juniper BRAS in the mix, this can be done. I've had this done several times on lines that are too far for 3Mbps, but are not too far for more than 1.5Mbps to be delivered.