Anyone getting packloss and choppy ping?
Pinging montreal2.voip.ms [174.142.75.171] with 32 bytes of data:
Reply from 174.142.75.171: bytes=32 time=167ms TTL=51
Request timed out.
Reply from 174.142.75.171: bytes=32 time=193ms TTL=51
Reply from 174.142.75.171: bytes=32 time=82ms TTL=51
Reply from 174.142.75.171: bytes=32 time=98ms TTL=51
Reply from 174.142.75.171: bytes=32 time=80ms TTL=51
Reply from 174.142.75.171: bytes=32 time=258ms TTL=51
Reply from 174.142.75.171: bytes=32 time=56ms TTL=51
Reply from 174.142.75.171: bytes=32 time=106ms TTL=51
Reply from 174.142.75.171: bytes=32 time=149ms TTL=51
Reply from 174.142.75.171: bytes=32 time=30ms TTL=51
Reply from 174.142.75.171: bytes=32 time=144ms TTL=51
Reply from 174.142.75.171: bytes=32 time=115ms TTL=51
Reply from 174.142.75.171: bytes=32 time=136ms TTL=51
Reply from 174.142.75.171: bytes=32 time=147ms TTL=51
Reply from 174.142.75.171: bytes=32 time=171ms TTL=51
Reply from 174.142.75.171: bytes=32 time=76ms TTL=51
Ping statistics for 174.142.75.171:
Packets: Sent = 17, Received = 16, Lost = 1 (5% loss),
Approximate round trip times in milli-seconds:
Minimum = 30ms, Maximum = 258ms, Average = 125ms
Pinging toronto.voip.ms [174.137.63.206] with 32 bytes of data:
Reply from 174.137.63.206: bytes=32 time=225ms TTL=55
Reply from 174.137.63.206: bytes=32 time=96ms TTL=55
Reply from 174.137.63.206: bytes=32 time=115ms TTL=55
Reply from 174.137.63.206: bytes=32 time=92ms TTL=55
Reply from 174.137.63.206: bytes=32 time=75ms TTL=55
Reply from 174.137.63.206: bytes=32 time=73ms TTL=55
Reply from 174.137.63.206: bytes=32 time=166ms TTL=55
Reply from 174.137.63.206: bytes=32 time=15ms TTL=55
Reply from 174.137.63.206: bytes=32 time=87ms TTL=55
Reply from 174.137.63.206: bytes=32 time=46ms TTL=55
Reply from 174.137.63.206: bytes=32 time=164ms TTL=55
Reply from 174.137.63.206: bytes=32 time=152ms TTL=55
Reply from 174.137.63.206: bytes=32 time=223ms TTL=55
Reply from 174.137.63.206: bytes=32 time=206ms TTL=55
Reply from 174.137.63.206: bytes=32 time=186ms TTL=55
Reply from 174.137.63.206: bytes=32 time=51ms TTL=55
Reply from 174.137.63.206: bytes=32 time=118ms TTL=55
Reply from 174.137.63.206: bytes=32 time=142ms TTL=55
Reply from 174.137.63.206: bytes=32 time=173ms TTL=55
Reply from 174.137.63.206: bytes=32 time=92ms TTL=55
Reply from 174.137.63.206: bytes=32 time=141ms TTL=55
Reply from 174.137.63.206: bytes=32 time=166ms TTL=55
Reply from 174.137.63.206: bytes=32 time=91ms TTL=55
Reply from 174.137.63.206: bytes=32 time=120ms TTL=55
Request timed out.
Reply from 174.137.63.206: bytes=32 time=89ms TTL=55
Reply from 174.137.63.206: bytes=32 time=54ms TTL=55
Reply from 174.137.63.206: bytes=32 time=226ms TTL=55
Reply from 174.137.63.206: bytes=32 time=169ms TTL=55
Reply from 174.137.63.206: bytes=32 time=114ms TTL=55
Host Loss% Last Avg Best Wrst StDev
1. 67.212.84.1 0.0% 6.4 3.4 0.8 8.8 2.2
2. 209.44.125.161 0.0% 0.3 0.2 0.2 0.3 0.0
3. 67.69.244.157 0.0% 0.4 4.1 0.4 68.4 14.6
4. bx4-montreal02_pos5-0-0.net.bell.ca 0.0% 0.6 0.8 0.5 4.4 0.8
5. Limelight_bx4-montreal02.net.bell.ca 0.0% 0.7 3.1 0.6 9.3 3.2
6. tge6-2.fr4.yyz.llnw.net 0.0% 7.9 11.9 7.8 26.6 5.1
7. teksavvy.tge11-3.fr4.yyz.llnw.net 0.0% 7.8 8.1 7.8 14.4 1.4
8. 24-52-255-154.cable.teksavvy.com 0.0% 10.1 9.5 9.3 10.1 0.2
9. gw01.wlfdle.phub.net.cable.rogers.com 0.0% 13.7 13.2 11.3 14.7 0.9
10. ???
11. XXX-XXX-183-187.cable.teksavvy.com 14.3% 91.8 115.2 24.5 174.8 38.4
Tracing route to google.ca [74.125.226.95]
over a maximum of 30 hops:
1 1 ms 1 ms 1 ms 192.168.1.1
2 9 ms 9 ms 8 ms 10.126.158.129
3 43 ms 52 ms 119 ms 66.185.89.109
4 88 ms 96 ms 45 ms 24-52-255-150.cable.teksavvy.com [24.52.255.150]
5 102 ms 123 ms 49 ms 24-52-255-149.cable.teksavvy.com [24.52.255.149]
6 12 ms 15 ms 22 ms gw-google.torontointernetxchange.net [206.108.34
.6]
7 66 ms 42 ms * 216.239.47.114
8 95 ms 70 ms 115 ms 64.233.175.98
9 117 ms 96 ms 56 ms yyz06s07-in-f31.1e100.net [74.125.226.95]
definitely a problem with TSI and cable. Local node or is anyone else experiencing this?