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 |
|
blave
join:2008-03-15
| Same here... exact symptoms from this thread:
»Anyone else in NY area seeing problems?
and my speedtest.net from tonight is reporting:
 |
|
BriGuy89
Let's Go Orange
join:2001-05-08
Yorktown Heights, NY
 ·Verizon Online DSL
| reply to jsanders
Same problems here in the northern end of 914. Downstream performance dropped gradually somewhere after 8 pm, and fell off the map to sub-dialup levels around 10 pm.
Ugh!
Logged my call to tech support and they grudingly admitted there might be a network (or should I say "notwork"?  ) problem.
Went through the whole song and dance with tech support. Said this one smelled exactly like the last major outage. Asked to correlate support calls aginst CO served, Internet router, local exchange served, etc. and the rep said that those tools don't exist at his level. He must escalate to the Wizard of CO and wait for a response to his plea for help.
And just like the famous movie, the initial answer from the wizard is the same: "Come back tomorrow!" 
I also asked for a qualification/certification test to have to avoid future hoop jumping because I know the drill and do all this stuff anyway before ever making the support call. He laughed. I said I was serious. He said that'll probably never happen.
Just waiting...  |
|
Pathfinder
Dazed Confused
Premium
join:2000-03-26
Mount Vernon, NY | reply to jsanders
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
| 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 | reply to jsanders
 |
|
Fed_Up_In_914
@verizon.net
| reply to jsanders
Re: 914 dsl down again Tarrytown
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. |
|
Pathfinder
Dazed Confused
Premium
join:2000-03-26
Mount Vernon, NY
·Verizon Online DSL
1 edit | reply to jsanders
Re: [trouble] 914 dsl down again
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 | 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. |
|
Out Again
@verizon.net
| reply to jsanders
Congratulations! |
 |
|
altermatt
Premium
join:2004-01-22
White Plains, NY
·Verizon Online DSL
| reply to jsanders
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
| 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
| reply to jsanders
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
| reply to jsanders
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 | reply to jsanders
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
| reply to jsanders
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 | reply to jsanders
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
| 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
| reply to jsanders
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
| reply to jsanders
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. |
|
