dslreports logo
site
 
    All Forums Hot Topics Gallery
spc

spacer




how-to block ads


Search Topic:
uniqs
1084
share rss forum feed


fahim

join:2011-02-08
canada

[Cable] Massive lag/jitter?




Trying to play a multiplayer game online...somewhat frustrating :/ Was working fine this morning before work, and got home to this. Restarted tomato-based router doesn't seem to have done anything.

Any suggestions on what I can do to troubleshoot?


fahim

join:2011-02-08
canada
Seems to fluctuate every few seconds...




fahim

join:2011-02-08
canada

1 edit
reply to fahim



Oh well. Not the end of the world. Perhaps will stabilize later on.


fahim

join:2011-02-08
canada
reply to fahim
Might be something wrong after all...speeds are unusually low as well

Fallowfield POI in Ottawa

Might as well try a modem power off/on cycle.


TSI Andre
Got TekSavvy?
Premium,VIP
join:2008-06-03
Chatham, ON
kudos:25
If that doesn't work. Please post in the direct forum so we can take a look for you


fahim

join:2011-02-08
canada
reply to fahim
Upload speeds are a bit low



Here are my modem stats




Thanks Andre; will create a post in the direct forum.
Expand your moderator at work

Savvyvdsl

join:2013-04-29
Canada
reply to fahim

Re: [Cable] Massive lag/jitter?

Is your upstream being saturated by any device on the network?
Cable slows down (latency increase) bigtime during heavy uploading... which could include a torrent client running in the background.


fahim

join:2011-02-08
canada
reply to fahim
Nope; nothing being uploaded.

Packet loss seems to be the culprit. Trying to determine the cause with teksavvy in the direct forum.


cable_proble

@teksavvy.com
some issue in thornhill area,

almost no traffic on the line, definitely some thing is wrong on ISP side,

64 bytes from yyz08s10-in-f31.1e100.net (173.194.43.127): icmp_req=24 ttl=56 time=13.1 ms
64 bytes from yyz08s10-in-f31.1e100.net (173.194.43.127): icmp_req=25 ttl=56 time=25.1 ms
^C
--- google.ca ping statistics ---
25 packets transmitted, 15 received, 40% packet loss, time 24021ms
rtt min/avg/max/mdev = 12.735/20.719/28.852/6.699 ms


fahim

join:2011-02-08
canada
reply to fahim
On a machine connected directly to the modem


root@WNR3500L:/tmp/home/root# ping -c 25 google.ca
PING google.ca (173.194.43.120): 56 data bytes
64 bytes from 173.194.43.120: seq=1 ttl=57 time=14.530 ms
64 bytes from 173.194.43.120: seq=2 ttl=57 time=15.285 ms
64 bytes from 173.194.43.120: seq=3 ttl=57 time=15.565 ms
64 bytes from 173.194.43.120: seq=4 ttl=57 time=15.144 ms
64 bytes from 173.194.43.120: seq=5 ttl=57 time=16.680 ms
64 bytes from 173.194.43.120: seq=6 ttl=57 time=15.544 ms
64 bytes from 173.194.43.120: seq=7 ttl=57 time=17.478 ms
64 bytes from 173.194.43.120: seq=8 ttl=57 time=14.894 ms
64 bytes from 173.194.43.120: seq=9 ttl=57 time=15.778 ms
64 bytes from 173.194.43.120: seq=10 ttl=57 time=14.488 ms
64 bytes from 173.194.43.120: seq=11 ttl=57 time=15.303 ms
64 bytes from 173.194.43.120: seq=12 ttl=57 time=14.945 ms
64 bytes from 173.194.43.120: seq=14 ttl=57 time=14.741 ms
64 bytes from 173.194.43.120: seq=15 ttl=57 time=15.280 ms
64 bytes from 173.194.43.120: seq=16 ttl=57 time=16.121 ms
64 bytes from 173.194.43.120: seq=17 ttl=57 time=15.408 ms
64 bytes from 173.194.43.120: seq=18 ttl=57 time=29.604 ms
64 bytes from 173.194.43.120: seq=20 ttl=57 time=15.558 ms
64 bytes from 173.194.43.120: seq=21 ttl=57 time=13.937 ms
64 bytes from 173.194.43.120: seq=22 ttl=57 time=13.948 ms
64 bytes from 173.194.43.120: seq=23 ttl=57 time=14.585 ms
64 bytes from 173.194.43.120: seq=24 ttl=57 time=16.072 ms

--- google.ca ping statistics ---
25 packets transmitted, 22 packets received, 12% packet loss
round-trip min/avg/max = 13.937/15.949/29.604 ms



cable_proble

@teksavvy.com
had the packet losing problem since morning and still going, is this a know problem and anyone is working on it?

64 bytes from 173.194.43.127: seq=76 ttl=57 time=12.524 ms
64 bytes from 173.194.43.127: seq=77 ttl=57 time=12.589 ms
64 bytes from 173.194.43.127: seq=80 ttl=57 time=26.370 ms
64 bytes from 173.194.43.127: seq=82 ttl=57 time=26.586 ms
64 bytes from 173.194.43.127: seq=83 ttl=57 time=12.268 ms

--- google.ca ping statistics ---
86 packets transmitted, 58 packets received, 32% packet loss
round-trip min/avg/max = 10.737/14.826/27.781 ms


Old Martin
Premium
join:2006-02-23
kudos:33
Hello,

I would strongly recommend you post in the »TekSavvy Direct forum so we may look into this with you.

Regards,
Martin

BrianON

join:2011-09-30
Ottawa, ON
Reviews:
·TekSavvy Cable

2 edits
reply to fahim
On cable in Ottawa it seems fine - Baseline/Woodroffe. 7:15PM on a Friday. So not widespread / ISP wide.




C:\>ping google.ca -n 100
 
Pinging google.ca [74.125.226.152] with 32 bytes of data:
Reply from 74.125.226.152: bytes=32 time=15ms TTL=56
Reply from 74.125.226.152: bytes=32 time=16ms TTL=56
Reply from 74.125.226.152: bytes=32 time=16ms TTL=56
...
Reply from 74.125.226.152: bytes=32 time=15ms TTL=56
Reply from 74.125.226.152: bytes=32 time=16ms TTL=56
Reply from 74.125.226.152: bytes=32 time=17ms TTL=56
 
Ping statistics for 74.125.226.152:
    Packets: Sent = 100, Received = 100, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 14ms, Maximum = 35ms, Average = 16ms
 


nupogodi
Premium
join:2012-07-10
Toronto, ON
reply to fahim
Hey, I've been getting the same thing here in Toronto.

Intermittent packet loss up to 30-40%. Lasts 20 minutes or so and then goes back to normal, 0% packet loss.

In the Direct forum they want me to leave my computer directly connected to the modem until the issue is resolved? LOL. Sorry, there's a reason I pay so much for this line, it's because I actually need to use it. Thinking about leaving TSI, no one's really interested in helping me when I've actually shown that my line stats are good and the packet loss occurs AFTER it leaves my network. Doubt this one can be blamed on Rogers, either.

falkon21

join:2004-02-27
I'm in the same boat, it's really frustrating.


fahim

join:2011-02-08
canada
reply to fahim
So while I wait, I have one single computer connected to the modem in the basement, leaving a plethora of devices and computers without net access. Yep; frustrating. A few disgruntled sighs from family members, but oh well. I'd rather get this problem solved.


oceros

join:2013-07-20
St Thomas, ON
Reviews:
·Rogers Hi-Speed
said by fahim:

So while I wait, I have one single computer connected to the modem in the basement, leaving a plethora of devices and computers without net access. Yep; frustrating. A few disgruntled sighs from family members, but oh well. I'd rather get this problem solved.

hook it back to normal once you get a *ahem* good status update for your ticket. even if it's a tech dispatch. if a tech is booked then they are done looking at your connection remotely.


nupogodi
Premium
join:2012-07-10
Toronto, ON
reply to fahim
Another 'attack' just now!

Dev$ ping -c 50 google.ca
PING google.ca (74.125.226.120): 56 data bytes
64 bytes from 74.125.226.120: icmp_seq=0 ttl=56 time=18.623 ms
64 bytes from 74.125.226.120: icmp_seq=1 ttl=56 time=19.809 ms
Request timeout for icmp_seq 2
64 bytes from 74.125.226.120: icmp_seq=3 ttl=56 time=17.545 ms
64 bytes from 74.125.226.120: icmp_seq=4 ttl=56 time=26.310 ms
64 bytes from 74.125.226.120: icmp_seq=5 ttl=56 time=16.810 ms
64 bytes from 74.125.226.120: icmp_seq=6 ttl=56 time=16.711 ms
Request timeout for icmp_seq 7
64 bytes from 74.125.226.120: icmp_seq=8 ttl=56 time=17.366 ms
64 bytes from 74.125.226.120: icmp_seq=9 ttl=56 time=12.059 ms
64 bytes from 74.125.226.120: icmp_seq=10 ttl=56 time=18.404 ms
m64 bytes from 74.125.226.120: icmp_seq=11 ttl=56 time=17.609 ms
64 bytes from 74.125.226.120: icmp_seq=12 ttl=56 time=15.789 ms
64 bytes from 74.125.226.120: icmp_seq=13 ttl=56 time=15.307 ms
64 bytes from 74.125.226.120: icmp_seq=14 ttl=56 time=23.053 ms
64 bytes from 74.125.226.120: icmp_seq=15 ttl=56 time=14.134 ms
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
64 bytes from 74.125.226.120: icmp_seq=18 ttl=56 time=13.707 ms
Request timeout for icmp_seq 19
64 bytes from 74.125.226.120: icmp_seq=20 ttl=56 time=14.968 ms
64 bytes from 74.125.226.120: icmp_seq=21 ttl=56 time=18.543 ms
64 bytes from 74.125.226.120: icmp_seq=22 ttl=56 time=16.409 ms
64 bytes from 74.125.226.120: icmp_seq=23 ttl=56 time=16.861 ms
64 bytes from 74.125.226.120: icmp_seq=24 ttl=56 time=17.034 ms
64 bytes from 74.125.226.120: icmp_seq=25 ttl=56 time=14.857 ms
64 bytes from 74.125.226.120: icmp_seq=26 ttl=56 time=18.831 ms
64 bytes from 74.125.226.120: icmp_seq=27 ttl=56 time=12.586 ms
64 bytes from 74.125.226.120: icmp_seq=28 ttl=56 time=16.035 ms
64 bytes from 74.125.226.120: icmp_seq=29 ttl=56 time=34.425 ms
64 bytes from 74.125.226.120: icmp_seq=30 ttl=56 time=36.567 ms
Request timeout for icmp_seq 31
64 bytes from 74.125.226.120: icmp_seq=32 ttl=56 time=24.803 ms
64 bytes from 74.125.226.120: icmp_seq=33 ttl=56 time=15.930 ms
64 bytes from 74.125.226.120: icmp_seq=34 ttl=56 time=19.111 ms
64 bytes from 74.125.226.120: icmp_seq=35 ttl=56 time=17.108 ms
64 bytes from 74.125.226.120: icmp_seq=36 ttl=56 time=15.610 ms
64 bytes from 74.125.226.120: icmp_seq=37 ttl=56 time=23.530 ms
Request timeout for icmp_seq 38
64 bytes from 74.125.226.120: icmp_seq=39 ttl=56 time=15.640 ms
64 bytes from 74.125.226.120: icmp_seq=40 ttl=56 time=15.099 ms
64 bytes from 74.125.226.120: icmp_seq=41 ttl=56 time=14.654 ms
64 bytes from 74.125.226.120: icmp_seq=42 ttl=56 time=20.538 ms
Request timeout for icmp_seq 43
64 bytes from 74.125.226.120: icmp_seq=44 ttl=56 time=16.926 ms
64 bytes from 74.125.226.120: icmp_seq=45 ttl=56 time=38.892 ms
64 bytes from 74.125.226.120: icmp_seq=46 ttl=56 time=28.983 ms
64 bytes from 74.125.226.120: icmp_seq=47 ttl=56 time=13.672 ms
64 bytes from 74.125.226.120: icmp_seq=48 ttl=56 time=13.817 ms
64 bytes from 74.125.226.120: icmp_seq=49 ttl=56 time=14.588 ms
 
--- google.ca ping statistics ---
50 packets transmitted, 42 packets received, 16.0% packet loss
round-trip min/avg/max/stddev = 12.059/18.792/38.892/6.086 ms
 

All of my services went down, couldn't connect to anything but barely load some WWW pages, massive packet loss...

And now, back to normal, phenomenal speeds and zero packet loss. *What the hell is going ON!?*


nupogodi
Premium
join:2012-07-10
Toronto, ON
reply to fahim
Honestly this is ridiculous. At random times throughout the day, for 15-45min, I encounter massive slowdowns and insane packet loss to the point where the pipe is nearly unusable. Line stats are good, all I see is that somewhere downstream packets are getting lost, makes even casual browsing of the WWW difficult (not to mention any other services...).

Always, within less than an hour, it subsides and goes back to normal and I get the same great speeds and performance as always.

What *IS* going on!?


nupogodi
Premium
join:2012-07-10
Toronto, ON
reply to fahim
Here we go again!!!!!

Dev$ ping -c 100 google.ca
PING google.ca (173.194.43.127): 56 data bytes
64 bytes from 173.194.43.127: icmp_seq=0 ttl=56 time=17.482 ms
64 bytes from 173.194.43.127: icmp_seq=1 ttl=56 time=13.882 ms
64 bytes from 173.194.43.127: icmp_seq=2 ttl=56 time=17.207 ms
Request timeout for icmp_seq 3
64 bytes from 173.194.43.127: icmp_seq=4 ttl=56 time=15.511 ms
64 bytes from 173.194.43.127: icmp_seq=5 ttl=56 time=18.482 ms
Request timeout for icmp_seq 6
64 bytes from 173.194.43.127: icmp_seq=7 ttl=56 time=15.447 ms
64 bytes from 173.194.43.127: icmp_seq=8 ttl=56 time=19.168 ms
64 bytes from 173.194.43.127: icmp_seq=9 ttl=56 time=14.025 ms
64 bytes from 173.194.43.127: icmp_seq=10 ttl=56 time=21.758 ms
64 bytes from 173.194.43.127: icmp_seq=11 ttl=56 time=12.321 ms
64 bytes from 173.194.43.127: icmp_seq=12 ttl=56 time=14.569 ms
Request timeout for icmp_seq 13
64 bytes from 173.194.43.127: icmp_seq=14 ttl=56 time=22.650 ms
64 bytes from 173.194.43.127: icmp_seq=15 ttl=56 time=15.173 ms
Request timeout for icmp_seq 16
Request timeout for icmp_seq 17
64 bytes from 173.194.43.127: icmp_seq=18 ttl=56 time=16.183 ms
64 bytes from 173.194.43.127: icmp_seq=19 ttl=56 time=12.505 ms
64 bytes from 173.194.43.127: icmp_seq=20 ttl=56 time=17.594 ms
64 bytes from 173.194.43.127: icmp_seq=21 ttl=56 time=13.023 ms
64 bytes from 173.194.43.127: icmp_seq=22 ttl=56 time=15.844 ms
Request timeout for icmp_seq 23
Request timeout for icmp_seq 24
64 bytes from 173.194.43.127: icmp_seq=25 ttl=56 time=11.666 ms
64 bytes from 173.194.43.127: icmp_seq=26 ttl=56 time=29.587 ms
64 bytes from 173.194.43.127: icmp_seq=27 ttl=56 time=16.698 ms
64 bytes from 173.194.43.127: icmp_seq=28 ttl=56 time=17.124 ms
64 bytes from 173.194.43.127: icmp_seq=29 ttl=56 time=13.477 ms
64 bytes from 173.194.43.127: icmp_seq=30 ttl=56 time=16.805 ms
Request timeout for icmp_seq 31
Request timeout for icmp_seq 32
Request timeout for icmp_seq 33
Request timeout for icmp_seq 34
64 bytes from 173.194.43.127: icmp_seq=35 ttl=56 time=12.757 ms
64 bytes from 173.194.43.127: icmp_seq=36 ttl=56 time=15.871 ms
64 bytes from 173.194.43.127: icmp_seq=37 ttl=56 time=13.487 ms
64 bytes from 173.194.43.127: icmp_seq=38 ttl=56 time=13.530 ms
64 bytes from 173.194.43.127: icmp_seq=39 ttl=56 time=12.066 ms
64 bytes from 173.194.43.127: icmp_seq=40 ttl=56 time=14.683 ms
64 bytes from 173.194.43.127: icmp_seq=41 ttl=56 time=14.344 ms
64 bytes from 173.194.43.127: icmp_seq=42 ttl=56 time=14.900 ms
64 bytes from 173.194.43.127: icmp_seq=43 ttl=56 time=14.543 ms
Request timeout for icmp_seq 44
Request timeout for icmp_seq 45
64 bytes from 173.194.43.127: icmp_seq=46 ttl=56 time=33.228 ms
64 bytes from 173.194.43.127: icmp_seq=47 ttl=56 time=18.378 ms
64 bytes from 173.194.43.127: icmp_seq=48 ttl=56 time=24.916 ms
64 bytes from 173.194.43.127: icmp_seq=49 ttl=56 time=13.974 ms
64 bytes from 173.194.43.127: icmp_seq=50 ttl=56 time=17.373 ms
64 bytes from 173.194.43.127: icmp_seq=51 ttl=56 time=17.547 ms
64 bytes from 173.194.43.127: icmp_seq=52 ttl=56 time=12.613 ms
64 bytes from 173.194.43.127: icmp_seq=53 ttl=56 time=12.777 ms
64 bytes from 173.194.43.127: icmp_seq=54 ttl=56 time=17.898 ms
Request timeout for icmp_seq 55
Request timeout for icmp_seq 56
Request timeout for icmp_seq 57
Request timeout for icmp_seq 58
64 bytes from 173.194.43.127: icmp_seq=59 ttl=56 time=16.226 ms
64 bytes from 173.194.43.127: icmp_seq=60 ttl=56 time=24.332 ms
Request timeout for icmp_seq 61
Request timeout for icmp_seq 62
64 bytes from 173.194.43.127: icmp_seq=63 ttl=56 time=20.609 ms
64 bytes from 173.194.43.127: icmp_seq=64 ttl=56 time=16.528 ms
64 bytes from 173.194.43.127: icmp_seq=65 ttl=56 time=13.199 ms
64 bytes from 173.194.43.127: icmp_seq=66 ttl=56 time=18.015 ms
Request timeout for icmp_seq 67
Request timeout for icmp_seq 68
64 bytes from 173.194.43.127: icmp_seq=69 ttl=56 time=15.314 ms
64 bytes from 173.194.43.127: icmp_seq=70 ttl=56 time=21.823 ms
64 bytes from 173.194.43.127: icmp_seq=71 ttl=56 time=14.222 ms
Request timeout for icmp_seq 72
64 bytes from 173.194.43.127: icmp_seq=73 ttl=56 time=13.495 ms
64 bytes from 173.194.43.127: icmp_seq=74 ttl=56 time=15.476 ms
64 bytes from 173.194.43.127: icmp_seq=75 ttl=56 time=15.311 ms
64 bytes from 173.194.43.127: icmp_seq=76 ttl=56 time=14.577 ms
64 bytes from 173.194.43.127: icmp_seq=77 ttl=56 time=17.502 ms
64 bytes from 173.194.43.127: icmp_seq=78 ttl=56 time=19.063 ms
Request timeout for icmp_seq 79
64 bytes from 173.194.43.127: icmp_seq=80 ttl=56 time=13.839 ms
Request timeout for icmp_seq 81
64 bytes from 173.194.43.127: icmp_seq=82 ttl=56 time=16.509 ms
64 bytes from 173.194.43.127: icmp_seq=83 ttl=56 time=15.371 ms
64 bytes from 173.194.43.127: icmp_seq=84 ttl=56 time=16.815 ms
Request timeout for icmp_seq 85
64 bytes from 173.194.43.127: icmp_seq=86 ttl=56 time=13.681 ms
64 bytes from 173.194.43.127: icmp_seq=87 ttl=56 time=20.058 ms
64 bytes from 173.194.43.127: icmp_seq=88 ttl=56 time=18.216 ms
64 bytes from 173.194.43.127: icmp_seq=89 ttl=56 time=13.403 ms
64 bytes from 173.194.43.127: icmp_seq=90 ttl=56 time=17.069 ms
Request timeout for icmp_seq 91
64 bytes from 173.194.43.127: icmp_seq=92 ttl=56 time=12.891 ms
64 bytes from 173.194.43.127: icmp_seq=93 ttl=56 time=15.029 ms
64 bytes from 173.194.43.127: icmp_seq=94 ttl=56 time=16.686 ms
Request timeout for icmp_seq 95
Request timeout for icmp_seq 96
64 bytes from 173.194.43.127: icmp_seq=97 ttl=56 time=8.693 ms
64 bytes from 173.194.43.127: icmp_seq=98 ttl=56 time=19.471 ms
64 bytes from 173.194.43.127: icmp_seq=99 ttl=56 time=12.541 ms
 
--- google.ca ping statistics ---
100 packets transmitted, 72 packets received, 28.0% packet loss
round-trip min/avg/max/stddev = 8.693/16.375/33.228/3.909 ms]
 

Honestly when are these people going to stop giving me bullshit answers!? Oh, we need your line stats, we need you to connect directly to the modem jesus christ.

I'm not the only one. This is happening regularly. It's been happening for a few weeks now. What is going ON? Practically unusable...


nupogodi
Premium
join:2012-07-10
Toronto, ON
reply to fahim
Now it has *actually* become unusable and I'm tethering my wireless to post this. Or, do anything.

What in hells is going on??


JZ

@teksavvy.com
Same here. Leslieville in Toronto, getting packet losses.


liamd90

@teksavvy.com
reply to fahim
Same problem here in the Jane and Eglinton Area of Toronto.




cant even play any games online the ping and lag is just too much


fahim

join:2011-02-08
canada
reply to fahim
Still being investigated

A couple of things are a bit annoying/puzzling:
- Only started Thursday (and with all the online gamers/streamers at home; trust me I'd know if things were bad earlier)
- I take care of my internal gigabit network; I can safely rule that out as the source of the issue (but I understand how this needs to be proven...and its simpler to bypass this by connecting a single PC directly to the modem)
- Not an RF issue apparently

So where is the issue? Routing? Faulty switch somewhere? Just curious. This may vary on a case by case basis, so probably something I can ask in the direct forums.


jmck
formerly 'shaded'

join:2010-10-02
Ottawa, ON
Reviews:
·TekSavvy DSL
·Start Communicat..
run mtr/winmtr instead of just pinging an IP and hopefully you can track down at least which hop its happening at. if it's happening at the gateway then it's some node or local issue. if it's happening between TSI and Rogers than it's an issue there.


clarknova

join:2010-02-23
Grande Prairie, AB
kudos:7
Reviews:
·TekSavvy DSL
reply to fahim
I don't know if it's related, considering I'm in Alberta on DSL, but I've been seeing throughput fall to the earth for several minutes at a time, about a dozen times in the last 24 hours. Meanwhile, no abnormal packet loss to the first hop.

It seems like TSI is having routing issues.
--
db


fahim

join:2011-02-08
canada
reply to fahim
My ticket's been escalated to rCable's networking department....whatever that implies.

Will try out mtr later when I get back home.


fahim

join:2011-02-08
canada
reply to fahim
Output from MTR (removed my IP/hostname for privacy reasons)
                                        My traceroute  [v0.71]
XXXXXX.cable.teksavvy.com (0.0.0.0)                                  Mon Dec  2 18:39:10 2013
Keys:  Help   Display mode   Restart statistics   Order of fields   quit
                                                              Packets               Pings
 Host                                                       Loss%   Snt   Last   Avg  Best  Wrst StDev
 1. 10.124.12.1                                             14.4%   139    6.6   9.0   6.1  34.5   4.9
 2. gw01.ajax.phub.net.cable.rogers.com                     12.2%   139   16.8  18.3  12.7  55.5   7.3
 3. so-4-0-0.gw02.ym.phub.net.cable.rogers.com               8.7%   138   12.8  16.5  12.5  32.5   3.9
 4. 2120.ae1.bdr04.tor.man.teksavvy.com.packetflow.ca       15.9%   138   13.9  17.5  13.7  59.5   6.0
 5. 72.14.212.134                                           44.5%   138   15.5  18.2  12.9  31.7   5.8
 6. 216.239.47.114                                          13.8%   138   15.8  17.8  13.5  73.1   7.2
 7. 209.85.250.207                                          17.4%   138   15.8  17.3  13.8  33.8   4.4
 8. 74.125.226.119                                          10.9%   138   14.8  17.6  13.2  32.5   5.3
 
 

Ping results
Request timeout for icmp_seq 37
64 bytes from 173.194.43.120: icmp_seq=38 ttl=57 time=15.245 ms
64 bytes from 173.194.43.120: icmp_seq=39 ttl=57 time=14.416 ms
64 bytes from 173.194.43.120: icmp_seq=40 ttl=57 time=15.468 ms
64 bytes from 173.194.43.120: icmp_seq=41 ttl=57 time=14.003 ms
64 bytes from 173.194.43.120: icmp_seq=42 ttl=57 time=16.170 ms
64 bytes from 173.194.43.120: icmp_seq=43 ttl=57 time=15.939 ms
64 bytes from 173.194.43.120: icmp_seq=44 ttl=57 time=14.762 ms
64 bytes from 173.194.43.120: icmp_seq=45 ttl=57 time=17.022 ms
64 bytes from 173.194.43.120: icmp_seq=46 ttl=57 time=14.031 ms
64 bytes from 173.194.43.120: icmp_seq=47 ttl=57 time=15.767 ms
64 bytes from 173.194.43.120: icmp_seq=48 ttl=57 time=14.430 ms
64 bytes from 173.194.43.120: icmp_seq=49 ttl=57 time=14.470 ms
 
--- google.ca ping statistics ---
50 packets transmitted, 44 packets received, 12.0% packet loss
round-trip min/avg/max/stddev = 13.604/16.311/28.827/3.126 ms
 


jmck
formerly 'shaded'

join:2010-10-02
Ottawa, ON
so it looks like you're getting packet loss on the first hop which means the issue is somewhere between your cable modem and Rogers's node. the 15% packet loss is a pretty good number since it will likely be deemed too serious to ignore on Rogers.