Continuous ping

[Lakeram Harrypersaud]

Hi Guys,

Is it normal to have the odd timeouts when doing a continous ping from my home to a public ip across the internet or is this a problem?

Any help will be greatly apprecited.

Thanks,

Lake

[nkarpysh · Accepted solution]

Hello,

It is better next time to paste the utput you see for us to clearly see the problem. Do you sing pings missed or RTT very high?

Nik

[Lakeram Harrypersaud]

I mean ping missed. I have an output but there is no timeout here. The RTT looks good yet there are the odd missed ping.

Thanks,

Lake

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=26ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=28ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=33ms TTL=55

Reply from 4.2.2.2: bytes=32 time=33ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=28ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=29ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=28ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=26ms TTL=55

Reply from 4.2.2.2: bytes=32 time=26ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=26ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=28ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=33ms TTL=55

Reply from 4.2.2.2: bytes=32 time=33ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=28ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=29ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=28ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

Reply from 4.2.2.2: bytes=32 time=26ms TTL=55

Reply from 4.2.2.2: bytes=32 time=26ms TTL=55

Reply from 4.2.2.2: bytes=32 time=27ms TTL=55

[nkarpysh · Accepted solution]

Some pings being dropped - not the best sign - though ping might not be actually droppec-  but delayed.

I mean that by default ping is using default Wait timeout for a ping response before declaring it as missed. So you can change that timeout to a higher value (-w on Windows or use context help of your ping command as it may be different depending on OS) and see if pings really missed or just arriving later.

If they missed - smth happening on the path. Again - that can be normal if provider is rate-limiting your channel to specific rate or a sign of bad link/HW.

There can be really many apsects of that - and detailed analysis needed even to say if that is fine or a problem.

Nik

[Lakeram Harrypersaud]

Thanks guys.

Regards,

Lake

[mbrooke]

Test