batsonaMaryland
join:2004-04-17
Ellicott City, MD Reviews:
 ·Vonage
 ·Verizon FiOS
| reply to mikev
Re: DC area internet issues There's a DNS benchmark utility that will examine the speed of lookups and time-to-reach (ping times).. I think it's called "DNSBench" maybe? Your computer can only display content as fast as DNS can find IPs for the hostnames.. If you happen to be using a cruddy DNS server, you can have 1,000,000/1,000,000 FiOS service, and it will still suck.... |
|
|
|
| reply to mikev
It's getting worse!
Ugghh. |
|
mikevPremium
join:2002-05-04
Northern VA Reviews:
·Callcentric
| reply to mikev
VZ speed test results | 
smokeping as of 10:24p EST |
Try doing a few traceroutes and see if that might show where the problem lies for you. |
|
| reply to mikev
Seems to be okay here too, again. My smokeping showed some squirrelly behavior yesterday evening from the KS server, and one crazy bounce from the CA server (NY was down), and ping times are reasonable for the distances.
dw |
|
| reply to Rain7249
I'm having similar issues since Friday in Bucks County (outside Philadelphia). Have 20/5 service and typically get 25/5 in tests. Recent Speakeasy test results have been 25/.05. Not sure what is causing problems with the upload speed. Have ticket open with Verizon support since Sunday evening. |
|
2 edits | reply to mikev
After calling Verizon twice, a tech coming out once to "replace our router", and Verizon calling us a few times today to check if they had fixed it claiming that their technicians see nothing wrong on their end, they are sending a "Network Technician" out to our house this Wednesday to get to the root problem of our slow-as-molasses upload speeds.
Verizon has been perfect for the 5-6 year's we've had it; I'm surprised it is this hard to diagnose and fix problem.
Edit (2-27-13 @ 4:33PM): Verizon Tech just left my house. The "network technician" they sent out turned out to be a standard on-site tech; nothing special. He got on the phone with support and ran through the checklist of things to try, including switching out our 5-year old ONT. Obviously this didn't fix anything, the problem is in there network somewhere. Finally they bumped the ticket up to tier 2 support. Within minutes T2 came back and said that the problem was a faulty "LM card" on their end. They said they would have it fixed within 12 hours. Hopefully they are right! |
|
