But a continuous ping is not an acceptable test or proof as I have for years set ping responses to the last thing to take care of in my embedded systems. All other traffic has priority so it's proper for ping to fail. It is not proof the connection has dropped.
Even with that out of the way, you did the usual and it's up to the ISP to fix this.
Bob
My wired RR internet connection drops aboout 2-4 minutes several times an hour. I've:
had 4 techs out , they say the signal/noise is perfect
swapped the cable modem,
tried another router,
connected without a router,
reconfigged router,
removed everything from the LAN except 1 system
tried alternate computers
called RR like 5 times
published it on DSL reports
sent ping logs to RR national help desk
..and nothing helps at all.
Here is a typical ping -t , dropped in the middleto google from today. It does this 24 x 7 and no one has been able to assist. I'm not doing anything on my net while this is happening except pinging google:
Reply from 173.194.37.4: bytes=32 time=37ms TTL=50
Reply from 173.194.37.4: bytes=32 time=36ms TTL=50
Reply from 173.194.37.4: bytes=32 time=35ms TTL=50
Reply from 173.194.37.4: bytes=32 time=34ms TTL=50
Reply from 173.194.37.4: bytes=32 time=33ms TTL=50
Reply from 173.194.37.4: bytes=32 time=32ms TTL=50
Reply from 173.194.37.4: bytes=32 time=31ms TTL=50
Reply from 173.194.37.4: bytes=32 time=40ms TTL=50
Reply from 173.194.37.4: bytes=32 time=39ms TTL=50
Reply from 173.194.37.4: bytes=32 time=38ms TTL=50
Reply from 173.194.37.4: bytes=32 time=47ms TTL=50
Reply from 173.194.37.4: bytes=32 time=36ms TTL=50
Reply from 173.194.37.4: bytes=32 time=35ms TTL=50
Reply from 173.194.37.4: bytes=32 time=34ms TTL=50
Reply from 173.194.37.4: bytes=32 time=33ms TTL=50
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 50.89.224.136: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 50.89.224.136: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 50.89.224.136: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 50.89.224.136: Destination host unreachable.
Request timed out.
Request timed out.
Request timed out.
Reply from 50.89.224.136: Destination host unreachable.
Request timed out.
Request timed out.
Reply from 173.194.37.4: bytes=32 time=31ms TTL=50
Reply from 173.194.37.4: bytes=32 time=30ms TTL=50
Reply from 173.194.37.4: bytes=32 time=37ms TTL=50
Reply from 173.194.37.4: bytes=32 time=37ms TTL=50
Reply from 173.194.37.4: bytes=32 time=35ms TTL=50
Reply from 173.194.37.4: bytes=32 time=34ms TTL=50
Reply from 173.194.37.4: bytes=32 time=33ms TTL=50
Reply from 173.194.37.4: bytes=32 time=31ms TTL=50
Reply from 173.194.37.4: bytes=32 time=50ms TTL=50
Reply from 173.194.37.4: bytes=32 time=32ms TTL=50
Reply from 173.194.37.4: bytes=32 time=31ms TTL=50
Reply from 173.194.37.4: bytes=32 time=29ms TTL=50

Chowhound
Comic Vine
GameFAQs
GameSpot
Giant Bomb
TechRepublic