blackice

Bad ping times and packet loss

Discussion created by blackice on Sep 1, 2016
Latest reply on Sep 1, 2016 by shaw-tamara

      I just got Shaw put in yesterday and I'm running the Cisco modem in bridge mode to my PFsense VM. I have been having major connectivity issues. Everything seems good them will just drop out for a min or so. I have been monitoring the PFsense quality service. The posted a screenshot is of the ping times and packet loss monitoring. The pings are all to the DHCP DNS from Shaw. This is over a 8 hour period since last night.

 

 

Packet loss and ping graph

 

I also did a ping test to google this morning and got this:


Reply from 24.244.4.24: bytes=32 time=25ms TTL=60
Reply from 24.244.4.24: bytes=32 time=24ms TTL=60
Reply from 24.244.4.24: bytes=32 time=30ms TTL=60
Reply from 24.244.4.24: bytes=32 time=22ms TTL=60
Reply from 24.244.4.24: bytes=32 time=20ms TTL=60
Reply from 24.244.4.24: bytes=32 time=22ms TTL=60
Reply from 24.244.4.24: bytes=32 time=239ms TTL=60
Reply from 24.244.4.24: bytes=32 time=19ms TTL=60
Reply from 24.244.4.24: bytes=32 time=168ms TTL=60
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.
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 24.244.4.24: bytes=32 time=20ms TTL=60
Reply from 24.244.4.24: bytes=32 time=22ms TTL=60
Reply from 24.244.4.24: bytes=32 time=26ms TTL=60
Reply from 24.244.4.24: bytes=32 time=23ms TTL=60
Reply from 24.244.4.24: bytes=32 time=19ms TTL=60
Reply from 24.244.4.24: bytes=32 time=24ms TTL=60
Reply from 24.244.4.24: bytes=32 time=22ms TTL=60
Reply from 24.244.4.24: bytes=32 time=20ms TTL=60
Reply from 24.244.4.24: bytes=32 time=26ms TTL=60
Reply from 24.244.4.24: bytes=32 time=33ms TTL=60
Reply from 24.244.4.24: bytes=32 time=27ms TTL=60
Reply from 24.244.4.24: bytes=32 time=24ms TTL=60
Reply from 24.244.4.24: bytes=32 time=18ms TTL=60
Reply from 24.244.4.24: bytes=32 time=21ms TTL=60
Reply from 24.244.4.24: bytes=32 time=20ms TTL=60
Reply from 24.244.4.24: bytes=32 time=25ms TTL=60
Reply from 24.244.4.24: bytes=32 time=25ms TTL=60
Reply from 24.244.4.24: bytes=32 time=17ms TTL=60
Reply from 24.244.4.24: bytes=32 time=23ms TTL=60
Reply from 24.244.4.24: bytes=32 time=18ms TTL=60
Reply from 24.244.4.24: bytes=32 time=436ms TTL=60
Reply from 24.244.4.24: bytes=32 time=1212ms TTL=60
Reply from 24.244.4.24: bytes=32 time=586ms TTL=60
Reply from 24.244.4.24: bytes=32 time=852ms TTL=60
Reply from 24.244.4.24: bytes=32 time=1156ms TTL=60
Reply from 24.244.4.24: bytes=32 time=464ms TTL=60
Reply from 24.244.4.24: bytes=32 time=464ms TTL=60
Reply from 24.244.4.24: bytes=32 time=1000ms TTL=60
Reply from 24.244.4.24: bytes=32 time=285ms TTL=60
Reply from 24.244.4.24: bytes=32 time=978ms TTL=60
Reply from 24.244.4.24: bytes=32 time=1282ms TTL=60
Reply from 24.244.4.24: bytes=32 time=1306ms TTL=60
Reply from 24.244.4.24: bytes=32 time=400ms TTL=60
Reply from 24.244.4.24: bytes=32 time=410ms TTL=60
Reply from 24.244.4.24: bytes=32 time=1159ms TTL=60
Reply from 24.244.4.24: bytes=32 time=853ms TTL=60
Reply from 24.244.4.24: bytes=32 time=1771ms TTL=60
Reply from 24.244.4.24: bytes=32 time=956ms TTL=60
Reply from 24.244.4.24: bytes=32 time=1659ms TTL=60
Reply from 24.244.4.24: bytes=32 time=1307ms TTL=60
Reply from 24.244.4.24: bytes=32 time=1310ms TTL=60
Request timed out.
Reply from 24.244.4.24: bytes=32 time=322ms TTL=60
Reply from 24.244.4.24: bytes=32 time=17ms TTL=60
Reply from 24.244.4.24: bytes=32 time=20ms TTL=60
Reply from 24.244.4.24: bytes=32 time=28ms TTL=60
Reply from 24.244.4.24: bytes=32 time=69ms TTL=60

 

 

Ping statistics for 24.244.4.24:
Packets: Sent = 585, Received = 544, Lost = 41 (7% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 1771ms, Average = 72ms

 

      I also did a traceroute as well:

 

C:\Windows\system32>tracert google.ca

Tracing route to google.ca [24.244.4.24]
over a maximum of 30 hops:

1 21 ms 15 ms 11 ms 68.148.XX.X
2 12 ms 18 ms 15 ms rc3ar-be111-1.ed.shawcable.net [64.59.186.97]
3 85 ms 68 ms 29 ms rc1we-be1.ed.shawcable.net [66.163.70.49]
4 22 ms 17 ms 16 ms rc3no-be6.cg.shawcable.net [66.163.64.69]
5 23 ms 18 ms 17 ms 24.244.4.24

 

      The ping rates fluctuate all over the place. When the connection is stable the speeds are great. 

Whats going on here?

Outcomes