 zenafu
join:2007-06-12 Brooklyn, NY | reply to xp8 Re: Slow Speeds in NYC
So far it looks like mostly Bensonhurst, Bay Ridge and parts of Long Island. Let's hope a fix is in the works. |
|
  Odaeus
join:2008-09-27 Brooklyn, NY
·Verizon Online DSL
| Just called Verizon up, they ran several line tests, saying things are all green, that I should be receiving 3.3Mbps DL. [Not the case on my end =P]
The guy thinks it's my out of date router; might be acting up. [Have 1st or 2nd edition white westell modem :P lol] Thing has been good for over 5 years+
Anyways, had them check out my friend's phone line, 13th ave area, saying he's good also, but we're both getting around 600-700 kbps. Meh. |
|
 Maze
join:2006-02-02 Brooklyn, NY
4 edits | said by Odaeus :said by Maze :I'm in bensonhurst 11214 and all is cool here at 8:18 pm. Verizon rocks in the speed here. Heh, so close yet so far away =P. Just ran a test at speedtest.net, getting No clue what's going on, going to call them soon =P said by zenafu :So far it looks like mostly Bensonhurst, Bay Ridge and parts of Long Island. Let's hope a fix is in the works. said by Bakun3 :
I'm also in the Bensonhurst 11214 part of Brooklyn and I've never had any slow-downs since I switched over to DSL 2 years ago. I dont know what's going on today but my downstream is at around 700kbps as opposed to the 2900kbps as always.
Anyone have any ideas as to what's causing this? That is odd we are though serviced out of same CO in 11214? 71street 16th AVE? It may be your router actually. Because if we are in the same area. We should be having same localized problems. Maybe my logic is flawed here. Something else is going on for you(s).
Those that have issue state clearly zip codes. Because i'm thinking "in general" it may be 11204 Bensonhurst. Which not sure uses same CO. |
|
  flatline_
join:2003-01-18
| I'm in the 11213 area. According to this tracert, latency seems to shoot up at the 4th hop. Under normal circumstances, I wouldn't see any pings here over 10ms throughout the entire trace. Maybe something is related:
Tracing route to nyc.speakeasy.net [216.254.95.2] over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1 2 7 ms 7 ms 6 ms 10.32.*.* 3 7 ms 8 ms 7 ms P12-0-0.LCR-04.NYCMNY.verizon-gni.net [130.81.44 .252] 4 68 ms 70 ms 70 ms so-6-0-0-0.PEER-RTR1.NY111.verizon-gni.net [130. 81.17.129] 5 62 ms 73 ms 64 ms so-0-3-1.mpr2.lga5.us.above.net [64.125.13.33] 6 71 ms 72 ms 71 ms xe-1-1-0.er2.lga5.us.above.net [64.125.26.166] 7 71 ms 65 ms 60 ms 208.184.48.181.speakeasy.net [208.184.48.181] 8 72 ms 70 ms 72 ms dns.nyc1.speakeasy.net [216.254.95.2]
Trace complete.
As of right now, my speeds are actually normal again. Seems like this is just a good old fashioned case of peak hour saturation.  |
|
  Odaeus
join:2008-09-27 Brooklyn, NY | Same, speeds are somewhat back to normal. It's 2am. 4PM-12AM was 600-900 kbps.
Now it's
Go figure. |
|
  Smith6612 Premium join:2008-02-01 united state | reply to flatline_ High ping is always related to slow speeds. Since that 4th hop is probably the main backbone for your area, that's your answer to the slow speeds. |
|
  user_11204
@verizon.net
| reply to Odaeus it's the peek hour thing. The last time (few months ago) it took 2 weeks to get back. Thanks to the guys at the support forum here actually. But still it's not believable that they don't know and they need us to tell them or the verizon people here telling them as well. It's not like a single line is down: it's an entire region!
now it's always the same story: I call and somebody from India tells me that everything looks fine (from India maybe). Then I call again and I have to run all the useless tests. Then I post on the support forum and again all the tests. To finally get that they are aware of the problem and they are working on it.
Amateurs act like that. Actually not even amateurs act like that: only Verizon DSL acts like that.
If I do something like that I'd be out of business in no time. |
|
  flatline_
join:2003-01-18
| reply to Smith6612 The thing is, though, the latency remains exactly the same despite the time of day - that's what's kind of puzzling. The speed, however, fluctuates. Right now I'm testing at 2800/714 with ~65ms to hop #4. Earlier, I was as low as 400/650, still pinging ~65ms to hop #4  |
|