dslreports logo
site
spacer

spacer

spacer




how-to block ads



Verizon Online DSL page on DSLReports
Six Month Rating

Reviews:
bullet 4501 reviews (2193 good) (1259 bad)
bullet Submit a review by email click here
bullet login for new review notification feature

Review by a333 See Profile

  • Location: Rego Park,Queens,NY
  • Cost: $19 per month (12 month contract)
  • Install: about 10 days
  • Telco party Verizon
Good "Great, once you get Verizon to fix up the local infrastructure"
Bad "Tech support nightmare unless you use the Direct forum"
Overall "Rock solid service... good value if you're willing to deal with poor tech support."
Pre Sales information:
Install Co-ordination:
Connection reliability:
Tech Support:
Services:
Value for money:
(ratings match consensus)

My Other Reviews

·T-Mobile US
UPDATE 08/31/2012: Finally decided to upgrade to the enhanced plan. called in and was told I qualify for 7.1/768 speeds, so I went ahead and upgraded. Minor downer: since I was an existing customer, I could only get the enhanced plan for $34.95 month-to-month, as opposed to the "new customer" price of $29.99. I was told I COULD get the lower price myself, but I would have to disconnect and reconnect service, which I really couldn't deal with given my parents' reliance on internet (and the fact that Verizon is notorious for having 2+ week downtime, and the potential for losing your port at the DSLAM and locking you out of getting service again for months on end.) Upgrade order was processed and the agent told me I should see the upgrade take effect the same day. When I rebooted my modem the next morning, I noticed my WAN IP had changed quite drastically (gone from a 72.xx.xx.xx to a 108.xx.xx.xx), and sure enough, I was syncing on the 5 Mbit/s profile with interleaved mode enabled. Speeds clocked in at around 4.8 - 4.9 Mbits/s. down and around 720 - 730 Kbits/s up. Seeing as my line stats were still quite solid, I went ahead and posted a request to be switched over to FastPath on the Verizon Direct forum, to lower first-hop latencies a bit. The change took place by the next day I rebooted my modem, and as an added surprise, I saw that I was syncing on the 7.1 Mbits/s profile with Fastpath enabled. Speedtests showed a solid 6.6 - 6.7 Mbits/s down and the same ~730 Kbits/s up.

The connection is definitely a LOT more responsive, and large downloads are less painful (a 700 MB file that might have taken an hour and 45 minutes not takes roughly 15 minutes). Also, I can now actually QoS my VoIP line without drastically slowing down other connections. Since I do still have 16 - 18 dB noise margins on the downstream side, I am going to try to get a loop test done to possibly get provisioned at 10 Mbits/second, but even if that doesn't work out, this connection should do fine until FiOS gets deployed to my apartment building (although the buildout is dead in most parts of the country, I happen to live in NYC where Verizon has a franchise requirement to finish deploying by 2014). I have seen fiber crews working during the early morning hours, and according to them, my block is on track to be lit up within the next few months.

UPDATE 08/06/2012: Well it's been an uneventful 3 years... speeds are always right around 1000/384 regardless of the time of day, and pings are also very stable. Got a voip.ms account for my parents, and set it up with QoS on my DD-WRT router, and voice quality is perfect using the G.711 (u-law) codec. Latency and jitter are excellent, which is to be expected from a FastPath-enabled DSL connection.

Bandwidth is a little bit dated, and feels rather inadequate in this day and age of HD YouTube/Netflix streaming, though I can easily have 1 stream going along with a phone conversation, thanks to the QoS at my router. Also, given the recent change in policy to no dry-loop option, I'll probably be switching over to a dry line service from DSLExtreme, since that will get me more bandwidth at a lower price than the $50 I am paying right now for basic message rate service and the DSL.

UPDATE 8/6/09: Just moved to a new place only about a mile or so away.... pretty much uneventful move. Phone was hooked up by 8/4, and DSL got solid sync the next day, although for some reason they pushed my SRD to 8/12/09....lol. Anyway, still rocking at 1 Mbit/384 Kbit. The line is still knock on wood, with stats telling me that I'm approximately 7,500 feet (EWL) from the CO.
Just realized I haven't updated the monthly cost in a while... just changed it to the $19.99 rate.

UPDATE 6/13/09: Well, it's been I think 3 years now, and no problems so far. Excellent uptime, latency, and routing. And I'd notice.... considering that I'm on 24/7, and also run SSH/FTP servers and SOCKS proxies, using DynDNS.
No comment on tech support, as I've never had to use it. Seriously, holding synch for 6 months = EPIC WIN. If only Verizon didn't push out that firmware update... oh well.

Anyways, speedtest: »www.speedtest.net/result/516865644.png

Stats:
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) 1179 447
Margin (dB) 31.0 26.0
Line Attenuation (dB) 23.0 11.5
Transmit Power (dBm) 12.0 11.9

The stats speak for themselves..... this line is knock on wood.
7.1 is finally available, but I'm OK with 1/384. Most of my heavy downloading can be done at school anyway.... 10 Mbit symmetric ethernet FTW....=)

Plan: 1/384
Price: $19.95/mo for 1 year I think... + the basic landline I don't need.

Keep up the good work, Verizon.

UPDATE 11/12/08: Got the 1Meg/384K bump today. Called my local business office yesterday, and was given a upgrade effective date of today. Upgrade went on schedule, and I an happily cruising at slightly over 1 mbit download and a little shy of 384 K upload. Speed test and stats:

»www.speedtest.net/result/354994063.png

Stats:


Transceiver Revision: 4.2.0.11
Vendor ID Code: 4
Line Mode: ADSL2+ Mode
Data Path: Fast
Transceiver Information Down Stream Up Stream
DSL Speed (Kbits/Sec) 1180 447
Margin (dB) 31.0 25.0
Line Attenuation (dB) 23.0 11.5
Transmit Power (dBm) 15.4 11.9

UPDATE 4/11/08- Going on to nearly two years of nothing but rock-solid service. I only have to reset the modem about once every two months, and my IP address doesn't change too often, good for managing servers. I might have to upgrade to 3/768 soon, as 128 K is just not cutting it for uploads and server hosting, among other things.
Considering all the capping going on in the cable industry, and the throttling of bittorrent and such, Verizon has done a good job maintaining their position as a 'dumb pipe' provider. No funny business; that's what is a good ISP. In all, great job Verizon, and keep it up!

UPDATE 10/29/07- Everything is still rock-solid for me. Just a brief issue a few weeks before, but a quick call to tech support solved it via a password reset. Funnily enough, I was lucky enough to get an actual american guy on the line... go figure. We had a nice laugh about the fact that I could literally spit at my CO

Original Review:
I've had Verizon DSL for almost like....2 yrs., so I think its about time I review it.
At first, it took almost 6 months to actually qualify my line, as I was on the distance limits where DSL starts crapping out. Finally, ordered month to month 768 service in April 2006. Kit arrived about 4 days later, with SRD a week later. About 5 days later, I had set up everything, and decided to turn on the modem just for the hell of it. Surprise, it synced right up. Went through the set-up, and speeds were approx. 500 K. Well below the advertised, but was great compared to dial up.

Fast-forward to December 2006-Jan 2007, and speeds often climbed to about 720 K. Funnily enough, they went back down gradually, from January to September. Also, by then, I learned about the transceiver stats thing, and managed to pinpoint it down to the line itself. Called VZ numerous times, got told it was the best the loop could handle, due to distance.

Then, in June or July of '07, few weeks after getting the 14.95 deal, I woke up to find no dialtone or DSL. Called voice repair, they sent a tech within like...30 minutes. tops. They managed to fix the dialtone, but DSL stayed out. The guy who was fixing the dialtone issue apparently had DSL equipment as well, so he did some line tests, and told me something in my particular loop was preventing me from getting the full sync.

The next week, I got a call from the CO guys, telling me that I would lose dialtone for an hour, while they switched me to a better pair. I told them to got ahead. About 2 hrs later, sure enough, the DSL light synced right up, and sure enough I had the perfect 864 sync!!
Finally, life was good.

Now, as of sept '07, I've moved to a place within 3,500 ft. of the CO, so my connection is even more rock solid. Also, I got switched to ADSL2+ and FastPath, so the connection now simply spoils me. Now then only thing is to get the 3/768 package.

»www.speedtest.net/result/186902064.png

Looks good to me.....
So, overall, once issues are resolved, Verizon rocks in terms of reliability. I mean, it's DSL, so longer loops will always be a bit iffy, but as far as the price vs. speed, I think it's still the best value around.

Ping test to my local SIP provider's server:

root@DD-WRT:~# ping newyork.voip.ms
PING newyork.voip.ms (74.63.41.218): 56 data bytes
64 bytes from 74.63.41.218: seq=0 ttl=54 time=11.127 ms
64 bytes from 74.63.41.218: seq=1 ttl=54 time=12.102 ms
64 bytes from 74.63.41.218: seq=2 ttl=54 time=10.830 ms
64 bytes from 74.63.41.218: seq=3 ttl=54 time=12.467 ms
64 bytes from 74.63.41.218: seq=4 ttl=54 time=10.136 ms
64 bytes from 74.63.41.218: seq=5 ttl=54 time=11.544 ms
64 bytes from 74.63.41.218: seq=6 ttl=54 time=11.442 ms
64 bytes from 74.63.41.218: seq=7 ttl=54 time=12.152 ms
64 bytes from 74.63.41.218: seq=8 ttl=54 time=11.257 ms
64 bytes from 74.63.41.218: seq=9 ttl=54 time=10.425 ms
64 bytes from 74.63.41.218: seq=10 ttl=54 time=11.815 ms
64 bytes from 74.63.41.218: seq=11 ttl=54 time=11.252 ms
64 bytes from 74.63.41.218: seq=12 ttl=54 time=12.112 ms
64 bytes from 74.63.41.218: seq=13 ttl=54 time=11.269 ms
64 bytes from 74.63.41.218: seq=14 ttl=54 time=13.887 ms
64 bytes from 74.63.41.218: seq=15 ttl=54 time=10.839 ms
64 bytes from 74.63.41.218: seq=16 ttl=54 time=11.509 ms
64 bytes from 74.63.41.218: seq=17 ttl=54 time=15.069 ms
64 bytes from 74.63.41.218: seq=18 ttl=54 time=10.806 ms
64 bytes from 74.63.41.218: seq=19 ttl=54 time=13.429 ms
^C
--- newyork.voip.ms ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 10.136/11.773/15.069 ms

A bit further out to Chicago:

root@DD-WRT:~# ping chicago.voip.ms
PING chicago.voip.ms (64.120.22.242): 56 data bytes
64 bytes from 64.120.22.242: seq=0 ttl=57 time=35.086 ms
64 bytes from 64.120.22.242: seq=1 ttl=57 time=34.060 ms
64 bytes from 64.120.22.242: seq=2 ttl=57 time=36.891 ms
64 bytes from 64.120.22.242: seq=3 ttl=57 time=35.080 ms
64 bytes from 64.120.22.242: seq=4 ttl=57 time=33.980 ms
64 bytes from 64.120.22.242: seq=5 ttl=57 time=35.113 ms
64 bytes from 64.120.22.242: seq=6 ttl=57 time=34.368 ms
64 bytes from 64.120.22.242: seq=7 ttl=57 time=35.920 ms
64 bytes from 64.120.22.242: seq=8 ttl=57 time=35.581 ms
64 bytes from 64.120.22.242: seq=9 ttl=57 time=34.816 ms
64 bytes from 64.120.22.242: seq=10 ttl=57 time=35.930 ms
64 bytes from 64.120.22.242: seq=11 ttl=57 time=36.044 ms
64 bytes from 64.120.22.242: seq=12 ttl=57 time=34.479 ms
64 bytes from 64.120.22.242: seq=13 ttl=57 time=33.615 ms
64 bytes from 64.120.22.242: seq=14 ttl=57 time=34.764 ms
64 bytes from 64.120.22.242: seq=15 ttl=57 time=34.915 ms
64 bytes from 64.120.22.242: seq=16 ttl=57 time=36.066 ms
64 bytes from 64.120.22.242: seq=17 ttl=57 time=33.177 ms
64 bytes from 64.120.22.242: seq=18 ttl=57 time=34.636 ms
64 bytes from 64.120.22.242: seq=19 ttl=57 time=34.044 ms
^C
--- chicago.voip.ms ping statistics ---
20 packets transmitted, 20 packets received, 0% packet loss
round-trip min/avg/max = 33.177/34.928/36.891 ms

member for 7.4 years, 1591 visits, last login: 1 year ago
updated 2.2 years ago

Comments: