• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Don't get Verizon DSL.

I've had it for three years with maybe, on average, one hour of downtime a month - usually every 3 months or so, and never during peak hours.

It just worked. Never been misbilled or anything. My mom uses their email accounts and that's about as reliable as the line has been.
 
I am peeved with them because although they have lowered my rate, I cannot get the higher bandwidth because of me being stuck on an ATM.

However, I just noticed that my being routed through another DNS, this one much closer to home. I don't think I am on the ATM anymore but they tell me I still am.

And btw, they lowered my DSL bill by $10 but have raised my phone service by$8. Some deal!
 
Ping statistics for 216.239.53.100:
Packets: Sent = 93, Received = 76, Lost = 17 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 1862ms, Maximum = 2354ms, Average = 2128ms

Tracing route to www.anandtech.com [168.143.107.162]
over a maximum of 30 hops:

1 * * 2139 ms 10.6.1.1
2 * * * Request timed out.
3 * 2127 ms 2079 ms so-0-0-0-0.CORE-RTR2.PITT2.verizon-gni.net [130.
81.8.154]
4 * 2131 ms 2102 ms so-1-0-0-0.BB-RTR1.PHIL.verizon-gni.net [130.81.
9.21]
5 * * * Request timed out.
 
Mine scheduled service ready date was the 8th.

Then it got pushed back to the 15th.

Then it got pushed back to the 28th.

I wonder how far it will get pushed back next week...

Right now the fastest I can get at my house is a 28.8k connection so I am still going to wait.
 
Are you having problems with installation or is it something other than that?

Installation is rarely smooth and efficient with DSL but after the initial "bumps" it usually smoothes out.
 
Like I said in other threads, the DSL itself is great with very little downtime.

However, should you want to upgrade your service, or if you require any sort of support, you will have to deal with some jackass from the ghetto who probably doesn't even OWN a computer, can barely read their training manual, and has the reasoning capability of a Down's syndrome child after a full frontal lobotomy.

Right now, I think Verizon employees are one notch ABOVE spammers on my hate list.
 
Try dealing with adelphia (both powerlink and business side). I had to tell the rep yesterday to check his queue to see if it just jumped in the time I was on the phone talking to him trying to tell him there was an issue with one of their routers. "oh yeah, it did... Wait now I can't get anything on my computer. Maybe there is something wrong". Ten hours later I get a call from a tech saying that the internet will be up in either a 1/2 hour or 4 hours, there was an issue with a router. And that was the business side! I won't even go into the powerlink side.
 
It worked fine until about yesterday... the my pings started going to 2000 and staying around there. Occasionally they'd return to normal... generally when I was on the phone with support.

Reply from 216.239.53.100: bytes=32 time=117ms TTL=49
Reply from 216.239.53.100: bytes=32 time=108ms TTL=49
Reply from 216.239.53.100: bytes=32 time=114ms TTL=49
Reply from 216.239.53.100: bytes=32 time=125ms TTL=49

That's slower than it shoudl be, but I can deal with it. 2000 is not acceptable. The techs are too incompetent to understand that the slowdown is at the FIRST HOP... not the kind of thing you would expect from a power outage 6 hours away, or a bunch of RPC worms.

edit:
Reply from 216.239.53.100: bytes=32 time=2191ms TTL=49
Reply from 216.239.53.100: bytes=32 time=2308ms TTL=49
Reply from 216.239.53.100: bytes=32 time=2237ms TTL=49
and we're back 🙁
 
Don't get Verizon DSL.
Agreed. I was a happy subscriber for two years until I had to move. They f'ed up my new order and told me it would be 3-4 additional weeks on top of the two I had already waited for installation. I said screw it and went with cable. Of course Verizon DSL can not compete speedwise or pricewise with my current cable setup. I am only paying $19.95 for cable internet and average 3.0mbps down with a 128kbps up cap.
 
Originally posted by: CTho9305
Ping statistics for 216.239.53.100:
Packets: Sent = 93, Received = 76, Lost = 17 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 1862ms, Maximum = 2354ms, Average = 2128ms

Tracing route to www.anandtech.com [168.143.107.162]
over a maximum of 30 hops:

1 * * 2139 ms 10.6.1.1
2 * * * Request timed out.
3 * 2127 ms 2079 ms so-0-0-0-0.CORE-RTR2.PITT2.verizon-gni.net [130.
81.8.154]
4 * 2131 ms 2102 ms so-1-0-0-0.BB-RTR1.PHIL.verizon-gni.net [130.81.
9.21]
5 * * * Request timed out.

Have you ever tried a different DSL Modem?

Have you eliminated all but one DSL Microfilter in the house?


 
Originally posted by: dmcowen674
Originally posted by: CTho9305
Ping statistics for 216.239.53.100:
Packets: Sent = 93, Received = 76, Lost = 17 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 1862ms, Maximum = 2354ms, Average = 2128ms

Tracing route to www.anandtech.com [168.143.107.162]
over a maximum of 30 hops:

1 * * 2139 ms 10.6.1.1
2 * * * Request timed out.
3 * 2127 ms 2079 ms so-0-0-0-0.CORE-RTR2.PITT2.verizon-gni.net [130.
81.8.154]
4 * 2131 ms 2102 ms so-1-0-0-0.BB-RTR1.PHIL.verizon-gni.net [130.81.
9.21]
5 * * * Request timed out.

Have you ever tried a different DSL Modem?

Have you eliminated all but one DSL Microfilter in the house?
1. I don't have any others
2. I disconnected everything from that line, rather than deal with filters. Once it works with NOTHING hooked up, I'll start worry about reconnecting stuff.
 
Up for two years now....low ping, fast speeds, and cheap rates. Prices have been dropping since I've got it, AND speeds kept going up. I have no downtime. Connections are on 24/7.
 
Originally posted by: CTho9305
Ping statistics for 216.239.53.100:
Packets: Sent = 93, Received = 76, Lost = 17 (18% loss),
Approximate round trip times in milli-seconds:
Minimum = 1862ms, Maximum = 2354ms, Average = 2128ms

Tracing route to www.anandtech.com [168.143.107.162]
over a maximum of 30 hops:

1 * * 2139 ms 10.6.1.1
2 * * * Request timed out.
3 * 2127 ms 2079 ms so-0-0-0-0.CORE-RTR2.PITT2.verizon-gni.net [130.
81.8.154]
4 * 2131 ms 2102 ms so-1-0-0-0.BB-RTR1.PHIL.verizon-gni.net [130.81.
9.21]
5 * * * Request timed out.

ouch!
 
Here is a recommendation to the newbs that wants to order DSL from Verizon.

Call up Earthlink and order from them instead. I believe they are resellers for Verizon and other DSL providers.
They'll get the guys out quicker than Verizon can themselves.

Earthlink Customer service is way more competent than Verizon, and they'll take care of problems quickly.
 
I have been having the same problem, but last night they told me they were getting hit by a worm, and today the speed is back to normal.
 
Originally posted by: dabuddha
Mine works perfectly fine. What's wrong with yours?

Scroll up.

edit:
cst@unix48~% traceroute ctho9305.ath.cx
traceroute to ctho9305.ath.cx (141.151.169.121), 30 hops max, 40 byte packets
1 CYH-A100-VL141.GW.CMU.NET (128.2.13.129) 1 ms 0 ms 0 ms
2 CORE0-VL1000.GW.CMU.NET (128.2.0.12) 1 ms 0 ms 0 ms
3 HYPER-VL501.GW.CMU.NET (128.2.33.225) 1 ms 1 ms 1 ms
4 bar-cmu-ge-4-0-0-0.psc.net (192.88.115.181) 1 ms 0 ms 0 ms
5 minime-ge-0-1-0-0.psc.net (192.88.115.5) 1 ms 1 ms 1 ms
6 pos4-1-1-0.a01.pitbpa05.us.ra.verio.net (199.239.216.13) 1 ms 1 ms 1 ms
7 p4-2-1-0.r02.mclnva02.us.bb.verio.net (129.250.16.90) 6 ms 6 ms 6 ms
8 p16-7-0-0.r02.stngva01.us.bb.verio.net (129.250.5.46) 7 ms 7 ms 7 ms
9 dca-brdr-02.inet.qwest.net (205.171.14.45) 8 ms 8 ms 8 ms
10 dca-core-02.inet.qwest.net (205.171.9.57) 8 ms 8 ms 8 ms
11 dca-edge-03.inet.qwest.net (205.171.9.62) 8 ms 14 ms 8 ms
12 65.118.218.46 (65.118.218.46) 11 ms 227 ms 127 ms
13 so-0-1-0-0.BB-RTR1.PHIL.verizon-gni.net (130.81.7.225) 142 ms 11 ms 11 ms
14 so-0-1-0-0.CORE-RTR2.PITT2.verizon-gni.net (130.81.9.22) 19 ms 18 ms 18 ms
15 so-0-0-0-0.CORE-RTR1.PITT2.verizon-gni.net (130.81.8.153) 18 ms 18 ms 18 ms
16 A3-0-0-1710.DSL-RTR1.PITT2.verizon-gni.net (130.81.8.182) 18 ms 18 ms 18 ms
17 pool-141-151-169-121.pitt.east.verizon.net (141.151.169.121) 1292 ms 1088 ms 1216 ms
cst@unix48~%

See, now if all of Verizon's network was slow (that is a traceroute from CMU), I would give them another day before whining. But, no. Incoming traceroute is only slow at the last hop, outgoing it slow at the first. They need to stop blaming it on the whole "the northeast US is currently experiencing slowdowns".

The fact that it is intermittent makes it EXTREMELY difficult to reproduce when talking to support.
 
Back
Top