dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
2715

Name
@shawcable.net

Name

Anon

Modem-Related Jitter?

I've been having terrible lag in online FPS games lately, prompting me to check my ping. Apart from typical shaw issues (unusable during the day / etc), I'm getting significant jitter to everywhere I've tested (google.com below):

...
Reply from 173.194.33.23: bytes=32 time=39ms TTL=57
Reply from 173.194.33.23: bytes=32 time=55ms TTL=56
Reply from 173.194.33.23: bytes=32 time=39ms TTL=56
Reply from 173.194.33.23: bytes=32 time=40ms TTL=57
Reply from 173.194.33.23: bytes=32 time=64ms TTL=57
Reply from 173.194.33.23: bytes=32 time=39ms TTL=57
Reply from 173.194.33.23: bytes=32 time=40ms TTL=56
Reply from 173.194.33.23: bytes=32 time=82ms TTL=56
Reply from 173.194.33.23: bytes=32 time=40ms TTL=57

Ping statistics for 173.194.33.23:
Packets: Sent = 87, Received = 87, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 39ms, Maximum = 94ms, Average = 62ms

I ran the tests at 2am to be sure congestion was not an issue (pings spike to ~250ms during the day, jitter is ~100ms). Tracert at 2am:

1 32 ms 9 ms 18 ms XX.XX.XXX.X
2 29 ms 27 ms 29 ms 64.59.173.146
3 37 ms 59 ms 47 ms 66.163.76.58
4 40 ms 42 ms 61 ms 66.163.76.154
5 39 ms 57 ms 38 ms 74.125.48.233
6 48 ms 63 ms 39 ms 209.85.249.32
7 54 ms 41 ms 41 ms 209.85.253.24
8 41 ms 74 ms 39 ms 173.194.33.23

I'm directly connected to the modem, with no routers or other hardware involved. Connecting a different computer had the same result, so there should be no software issues.

Pinging the modem (Motorola SB5102):
Ping statistics for 192.168.100.1:
Packets: Sent = 104, Received = 104, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 32ms, Average = 14ms

As I happen to have another modem (SB5101), I tried that with the same result:
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 32ms, Average = 15ms

I haven't pinged the modems before (that I can remember), is this normal? In any case, jitter was not normal back when Shaw was working properly (years ago?).

Are the modem's ping spikes to blame for the jitter, and if so, what options do I have to remedy that?

Shaw_Alex
Official Shaw Rep
join:2010-12-16

Shaw_Alex

Member

If you send me your account number, I'd like to send it to our network team to look into on our end.
Shaw_Alex

Shaw_Alex to Name

Member

to Name
Try using a different Ethernet cable directly to the modem. The ping to the modem should be under 1ms, and you are getting average 14ms.

If that doesn't work, we could try putting the modem in bridge mode and going from there.
Name3
join:2013-05-28

Name3

Member

I was using a ~50' Ethernet cable - moved a laptop to the modem and used a short cable, no change. Min 1ms, Max 32ms, Avg 14ms.
Name3

Name3 to Name

Member

to Name
Well, my pings were even worse last night. I can't believe Shaw would be congested at 3am on a Wednesday morning. The upgrades for this area are supposed to be COMPLETED as of more than a month ago.

Pinging google.ca [173.194.33.31] with 32 bytes of data:
Reply from 173.194.33.31: bytes=32 time=51ms TTL=56
Reply from 173.194.33.31: bytes=32 time=62ms TTL=56
Reply from 173.194.33.31: bytes=32 time=50ms TTL=56
Reply from 173.194.33.31: bytes=32 time=40ms TTL=57
Reply from 173.194.33.31: bytes=32 time=327ms TTL=56
Reply from 173.194.33.31: bytes=32 time=95ms TTL=56
Reply from 173.194.33.31: bytes=32 time=234ms TTL=56
Reply from 173.194.33.31: bytes=32 time=37ms TTL=57
Request timed out.
Reply from 173.194.33.31: bytes=32 time=39ms TTL=56
Reply from 173.194.33.31: bytes=32 time=64ms TTL=57
Reply from 173.194.33.31: bytes=32 time=160ms TTL=57
Reply from 173.194.33.31: bytes=32 time=215ms TTL=56
Reply from 173.194.33.31: bytes=32 time=184ms TTL=56
Reply from 173.194.33.31: bytes=32 time=40ms TTL=57

Ping statistics for 173.194.33.31:
Packets: Sent = 15, Received = 14, Lost = 1 (6% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 327ms, Average = 114ms
Control-C

jtl999
join:2012-11-24
canada

jtl999 to Name

Member

to Name
Heres a suggestion. Run a smokeping at »/smokeping and post the link here so e can see the latency of your connection over a period of time. I'm interested at the results.
Name3
join:2013-05-28

Name3

Member

»/r3/sm ··· 22adf187
Name3

Name3 to Name

Member

to Name
It's been well over a month since my first post. No change whatsoever.

Ping statistics for 173.194.33.31:
Packets: Sent = 56, Received = 56, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 1169ms, Average = 173ms

Speedtest shows 234ms / 0.65 down / 2.35 up
Paying for 25 down.

kevinds
Premium Member
join:2003-05-01
Calgary, AB

kevinds

Premium Member

Does pinging your modem still average 14?
Name3
join:2013-05-28

Name3

Member

15 today.

Modem:
Approximate round trip times in milli-seconds:
Minimum = 4ms, Maximum = 27ms, Average = 15ms

kevinds
Premium Member
join:2003-05-01
Calgary, AB

kevinds

Premium Member

I just did a few hundred to mine, 1ms min 2 ms max 1 ms average
adiabatic
join:2009-01-24
Victoria, BC

adiabatic to Name3

Member

to Name3
said by Name3:

It's been well over a month since my first post. No change whatsoever.

Ping statistics for 173.194.33.31:
Packets: Sent = 56, Received = 56, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 37ms, Maximum = 1169ms, Average = 173ms

Yeah, that ain't good. To that same IP from my laptop using wifi and through the router to modem:
Ping statistics for 173.194.33.31:
Packets: Sent = 25, Received = 25, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 11ms, Maximum = 18ms, Average = 12ms

rustydusty
join:2009-09-29
Red Deer County, AB

rustydusty to Name

Member

to Name
Is modem bridged? Modem swap maybe
Name3
join:2013-05-28

Name3 to kevinds

Member

to kevinds
Thanks. I'd hate to trouble the service techs with a useless trip if the problem is /not/ the modem, but if you're getting 1ms-2ms, perhaps it's worthwhile.

Of course I doubt that will solve the extreme ping to Google/everything else (Shaw's pretty much horrible around here), but at least I might be able to use the internet at 3am without so much jitter.

Those Motorola modems don't act as routers. They have one ethernet out and no wifi. Using a switch to connect multiple computers, they do not provide network IPs via DHCP. If bridging is still technically possible despite that, it probably wasn't done.

kevinds
Premium Member
join:2003-05-01
Calgary, AB

kevinds

Premium Member

The Motorola modems are permanently 'bridged' they have no other modes...

rustydusty
join:2009-09-29
Red Deer County, AB

rustydusty to Name

Member

to Name
Didn't even see the D2 modem mentioned, my apologies. I would swap the modem for sure, get levels checked before and after as well. Shaw Alex can help with that.

kevinds
Premium Member
join:2003-05-01
Calgary, AB

kevinds

Premium Member

I only saw it once, when he mentioned pinging the modem's IP.
Name3
join:2013-05-28

Name3 to rustydusty

Member

to rustydusty
I sent him a message ~10 days ago, but have yet to receive a response. Hopefully that means he's busy looking into it.
Name3

Name3 to Name

Member

to Name
Still no response from Shaw_Alex. I contacted support, and they eventually said the jitter at all times of day is a problem on their end. Terrible daytime pings (today averaging ~1500ms) is congestion, and again a problem on their end. They have no ETA available as to when it'll be fixed. Just FYI if anyone else is following this thread.
Name3

Name3 to Name

Member

to Name
And now there's been a massive packet loss after 5-6pm every day since Monday.

Request timed out.
Request timed out.
Reply from 173.194.33.63: bytes=32 time=40ms TTL=56
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 173.194.33.63: bytes=32 time=102ms TTL=57
Reply from 173.194.33.63: bytes=32 time=74ms TTL=56
Reply from 173.194.33.63: bytes=32 time=68ms TTL=57
Reply from 173.194.33.63: bytes=32 time=41ms TTL=56
Request timed out.
Request timed out.
Reply from 173.194.33.63: bytes=32 time=72ms TTL=56
Reply from 173.194.33.63: bytes=32 time=42ms TTL=56
Reply from 173.194.33.63: bytes=32 time=41ms TTL=56
Request timed out.
Reply from 173.194.33.63: bytes=32 time=97ms TTL=56
Reply from 173.194.33.63: bytes=32 time=66ms TTL=57
Reply from 173.194.33.63: bytes=32 time=58ms TTL=56
Reply from 173.194.33.63: bytes=32 time=40ms TTL=57
Request timed out.
Reply from 173.194.33.63: bytes=32 time=37ms TTL=56
Request timed out.
Request timed out.
Reply from 173.194.33.63: bytes=32 time=93ms TTL=56

Ping statistics for 173.194.33.63:
Packets: Sent = 218, Received = 103, Lost = 115 (52% loss),
Approximate round trip times in milli-seconds:
Minimum = 36ms, Maximum = 153ms, Average = 62ms

Really, why can't Shaw get their act together?

Shaw_Alex
Official Shaw Rep
join:2010-12-16

Shaw_Alex

Member

We need to have a service call to get your levels fixed. Contact an agent via phone or online chat to have someone come to your house.