It started being slow a couple days ago. I was wondering whether it was on my end or Verizon's.
I ran a Tracert to Verizon.net and pasted the results into a document, if that's needed.
Any ideas? Thanks in advance.
08-21-2011 03:56 PM - edited 08-21-2011 03:58 PM
I've also been seeing slowdowns for the 2 days (Bergen County).
Yesterday morning it was fine:
2011-08-20 08:05:04 (3.50 MB/s) - `/dev/null' saved [10485760/10485760]
During the day it was awful
2011-08-20 15:05:27 (387 KB/s) - `/dev/null' saved [10485760/10485760]
Overnight it got better
2011-08-21 02:50:04 (3.52 MB/s) - `/dev/null' saved [10485760/10485760]
This morning (starting 10am) it went bad again
2011-08-21 15:50:54 (194 KB/s) - `/dev/null' saved [10485760/10485760]
Currently 2011-08-21 18:51:10 (149 KB/s) - `/dev/null' saved [10485760/10485760] That's slower than DSL!
It looks like the problem may be on the Verizon backbone.
I stuck a 10Mbyte file on my server in Fremont, CA
Attempting to download it via wget:
2% [ ] 260,369 27.5K/s eta 6m 20s
Let's give up on that. Heh, let's try via IPv6
100%[======================================>] 10,485,760 2.99M/s in 4.0s
I am also experiencing slow downloads here in Jersey City NJ. There are now many reports in DSLReports on this issue and is apparently not being acknowledged by Verizon tech support. Hopefully we can get some traction here.
I'm also getting slow speeds and a traceroute to www.google.com or other sites show drops starting at what appears to be a newark router on the FiOS network.
What the hell is Verizon doing about this? They should be troubleshooting this and fixing it rather than trying to say there's no issue. I've rebooted all my routers and downstream network devices from the ONT and I still have the issue. Nothing has changed otherwise config wise on my side.
Has anyone called and complained to Verizon?
The issue is within the Verizon network as several customers I talked to are dropping packets causing the slow downs. Tech support is barely reachable and is blaming the weather with a resolution time of 02:45pm, August 22, 2011 for this problem.