Guest kamil234 Posted October 22, 2006 CID Share Posted October 22, 2006 Pinging www.google.com [216.239.37.104] with 32 bytes of data: Reply from 216.239.37.104: bytes=32 time=32ms TTL=244 Reply from 216.239.37.104: bytes=32 time=22ms TTL=244 Reply from 216.239.37.104: bytes=32 time=19ms TTL=244 Reply from 216.239.37.104: bytes=32 time=17ms TTL=244 Reply from 216.239.37.104: bytes=32 time=28ms TTL=244 Reply from 216.239.37.104: bytes=32 time=24ms TTL=244 Reply from 216.239.37.104: bytes=32 time=31ms TTL=244 Reply from 216.239.37.104: bytes=32 time=20ms TTL=244 Reply from 216.239.37.104: bytes=32 time=46ms TTL=244 Reply from 216.239.37.104: bytes=32 time=27ms TTL=244 Reply from 216.239.37.104: bytes=32 time=17ms TTL=244 Reply from 216.239.37.104: bytes=32 time=31ms TTL=244 Reply from 216.239.37.104: bytes=32 time=17ms TTL=244 Reply from 216.239.37.104: bytes=32 time=16ms TTL=244 Reply from 216.239.37.104: bytes=32 time=17ms TTL=244 Reply from 216.239.37.104: bytes=32 time=16ms TTL=244 Reply from 216.239.37.104: bytes=32 time=17ms TTL=244 Reply from 216.239.37.104: bytes=32 time=16ms TTL=244 Reply from 216.239.37.104: bytes=32 time=19ms TTL=244 Reply from 216.239.37.104: bytes=32 time=17ms TTL=244 Reply from 216.239.37.104: bytes=32 time=18ms TTL=244 Request timed out. Reply from 216.239.37.104: bytes=32 time=115ms TTL=244 Reply from 216.239.37.104: bytes=32 time=17ms TTL=244 Reply from 216.239.37.104: bytes=32 time=117ms TTL=244 Reply from 216.239.37.104: bytes=32 time=16ms TTL=244 Reply from 216.239.37.104: bytes=32 time=40ms TTL=244 Reply from 216.239.37.104: bytes=32 time=45ms TTL=244 Reply from 216.239.37.104: bytes=32 time=138ms TTL=244 Reply from 216.239.37.104: bytes=32 time=55ms TTL=244 Reply from 216.239.37.104: bytes=32 time=22ms TTL=244 Reply from 216.239.37.104: bytes=32 time=21ms TTL=244 Reply from 216.239.37.104: bytes=32 time=84ms TTL=244 Reply from 216.239.37.104: bytes=32 time=82ms TTL=244 Reply from 216.239.37.104: bytes=32 time=21ms TTL=244 Reply from 216.239.37.104: bytes=32 time=21ms TTL=244 Reply from 216.239.37.104: bytes=32 time=44ms TTL=244 Reply from 216.239.37.104: bytes=32 time=36ms TTL=244 Reply from 216.239.37.104: bytes=32 time=47ms TTL=244 Reply from 216.239.37.104: bytes=32 time=47ms TTL=244 Reply from 216.239.37.104: bytes=32 time=52ms TTL=244 Reply from 216.239.37.104: bytes=32 time=16ms TTL=244 Reply from 216.239.37.104: bytes=32 time=35ms TTL=244 Reply from 216.239.37.104: bytes=32 time=16ms TTL=244 Reply from 216.239.37.104: bytes=32 time=51ms TTL=244 Reply from 216.239.37.104: bytes=32 time=65ms TTL=244 Reply from 216.239.37.104: bytes=32 time=23ms TTL=244 Reply from 216.239.37.104: bytes=32 time=106ms TTL=244 Reply from 216.239.37.104: bytes=32 time=19ms TTL=244 Reply from 216.239.37.104: bytes=32 time=15ms TTL=244 Reply from 216.239.37.104: bytes=32 time=45ms TTL=244 Reply from 216.239.37.104: bytes=32 time=60ms TTL=244 Reply from 216.239.37.104: bytes=32 time=22ms TTL=244 Reply from 216.239.37.104: bytes=32 time=42ms TTL=244 Reply from 216.239.37.104: bytes=32 time=20ms TTL=244 Reply from 216.239.37.104: bytes=32 time=103ms TTL=244 Reply from 216.239.37.104: bytes=32 time=33ms TTL=244 Reply from 216.239.37.104: bytes=32 time=18ms TTL=244 Reply from 216.239.37.104: bytes=32 time=19ms TTL=244 Reply from 216.239.37.104: bytes=32 time=18ms TTL=244 Reply from 216.239.37.104: bytes=32 time=72ms TTL=244 Reply from 216.239.37.104: bytes=32 time=22ms TTL=244 Reply from 216.239.37.104: bytes=32 time=26ms TTL=244 Reply from 216.239.37.104: bytes=32 time=17ms TTL=244 Reply from 216.239.37.104: bytes=32 time=95ms TTL=244 Reply from 216.239.37.104: bytes=32 time=46ms TTL=244 Reply from 216.239.37.104: bytes=32 time=19ms TTL=244 Reply from 216.239.37.104: bytes=32 time=99ms TTL=244 Reply from 216.239.37.104: bytes=32 time=78ms TTL=244 Reply from 216.239.37.104: bytes=32 time=39ms TTL=244 Reply from 216.239.37.104: bytes=32 time=37ms TTL=244 Reply from 216.239.37.104: bytes=32 time=78ms TTL=244 Reply from 216.239.37.104: bytes=32 time=45ms TTL=244 Reply from 216.239.37.104: bytes=32 time=23ms TTL=244 Reply from 216.239.37.104: bytes=32 time=87ms TTL=244 Reply from 216.239.37.104: bytes=32 time=17ms TTL=244 Reply from 216.239.37.104: bytes=32 time=37ms TTL=244 Reply from 216.239.37.104: bytes=32 time=14ms TTL=244 Reply from 216.239.37.104: bytes=32 time=155ms TTL=244 Reply from 216.239.37.104: bytes=32 time=18ms TTL=244 Reply from 216.239.37.104: bytes=32 time=22ms TTL=244 Reply from 216.239.37.104: bytes=32 time=19ms TTL=244 Reply from 216.239.37.104: bytes=32 time=48ms TTL=244 Request timed out. Reply from 216.239.37.104: bytes=32 time=18ms TTL=244 Reply from 216.239.37.104: bytes=32 time=17ms TTL=244 Reply from 216.239.37.104: bytes=32 time=30ms TTL=244 Reply from 216.239.37.104: bytes=32 time=45ms TTL=244 Reply from 216.239.37.104: bytes=32 time=21ms TTL=244 Reply from 216.239.37.104: bytes=32 time=29ms TTL=244 Reply from 216.239.37.104: bytes=32 time=25ms TTL=244 Reply from 216.239.37.104: bytes=32 time=17ms TTL=244 Reply from 216.239.37.104: bytes=32 time=18ms TTL=244 Reply from 216.239.37.104: bytes=32 time=24ms TTL=244 Reply from 216.239.37.104: bytes=32 time=67ms TTL=244 Reply from 216.239.37.104: bytes=32 time=39ms TTL=244 Reply from 216.239.37.104: bytes=32 time=24ms TTL=244 Reply from 216.239.37.104: bytes=32 time=17ms TTL=244 Reply from 216.239.37.104: bytes=32 time=28ms TTL=244 Reply from 216.239.37.104: bytes=32 time=16ms TTL=244 Ping statistics for 216.239.37.104: Packets: Sent = 100, Received = 98, Lost = 2 (2% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 155ms, Average = 38ms im using a NETGEAR MR814 router. any ideas how to get rid of the spikes? also 1/10 of the time when i browse firefox says: connection timed out. my connection is : OOL 15/2 my computer is clean of spyware and viruses. Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/ Share on other sites More sharing options...
dlewis23 Posted October 23, 2006 CID Share Posted October 23, 2006 try doing it with out the router real quick. Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179481 Share on other sites More sharing options...
Guest kamil234 Posted October 23, 2006 CID Share Posted October 23, 2006 Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsHP_Administrator>ping www.google.com -n 100 Pinging www.google.com [216.239.37.104] with 32 bytes of data: Reply from 216.239.37.104: bytes=32 time=33ms TTL=245 Reply from 216.239.37.104: bytes=32 time=46ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=18ms TTL=245 Reply from 216.239.37.104: bytes=32 time=19ms TTL=245 Reply from 216.239.37.104: bytes=32 time=21ms TTL=245 Reply from 216.239.37.104: bytes=32 time=19ms TTL=245 Reply from 216.239.37.104: bytes=32 time=16ms TTL=245 Reply from 216.239.37.104: bytes=32 time=28ms TTL=245 Reply from 216.239.37.104: bytes=32 time=23ms TTL=245 Reply from 216.239.37.104: bytes=32 time=20ms TTL=245 Reply from 216.239.37.104: bytes=32 time=18ms TTL=245 Reply from 216.239.37.104: bytes=32 time=18ms TTL=245 Reply from 216.239.37.104: bytes=32 time=24ms TTL=245 Reply from 216.239.37.104: bytes=32 time=17ms TTL=245 Reply from 216.239.37.104: bytes=32 time=91ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=36ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=14ms TTL=245 Reply from 216.239.37.104: bytes=32 time=65ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=14ms TTL=245 Reply from 216.239.37.104: bytes=32 time=22ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=28ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=16ms TTL=245 Reply from 216.239.37.104: bytes=32 time=14ms TTL=245 Reply from 216.239.37.104: bytes=32 time=17ms TTL=245 Reply from 216.239.37.104: bytes=32 time=17ms TTL=245 Reply from 216.239.37.104: bytes=32 time=19ms TTL=245 Reply from 216.239.37.104: bytes=32 time=18ms TTL=245 Reply from 216.239.37.104: bytes=32 time=17ms TTL=245 Reply from 216.239.37.104: bytes=32 time=21ms TTL=245 Reply from 216.239.37.104: bytes=32 time=20ms TTL=245 Reply from 216.239.37.104: bytes=32 time=20ms TTL=245 Reply from 216.239.37.104: bytes=32 time=58ms TTL=245 Reply from 216.239.37.104: bytes=32 time=33ms TTL=245 Reply from 216.239.37.104: bytes=32 time=18ms TTL=245 Reply from 216.239.37.104: bytes=32 time=29ms TTL=245 Reply from 216.239.37.104: bytes=32 time=18ms TTL=245 Reply from 216.239.37.104: bytes=32 time=14ms TTL=245 Reply from 216.239.37.104: bytes=32 time=17ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=16ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=16ms TTL=245 Reply from 216.239.37.104: bytes=32 time=35ms TTL=245 Reply from 216.239.37.104: bytes=32 time=27ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=14ms TTL=245 Reply from 216.239.37.104: bytes=32 time=22ms TTL=245 Reply from 216.239.37.104: bytes=32 time=16ms TTL=245 Reply from 216.239.37.104: bytes=32 time=19ms TTL=245 Reply from 216.239.37.104: bytes=32 time=22ms TTL=245 Reply from 216.239.37.104: bytes=32 time=21ms TTL=245 Reply from 216.239.37.104: bytes=32 time=17ms TTL=245 Reply from 216.239.37.104: bytes=32 time=17ms TTL=245 Reply from 216.239.37.104: bytes=32 time=18ms TTL=245 Reply from 216.239.37.104: bytes=32 time=18ms TTL=245 Reply from 216.239.37.104: bytes=32 time=21ms TTL=245 Reply from 216.239.37.104: bytes=32 time=24ms TTL=245 Reply from 216.239.37.104: bytes=32 time=27ms TTL=245 Reply from 216.239.37.104: bytes=32 time=17ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=16ms TTL=245 Reply from 216.239.37.104: bytes=32 time=19ms TTL=245 Reply from 216.239.37.104: bytes=32 time=38ms TTL=245 Reply from 216.239.37.104: bytes=32 time=14ms TTL=245 Reply from 216.239.37.104: bytes=32 time=20ms TTL=245 Reply from 216.239.37.104: bytes=32 time=16ms TTL=245 Reply from 216.239.37.104: bytes=32 time=27ms TTL=245 Reply from 216.239.37.104: bytes=32 time=26ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=16ms TTL=245 Reply from 216.239.37.104: bytes=32 time=24ms TTL=245 Reply from 216.239.37.104: bytes=32 time=14ms TTL=245 Reply from 216.239.37.104: bytes=32 time=16ms TTL=245 Reply from 216.239.37.104: bytes=32 time=18ms TTL=245 Reply from 216.239.37.104: bytes=32 time=18ms TTL=245 Reply from 216.239.37.104: bytes=32 time=19ms TTL=245 Reply from 216.239.37.104: bytes=32 time=46ms TTL=245 Reply from 216.239.37.104: bytes=32 time=16ms TTL=245 Reply from 216.239.37.104: bytes=32 time=16ms TTL=245 Reply from 216.239.37.104: bytes=32 time=17ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=18ms TTL=245 Reply from 216.239.37.104: bytes=32 time=21ms TTL=245 Reply from 216.239.37.104: bytes=32 time=35ms TTL=245 Reply from 216.239.37.104: bytes=32 time=20ms TTL=245 Reply from 216.239.37.104: bytes=32 time=18ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=17ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Reply from 216.239.37.104: bytes=32 time=15ms TTL=245 Ping statistics for 216.239.37.104: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 14ms, Maximum = 91ms, Average = 21ms Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179483 Share on other sites More sharing options...
dlewis23 Posted October 23, 2006 CID Share Posted October 23, 2006 it looks a little better but the few spikes you did get may be the website. if you ping testmy.net does the same thing happen? Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179484 Share on other sites More sharing options...
ispgeek Posted October 23, 2006 CID Share Posted October 23, 2006 Please do a trace route to google and post the results. Also I need to know your carrier. Thanks! Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179485 Share on other sites More sharing options...
dlewis23 Posted October 23, 2006 CID Share Posted October 23, 2006 Please do a trace route to google and post the results. Also I need to know your carrier. Thanks! he said his connection its OOL 15/2 Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179486 Share on other sites More sharing options...
Guest kamil234 Posted October 23, 2006 CID Share Posted October 23, 2006 it looks a little better but the few spikes you did get may be the website. if you ping testmy.net does the same thing happen? Microsoft Windows XP [Version 5.1.2600] © Copyright 1985-2001 Microsoft Corp. C:Documents and SettingsHP_Administrator>ping www.testmy.net -n 100 Pinging www.testmy.net [67.18.179.85] with 32 bytes of data: Reply from 67.18.179.85: bytes=32 time=78ms TTL=49 Reply from 67.18.179.85: bytes=32 time=57ms TTL=49 Reply from 67.18.179.85: bytes=32 time=55ms TTL=49 Reply from 67.18.179.85: bytes=32 time=189ms TTL=49 Reply from 67.18.179.85: bytes=32 time=57ms TTL=49 Reply from 67.18.179.85: bytes=32 time=65ms TTL=49 Reply from 67.18.179.85: bytes=32 time=69ms TTL=49 Reply from 67.18.179.85: bytes=32 time=88ms TTL=49 Reply from 67.18.179.85: bytes=32 time=55ms TTL=49 Reply from 67.18.179.85: bytes=32 time=68ms TTL=49 Reply from 67.18.179.85: bytes=32 time=59ms TTL=49 Reply from 67.18.179.85: bytes=32 time=71ms TTL=49 Reply from 67.18.179.85: bytes=32 time=75ms TTL=49 Reply from 67.18.179.85: bytes=32 time=62ms TTL=49 Reply from 67.18.179.85: bytes=32 time=68ms TTL=49 Reply from 67.18.179.85: bytes=32 time=66ms TTL=49 Reply from 67.18.179.85: bytes=32 time=59ms TTL=49 Reply from 67.18.179.85: bytes=32 time=77ms TTL=49 Reply from 67.18.179.85: bytes=32 time=81ms TTL=49 Reply from 67.18.179.85: bytes=32 time=63ms TTL=49 Reply from 67.18.179.85: bytes=32 time=76ms TTL=49 Reply from 67.18.179.85: bytes=32 time=58ms TTL=49 Reply from 67.18.179.85: bytes=32 time=93ms TTL=49 Reply from 67.18.179.85: bytes=32 time=94ms TTL=49 Reply from 67.18.179.85: bytes=32 time=55ms TTL=49 Reply from 67.18.179.85: bytes=32 time=91ms TTL=49 Reply from 67.18.179.85: bytes=32 time=70ms TTL=49 Reply from 67.18.179.85: bytes=32 time=61ms TTL=49 Reply from 67.18.179.85: bytes=32 time=59ms TTL=49 Reply from 67.18.179.85: bytes=32 time=101ms TTL=49 Reply from 67.18.179.85: bytes=32 time=94ms TTL=49 Reply from 67.18.179.85: bytes=32 time=71ms TTL=49 Reply from 67.18.179.85: bytes=32 time=112ms TTL=49 Reply from 67.18.179.85: bytes=32 time=132ms TTL=49 Reply from 67.18.179.85: bytes=32 time=66ms TTL=49 Reply from 67.18.179.85: bytes=32 time=68ms TTL=49 Reply from 67.18.179.85: bytes=32 time=60ms TTL=49 Reply from 67.18.179.85: bytes=32 time=63ms TTL=49 Reply from 67.18.179.85: bytes=32 time=67ms TTL=49 Reply from 67.18.179.85: bytes=32 time=64ms TTL=49 Reply from 67.18.179.85: bytes=32 time=58ms TTL=49 Reply from 67.18.179.85: bytes=32 time=66ms TTL=49 Reply from 67.18.179.85: bytes=32 time=61ms TTL=49 Reply from 67.18.179.85: bytes=32 time=60ms TTL=49 Reply from 67.18.179.85: bytes=32 time=82ms TTL=49 Reply from 67.18.179.85: bytes=32 time=83ms TTL=49 Reply from 67.18.179.85: bytes=32 time=120ms TTL=49 Reply from 67.18.179.85: bytes=32 time=77ms TTL=49 Reply from 67.18.179.85: bytes=32 time=92ms TTL=49 Reply from 67.18.179.85: bytes=32 time=177ms TTL=49 Reply from 67.18.179.85: bytes=32 time=62ms TTL=49 Reply from 67.18.179.85: bytes=32 time=59ms TTL=49 Reply from 67.18.179.85: bytes=32 time=65ms TTL=49 Reply from 67.18.179.85: bytes=32 time=130ms TTL=49 Reply from 67.18.179.85: bytes=32 time=64ms TTL=49 Reply from 67.18.179.85: bytes=32 time=161ms TTL=49 Reply from 67.18.179.85: bytes=32 time=59ms TTL=49 Reply from 67.18.179.85: bytes=32 time=128ms TTL=49 Reply from 67.18.179.85: bytes=32 time=67ms TTL=49 Reply from 67.18.179.85: bytes=32 time=161ms TTL=49 Reply from 67.18.179.85: bytes=32 time=67ms TTL=49 Reply from 67.18.179.85: bytes=32 time=64ms TTL=49 Reply from 67.18.179.85: bytes=32 time=69ms TTL=49 Reply from 67.18.179.85: bytes=32 time=76ms TTL=49 Reply from 67.18.179.85: bytes=32 time=112ms TTL=49 Reply from 67.18.179.85: bytes=32 time=91ms TTL=49 Reply from 67.18.179.85: bytes=32 time=62ms TTL=49 Reply from 67.18.179.85: bytes=32 time=73ms TTL=49 Reply from 67.18.179.85: bytes=32 time=116ms TTL=49 Reply from 67.18.179.85: bytes=32 time=109ms TTL=49 Reply from 67.18.179.85: bytes=32 time=58ms TTL=49 Reply from 67.18.179.85: bytes=32 time=87ms TTL=49 Reply from 67.18.179.85: bytes=32 time=108ms TTL=49 Reply from 67.18.179.85: bytes=32 time=95ms TTL=49 Reply from 67.18.179.85: bytes=32 time=55ms TTL=49 Reply from 67.18.179.85: bytes=32 time=64ms TTL=49 Reply from 67.18.179.85: bytes=32 time=62ms TTL=49 Reply from 67.18.179.85: bytes=32 time=54ms TTL=49 Reply from 67.18.179.85: bytes=32 time=70ms TTL=49 Reply from 67.18.179.85: bytes=32 time=72ms TTL=49 Reply from 67.18.179.85: bytes=32 time=85ms TTL=49 Reply from 67.18.179.85: bytes=32 time=112ms TTL=49 Reply from 67.18.179.85: bytes=32 time=59ms TTL=49 Reply from 67.18.179.85: bytes=32 time=110ms TTL=49 Reply from 67.18.179.85: bytes=32 time=75ms TTL=49 Reply from 67.18.179.85: bytes=32 time=72ms TTL=49 Reply from 67.18.179.85: bytes=32 time=90ms TTL=49 Reply from 67.18.179.85: bytes=32 time=57ms TTL=49 Reply from 67.18.179.85: bytes=32 time=111ms TTL=49 Reply from 67.18.179.85: bytes=32 time=63ms TTL=49 Reply from 67.18.179.85: bytes=32 time=87ms TTL=49 Reply from 67.18.179.85: bytes=32 time=103ms TTL=49 Reply from 67.18.179.85: bytes=32 time=64ms TTL=49 Reply from 67.18.179.85: bytes=32 time=63ms TTL=49 Reply from 67.18.179.85: bytes=32 time=59ms TTL=49 Reply from 67.18.179.85: bytes=32 time=101ms TTL=49 Reply from 67.18.179.85: bytes=32 time=84ms TTL=49 Reply from 67.18.179.85: bytes=32 time=76ms TTL=49 Reply from 67.18.179.85: bytes=32 time=82ms TTL=49 Reply from 67.18.179.85: bytes=32 time=76ms TTL=49 Ping statistics for 67.18.179.85: Packets: Sent = 100, Received = 100, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 54ms, Maximum = 189ms, Average = 80ms bad pings to testmy.net haha Please do a trace route to google and post the results. Also I need to know your carrier. Thanks! Tracing route to www.l.google.com [216.239.37.104] over a maximum of 30 hops: 1 50 ms 55 ms 13 ms 10.54.0.1 2 7 ms 13 ms 25 ms opti33-162.nassau.cv.net [167.206.33.162] 3 32 ms 7 ms 10 ms r4-ge9-1.mhe.hcvlny.cv.net [167.206.33.133] 4 26 ms 15 ms 9 ms 65.19.111.203 5 19 ms 11 ms 35 ms 451be0b4.cst.lightpath.net [65.19.96.180] 6 15 ms 16 ms 13 ms 64.15.0.37 7 * * * Request timed out. 8 39 ms 36 ms 41 ms 66.249.94.235 9 27 ms 52 ms 25 ms 72.14.232.106 10 20 ms 79 ms 72 ms 72.14.232.108 11 23 ms 70 ms 74 ms 216.239.37.104 Trace complete. (this is all still with router DISCONNECTED) yeah i have OPTIMUM ONLINE speed is 15/2 Mbps Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179487 Share on other sites More sharing options...
ispgeek Posted October 23, 2006 CID Share Posted October 23, 2006 You need to contact your ISP and ask them if they are having some issues...sure looks like it to me....send them a copy of the trace route if they have any doubts.... Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179489 Share on other sites More sharing options...
ispgeek Posted October 23, 2006 CID Share Posted October 23, 2006 Now keep in mind...those ping times are not that bad....BUT...that drop is a whole different beast....to google that shouldn't be happening at that hope this is for sure... Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179490 Share on other sites More sharing options...
Guest kamil234 Posted October 23, 2006 CID Share Posted October 23, 2006 i have a splitter in my house that the modem is on, could that be the issue? (it goes like 5 ways) and no, i cant connect the modem to the main line because the cable is too short. Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179492 Share on other sites More sharing options...
dlewis23 Posted October 23, 2006 CID Share Posted October 23, 2006 i have a splitter in my house that the modem is on, could that be the issue? (it goes like 5 ways) and no, i cant connect the modem to the main line because the cable is too short. that can and probally is causing it. Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179497 Share on other sites More sharing options...
ispgeek Posted October 23, 2006 CID Share Posted October 23, 2006 Does your modem have onboard diagnostics...if it does please post all data from it.....that will tell us real quick if thats the issue or not. Based on your tracert info...that is not the problem...but we can certainly check anyway. Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179498 Share on other sites More sharing options...
Guest kamil234 Posted October 23, 2006 CID Share Posted October 23, 2006 it does, i've done it before butttt....i forgot what numbers you type in to check it..help me out? its a motorola modem nevermind i got it. Frequency 603000000 Hz Locked Signal to Noise Ratio 36 dB Power Level -6 dB The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading Upstream Value Channel ID 1 Frequency 28000000 Hz Ranged Power Level 50 dBmV Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179502 Share on other sites More sharing options...
Guest kamil234 Posted October 23, 2006 CID Share Posted October 23, 2006 yes no maybe? Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179508 Share on other sites More sharing options...
dlewis23 Posted October 23, 2006 CID Share Posted October 23, 2006 everything looks pertty good from your modem, i would try and get it away from that splitter if you can. Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179509 Share on other sites More sharing options...
ispgeek Posted October 23, 2006 CID Share Posted October 23, 2006 it does, i've done it before butttt....i forgot what numbers you type in to check it..help me out? its a motorola modem nevermind i got it. Frequency 603000000 Hz Locked Signal to Noise Ratio 36 dB Power Level -6 dB The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading Upstream Value Channel ID 1 Frequency 28000000 Hz Ranged Power Level 50 dBmV Okay...this is not a splitter issue.....look to your ISP for answers on this one... Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179510 Share on other sites More sharing options...
ispgeek Posted October 23, 2006 CID Share Posted October 23, 2006 everything looks pertty good from your modem, i would try and get it away from that splitter if you can. His dropped packets are very much an external issue. Notice his tracert's....they pretty much tell the story right there.... Link to comment https://testmy.net/ipb/topic/16015-ping-spikes-dropped-packets/#findComment-179511 Share on other sites More sharing options...
Recommended Posts