I’ve had Verizon DSL since Fall 2001, and it’s been a mixed bag. When we only had one computer, we’d often have connection issues that a modem or computer restart would fix. Adding a wireless router solved those problems, but getting devices to connect wirelessly was a pain. Later, Verizon bundled MSN, which took some effort to install. Overall, I’m happy with the reliability, but the speed leaves a lot to be desired. My connection is usually less than 100 KBps (0.8 Mbps), and downloads slow down as they progress. I’m using a Westell modem (an old model that lays flat) with a Linksys WRT54G router. My computer is a new HP Pavilion with a Pentium 4 and 512 MB RAM, so it’s not the hardware. I know people who got faster DSL recently, so I suspect my modem is the bottleneck. What are your experiences with DSL or other broadband types? Any tips for squeezing more speed out of an old setup?
Topic Summary: User with Verizon DSL since 2001 has slow speeds under 100 KBps, suspects old Westell modem is bottleneck despite new PC; uses Linksys
Topic Overview (Wikipedia):
DSLReports was a North American-oriented broadband information and review site based in New York City. The site’s main focus was on internet, phone, cable TV, fiber optics, and wireless services in the United States and Canada, as well as other countries.
— Read more on Wikipedia
Official Documentation & Reference Links:
---
title: DSL Troubleshooting Flowchart
---
flowchart TD
A[Start] --> B{Internet Down?}
B -- Yes --> C[Check Modem Lights]
C --> D{DSL Light On?}
D -- No --> E[Check Phone Line Connection]
E --> F[Jack Filter Installed?]
F -- No --> G[Install DSL Filter]
F -- Yes --> H[Contact ISP]
D -- Yes --> I[Reboot Modem and Router]
I --> J{Still Down?}
J -- Yes --> H
J -- No --> K[Success]
B -- No --> L[Speed Slow]
L --> M[Run Speed Test]
M --> N{Below Expected?}
N -- Yes --> O[Check for Interference]
O --> P[Move Modem Away from Electronics]
P --> Q[Test with Wired Connection]
Q --> R[Consider Upgrade]
N -- No --> S[Check Network Usage]
I had Verizon DSL since November 2004, initially at $29.95/month for 768/128 kbps. After a year, they dropped the price to $14.95. My speed issues turned out to be caused by damaged outside wiring from weather exposure. After the technician replaced the line, my speeds jumped from erratic drops to a stable 864/160 kbps. I also learned that you can access the Westell 2200 modem at 192.168.1.1 with default credentials (admin/password) to set up PPPoE so you don’t need extra software. If you’re far from the CO (central office), speeds suffer significantly. Check your line quality and modem config before blaming the ISP.
I ran speed tests on BroadbandReports and got consistent 701/131 kbps. For $14.95, that was acceptable back then. But compared to modern fiber or cable, it’s night and day. If you’re still on DSL today (2026), you’re probably in a rural area or on a legacy plan. Have you checked if fiber is available in your area?
Speed issues aren’t always on your end. Many servers limit download speeds—our hosting company caps at 128 kbps. When I had 3 Mbps cable, I tested by downloading from multiple sources simultaneously: FreeBSD ISOs, OpenOffice, etc. One server gave 115 kbps, another 64 kbps, so the bottleneck was the remote server, not my connection. Your DSL connection might be fine for most tasks, but if you’re pulling from a speed-limited server, it’ll feel slow.
Also, WiFi signal strength can throttle throughput. Even with a decent router, interference from neighbors or walls can halve your speed. I’d suggest hardwiring your computer for a true speed test. And if you’re on older equipment, consider upgrading to a modern router with QoS features to prioritize traffic.
For what it’s worth, I eventually switched to fiber (not Verizon, but a local provider) and never looked back. But DSL is still a viable option for light browsing and email if you optimize the setup.
Having gone through similar troubleshooting, I’d like to add some closing thoughts that tie together what everyone has said. The Mermaid diagram posted earlier captures the ideal systematic approach: start by isolating whether the bottleneck is local or remote. Too many people skip the “check server limitations” step and immediately blame their ISP or hardware. stlgooie made a great point about testing multiple sources — I’ve seen the same thing where a single download from a throttled server makes a 3 Mbps line feel like dial-up.
The DSLReports site (formerly BroadbandReports) is still the best resource for this kind of detective work. Their speed test and tweak test can reveal bufferbloat, MTU issues, and line noise that a simple ping won’t catch. BuffaloHELP’s experience with the Westell modem and PPPoE config is exactly the kind of thing you’d diagnose using their line quality tool. The modem config screen at 192.168.1.1 lets you check SNR margins and attenuation — if those numbers are borderline, no amount of router tweaking will fix it.
As for the old hardware — the WRT54G is legendary, but its CPU can struggle with modern traffic patterns, especially if you’re running multiple devices. Even with Tomato or DD-WRT, the WiFi is only 802.11g. Hardwiring a speed test as suggested is essential to separate router issues from line issues. If you’re stuck on DSL because fiber isn’t available, max out what you can: ensure your modem is in bridging mode, use a wired connection for critical use, and consider a newer router with QoS to prioritize gaming or streaming over background updates.
Ultimately, if your DSL line is healthy and you’re still under 1 Mbps, you’re likely distance-limited from the CO. At that point, the only real fix is lobbying for better infrastructure or checking for WISPs or LTE fixed wireless. But for light use, a well-tuned DSL connection can still be surprisingly reliable.