jsanders
join:2008-03-16
Yonkers, NY | [trouble] 914 dsl down again i hate verizon.
hopefully moving soon and then i'll have cable
worse than dial-up again | |
|
 |
|
Pathfinder
Dazed Confused
Premium
join:2000-03-26
Mount Vernon, NY | 
I was just about to post here. I am way too tired to call tech support. | |
|
 | 
BriGuy89
Let's Go Orange
join:2001-05-08
Yorktown Heights, NY
 ·Verizon Online DSL
| Re: [trouble] 914 dsl down again You need to call.
If not enough people call, VZ perceives it to be a bunch of separate incidents rather than a broader outbound Internet issue that needs to be examined in that broader context.
Only after hundreds called -- and a day and a half had passed -- did VZ acknowledge the last 914 performance-related "outage" a few weeks back. | |
|
| | |
BriGuy89
Let's Go Orange
join:2001-05-08
Yorktown Heights, NY |  | |
|
Fed_Up_In_914
@verizon.net
| Verizon is back at it again. Denying the problem and blaming the customer. Tech named Neil was going to give me an ADDRESS I could WRITE to to complain, no phone number is available from a communications company.
I'm no fan of cable but they're not leaving me much choice.
So, no work accomplished today. | |
|
| |
|
Bad914
@verizon.net | Re: 914 dsl down again Tarrytown Complaints:
Verizon President's Help Line
800-483-7988 | |
|
| |
|
SloJoe914
@verizon.net
1 edit | Re: 914 dsl down again Tarrytown
212-395-1060 is the number for the CEO's office.
212-719-3349 is the fax number for the CEO's office.
212-321-8700 is Verizon Executive Customer Service.
ivan.g.seidenberg@verizon.com is the CEO's email address. | |
|
Pathfinder
Dazed Confused
Premium
join:2000-03-26
Mount Vernon, NY
·Verizon Online DSL
1 edit | On the phone now with Robbie. Of course he shows I am getting over 3000kbps so naturally the problem is in my PC.
Ok "Robbie" came back and said that he is showing an outage in 914 but not a lot of people have called and I am the first from 914-668 (Mount Vernon).
He wasn't convinced until I ran a speedtest from my other PC then he acknowledged that both PC probably weren't bad. | |
|
|
Leakywart
@verizon.net | Re: [trouble] 914 dsl down again 845 area down to less then dial-up.Started at around 8-9pm last nite.
This is just like when that transponder( or whatever) when out in White plains. | |
|
|
altermatt
Premium
join:2004-01-22
White Plains, NY
·Verizon Online DSL
| Glad I didn't start this thread  . Yup, down to a crawl download, normal upload.
After all these years, and being an active Verizon DSL evangelist, I'm ready to jump ship. This is ridiculous.
Again, Verizon, it ain't just the slowdowns (which are getting habitual suddenly), it's your REFUSAL to admit them, and insistance that all of a sudden, tons of users are having the same exact trouble because of THEIR own computers.
Clearly, you've taught even your most faithful users that YOU can't hear US now.
--
The truth of a thing is the feel of it, not the think of it. -- Stanley Kubrick | |
|
|
Pathfinder
Dazed Confused
Premium
join:2000-03-26
Mount Vernon, NY
·Verizon Online DSL
| Re: [trouble] 914 dsl down again I'm not quite ready to jump ship just yet. But then again my alternative is Time Warner with its pathetic 368 upload. But I am getting miffed. 6 years with no issues and then twice in 3 weeks.
And as you said, their failure to acknowledge it is even more frustrating. "Robbie" insisted that there was no network problem until I got a little short with him then he checked another database and saw it. The internal reporting and monitoring leaves a lot to be desired.
Right now I am trying to check System Status to see if they listed it but I can't get to dslstart.verizon.net | |
|
BriGuy89
Let's Go Orange
join:2001-05-08
Yorktown Heights, NY
·Verizon Online DSL
| The Verizon CO team (not your local CO to which your line connects) that has responsibility for monitoring downstream Internet throughput has a cavalier attutude to say the least. They won't acknowledge or even consider the possibility of being at fault until the CSR and local field tech have eliminated all the posiibilities from their end.
Performance issues (without complete device failures) is clearly this team Achilles' Heel.
And VZ provides no mechanism by which people can directly report a common set of symptoms across multiple users and geographies for examination and correlation by someone.
The lack of acknowledgement of a VZ problem is equally disturbing. Clearly VZ internal processes and reward systems are not aligned with providing customers with accurate information and speeding service restoration.
For the first time in 8+ years with VZ DSL, I am going to start considering alternatives. CAN YOU HEAR ME NOW? | |
|
FFS
@verizon.net
| dsl still sucks in 845 area code..
WTF is going on?
"babu" said it was my pc,I ripped him a new one,and we somehow got d/c'd.
I understand nothing in life is perfect,but a little accountability would be nice.
Hey verizon,spend less money on the 4 eyed geek commercials and more communications to your techs in India.
Can you hear us now holio? | |
|
BiteMe
@verizon.net | 
hear me now?
Its hard to believe that the businesses in the 914/845 area code are tolerating #'s like this. | |
|
BriGuy89
Let's Go Orange
join:2001-05-08
Yorktown Heights, NY
·Verizon Online DSL
| In case this helps anyone...
Tracing route to www.verizon.net [206.46.232.39] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms dslrouter [192.168.1.1]
2 53 ms 59 ms 60 ms 10.32.66.1
3 34 ms 34 ms 49 ms so-4-1-3-0.CORE-RTR1.NY325.verizon-gni.net [130.81.13.105]
4 62 ms * 61 ms 130.81.20.176
5 54 ms 69 ms 65 ms 130.81.19.111
6 51 ms 61 ms 57 ms so-7-0-0-0.BB-RTR2.RES.verizon-gni.net [130.81.19.51]
7 112 ms 97 ms 78 ms 130.81.19.78
8 80 ms 88 ms 108 ms so-1-0-0-0.CORE-RTR1.DFW03.verizon-gni.net [130.81.20.157]
9 97 ms 90 ms 99 ms po1.ctn-border1.vzlink.com [206.46.225.85]
10 * 110 ms 70 ms po121.ctn-core1.vzlink.com [206.46.225.18]
11 115 ms 94 ms 96 ms 206.46.229.17
12 * 120 ms 106 ms 206.46.232.39
Trace complete. | |
|
Smith6612
Premium
join:2008-02-01
united state | It's a CO problem without a doubt if you aren't downloading anything while running the trace route on FastPath. If you ran that while on Interleaved with no downloads, it still shows some conjestion. | |
|
|
BriGuy89
Let's Go Orange
join:2001-05-08
Yorktown Heights, NY
·Verizon Online DSL
| Re: [trouble] 914 dsl down again said by Smith6612  :It's a CO problem without a doubt if you aren't downloading anything while running the trace route on FastPath. Thanks.
To clarify -- no downloading over any protocol was going on during the traceroute (not even an open browser). | |
|
BriGuy89
Let's Go Orange
join:2001-05-08
Yorktown Heights, NY
·Verizon Online DSL
| For more comparisons -- hopefully will help others
I ran these tests as well; I'm putting them out here in case someone needs/wants to use them as a benchmark against their similar issues (or lack of issues  )
Tests from www.speedtest.net (to its closest speed test server, in NYC, less than 50 miles away from me):
175 kbps down / 697 kbps up / 085 ms latency (4/3/08 10:15)
337 kbps down / 682 kbps up / 058 ms latency (4/3/08 10:28)
380 kbps down / 699 kbps up / 117 ms latency (4/3/08 11:13)
435 kbps down / 713 kbps up / 103 ms latency (4/3/08 16:53)
C:\>ping www.verizon.net -n 10
Test 1
Pinging www.verizon.net [206.46.232.39] with 32 bytes of data:
Reply from 206.46.232.39: bytes=32 time=116ms TTL=247
Reply from 206.46.232.39: bytes=32 time=83ms TTL=247
Reply from 206.46.232.39: bytes=32 time=116ms TTL=247
Reply from 206.46.232.39: bytes=32 time=110ms TTL=247
Reply from 206.46.232.39: bytes=32 time=64ms TTL=247
Request timed out.
Request timed out.
Request timed out.
Reply from 206.46.232.39: bytes=32 time=68ms TTL=247
Reply from 206.46.232.39: bytes=32 time=99ms TTL=247
Ping statistics for 206.46.232.39:
Packets: Sent = 10, Received = 7, Lost = 3 (30% loss)
Approximate round trip times in milli-seconds:
Minimum = 64ms, Maximum = 116ms, Average = 93ms
Test 2
Pinging www.verizon.net [206.46.232.39] with 32 bytes of data:
Reply from 206.46.232.39: bytes=32 time=121ms TTL=247
Reply from 206.46.232.39: bytes=32 time=100ms TTL=247
Reply from 206.46.232.39: bytes=32 time=87ms TTL=247
Reply from 206.46.232.39: bytes=32 time=111ms TTL=247
Reply from 206.46.232.39: bytes=32 time=97ms TTL=247
Reply from 206.46.232.39: bytes=32 time=115ms TTL=247
Reply from 206.46.232.39: bytes=32 time=120ms TTL=247
Request timed out.
Reply from 206.46.232.39: bytes=32 time=96ms TTL=247
Reply from 206.46.232.39: bytes=32 time=112ms TTL=247
Ping statistics for 206.46.232.39:
Packets: Sent = 10, Received = 9, Lost = 1 (10% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 121ms, Average = 106ms | |
|
BriGuy89
Let's Go Orange
join:2001-05-08
Yorktown Heights, NY
·Verizon Online DSL
| Still not an acknowledged issue. Whatever the magic complaint number threshhold is, it has not been crossed.
If you are facing the same performance issues described in this thread, and have not already done so, please log a ticket with VZ -- reaching that critical mass point seems to be the only way to get this matter considered as a broader network performance problem and have it not be treated as a whole lot of people in different areas experiencing the same exact symptoms and problems that started at the same exact time.
If things stay as they are (continued denial of a broader network performance problem), VZ is going to waste a lot of $ sending out an army of technicians to many individuals over the next few days. | |
|
BriGuy89
Let's Go Orange
join:2001-05-08
Yorktown Heights, NY | Still severely compromised; I'm giving up for the night at this point
Good luck to all similarly affected DSL users. | |
|
no_name
@verizon.net
| Try calling the "premium" support at 1.877.718.6716 and complaining as well.
They don't want to be rude and hang up on you - and are "fearful" of being "monitored" so they want to provide excellent service...
I spent 3 hrs on phone today with Tier1, starting at 10:30 am, before sent to Tier2 for escalation, and it still is not shown as issue on System Status page. | |
|
|
altermatt
Premium
join:2004-01-22
White Plains, NY
·Verizon Online DSL
| Re: [trouble] 914 dsl down again said by no_name :
Try calling the "premium" support They are EXTREMELY helpful, but you can only use premium support if you have paid for it. Otherwise you will be given the option to purchase it, or be connected back to regular tech support.
That said, the person I spoke with CONFIRMED that there is an outage in 914 and 845---guess when it was posted??? 7:30 tonite---literally a few minutes ago!!! All these phone calls all day, and they just ignored them til now.
But now that it is in the system, the engineers are working on it.
I stressed to her that this stonewalling of customers and ignoring calls that say there are posts in the forum does NOT help Verizon, but hurts them. Many of us, again, are angry not so much about the outage (although three in three weeks is too much), but about them ignoring it for so long!
But hang in there; they DO know about.
--
The truth of a thing is the feel of it, not the think of it. -- Stanley Kubrick | |
|
| | raresticks
join:2007-07-31
White Plains, NY
2 edits | Re: [trouble] 914 dsl down again triplicate post | |
|
| | |
| | raresticks
join:2007-07-31
White Plains, NY
| Alter -
I called this in on 4/2 at approximately 9:00PM EDT.
Appears exactly as the 3/16-3/18 train wreck. They did open a ticket and said it was escalated to a 'supervisor'.
Somehow I knew 24hrs. later they would still be down and in denial...
Now the rep I spoke to says it looks like a piece of equipment needs to be replaced....914 and 845 impacted. | |
|
| | | smanjanath
join:2001-12-20
Tarrytown, NY
| Re: [trouble] 914 dsl down again Still down in Tarrytown... I haven't seen dnload speeds like this since I was on dialup. 2 different speed tests with 48K download to almost 400K upload.
Calling tech support is no use as they make you jump thru hoops to tell you the problem in on your pc.
I hope it's fixed soon! | |
|
Fed_Up_In_914
@verizon.net | Thanks to all who have posted... very frustrated and have contacted all the VZ reps I can (also called the Journal News reporter again). VZ really needs to get this right and give the customer correct & current information instead of blame. | |
|
Pathfinder
Dazed Confused
Premium
join:2000-03-26
Mount Vernon, NY
·Verizon Online DSL
| Amazingly enough, it hasn't hit the status page yet.
I am really amazed that with monitoring equipment they aren't able to see this type of outage before 100 customers have to call in. I am also amazed at the fact that a problem like this can't be resolved with a reroute. | |
|
|
altermatt
Premium
join:2004-01-22
White Plains, NY
·Verizon Online DSL
| Re: [trouble] 914 dsl down again said by Pathfinder :Amazingly enough, it hasn't hit the status page yet. I am really amazed that...they aren't able to see this type of outage before 100 customers have to call in. Yup, we always said Verizon was amazing  !
Anyone else notice that all three times this same thing has happened in the last few weeks, the amount of spam also increased?
--
The truth of a thing is the feel of it, not the think of it. -- Stanley Kubrick | |
|
| |
Pathfinder
Dazed Confused
Premium
join:2000-03-26
Mount Vernon, NY | Re: [trouble] 914 dsl down again I haven't noticed any increase in SPAM. | |
|
|
BriGuy89
Let's Go Orange
join:2001-05-08
Yorktown Heights, NY
·Verizon Online DSL
| said by Pathfinder :I am really amazed that with monitoring equipment they aren't able to see this type of outage before 100 customers have to call in. History shows that outbound Internet performance problems are the Achilles' Heel of the VZ CO team in this area. I know of five instances in the last eight years that this exact performance-related problem has occurred, and the pattern is exactly the same: deny it is a network issue; refuse to correlate trouble tickets to see if a broader problem pattern exists; dispatch a technician to eliminate the user, line, and local CO as a potential source of the problem; eventually admit that an outbound Internet router was severely compromised but not completely fried, so it got missed as a problem by VZ monitoring systems. (Admittedly, many automated management systems have a very difficult time accurately and quickly picking up performance-related problems in compromised but not failed devices, such as routers.)
Clearly, this team lacks the tools to automatically identify this kind of performance problem. They likely lack the capital ($ and/or political) to make significantly improving the ability to identify this type of problem a priority. I sincerely hope that it is not that this CO team lacks perspective and has not learned from history.
But I also grudgingly admit this probably isn't the last time this type of problem will happen. | |
|
jsanders
join:2008-03-16
Yonkers, NY | at 11:40 speed returned to normal...but for how long??? | |
|
|
| (topic locked) |
|
) problem.
