(Shamelessly borrowing a title from an earlier post...)
As I write this, I have 2 command windows open constantly pinging 2 web sites... and about 50% of the pings are timing out. In fact, just trying to write this post has been an ordeal with the browser timing out! Note that I am even using a long timeout as well - 10 seconds. For those who care, most of the response times are in the 40ms range, with the periodic outlier closer to 100ms... besides of course the timeouts. It's like the packets are just gone.
Has anyone else had these symptoms? If you are not checking pings, maybe your browser sometimes fails to load pages or require a second click of that link to actually get to the destination?
I have been through the normal tech support questions and line tests... all were fine. This seems to be a network problem. I have 2 PCs and a few other Internet capable devices here on my router that all have the same issues. It's an old Westell 7500, and yes, the problem still occurs when directly connected. Additionally, I have heard the same complaints from friends in different parts of the area... not connected to my Central Office.
This problem makes it hard to do VOIP-like things, VPN-like things, and my telnet/ftp/ssh connections are not happy with the spotty service. I can watch my IM client periodically re-connect when the losses are especially long...
I seem to be having these issues pretty much throughout the day. I *know* that I have seen them in the mornings and in the evenings... and I interpret my wife's complaints about some websites not loading as the same thing during the day.
What sorts of things can I run and test to help pin-point what I think is a network issue? Any ideas out there? Keep in mind that during all this time, the DSL modem says that everything is just fine...
If you have your router set up to respond to ICMP data, try the Line Quality test at DSLReports:http://www.dslreports.com/pingtest
You could even consider running their Smokeping as well in the Tools section which might help with finding a time-of-day related issue. This does sound like a network issue though and could be just due to faulty equipment if data is lost just like *that*
I'm having similar issues in the Southeastern PA area. I regularly have been running ongoing pings to google and Broadbandreports at the same time. While it's good, they're at 22-35ms but you can watch them climb as the problem comes in. Here's a snip from last night (6/2/12) to Yahoo.
Snippets of ping times to yahoo:
Reply from 98.139.183.24: bytes=32 time=55ms TTL=50
Reply from 98.139.183.24: bytes=32 time=55ms TTL=49
Reply from 98.139.183.24: bytes=32 time=72ms TTL=50
Reply from 98.139.183.24: bytes=32 time=76ms TTL=50
Reply from 98.139.183.24: bytes=32 time=66ms TTL=50
Reply from 98.139.183.24: bytes=32 time=52ms TTL=49
Reply from 98.139.183.24: bytes=32 time=94ms TTL=49
Reply from 98.139.183.24: bytes=32 time=137ms TTL=49
Reply from 98.139.183.24: bytes=32 time=40ms TTL=49
Reply from 98.139.183.24: bytes=32 time=420ms TTL=49
Reply from 98.139.183.24: bytes=32 time=973ms TTL=49
Reply from 98.139.183.24: bytes=32 time=1410ms TTL=49
Reply from 98.139.183.24: bytes=32 time=1995ms TTL=50
Reply from 98.139.183.24: bytes=32 time=3076ms TTL=49
Reply from 98.139.183.24: bytes=32 time=2058ms TTL=50
Reply from 98.139.183.24: bytes=32 time=114ms TTL=49
Reply from 98.139.183.24: bytes=32 time=54ms TTL=50
Reply from 98.139.183.24: bytes=32 time=55ms TTL=50
Reply from 98.139.183.24: bytes=32 time=43ms TTL=49
Reply from 98.139.183.24: bytes=32 time=68ms TTL=50
Reply from 98.139.183.24: bytes=32 time=141ms TTL=50
Reply from 98.139.183.24: bytes=32 time=69ms TTL=49
Reply from 98.139.183.24: bytes=32 time=52ms TTL=50
Reply from 98.139.183.24: bytes=32 time=56ms TTL=50
Reply from 98.139.183.24: bytes=32 time=309ms TTL=50
Start a new topic or ask questions in the open forum.
