-- Here's that tracert result Sigh. Those are IPv6 addres...

[mdk]

@miX_ -- Here's that tracert result

Sigh. Those are IPv6 addresses, which are more difficult to analyze.

Can you change the settings on your computer's network adapter to temporarily disable IPv6, leaving only the IPv4 protocol as the active protocol, and rerun the TRACERT ?

[rstra]

@mdk Not all addresses have the 100 up yet and they mentioned Saskatoon in their post, which only has 25 up.

[miX_]

@mdk 

Tracing route to e13678.dscb.akamaiedge.net [72.247.170.32]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 10.0.0.1
2 12 ms 12 ms 11 ms 70.64.64.1
3 15 ms 12 ms 14 ms rd4ha-be103-1.ss.shawcable.net [64.59.181.37]
4 15 ms 11 ms 16 ms rd3ha-be1.ss.shawcable.net [66.163.73.21]
5 19 ms 25 ms 20 ms rc3sc-be7.wp.shawcable.net [66.163.73.209]
6 34 ms 35 ms 34 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134]
7 39 ms 35 ms 34 ms ae18.cr9-chi1.ip4.gtt.net [209.120.141.213]
8 36 ms 33 ms 33 ms ip4.gtt.net [98.124.183.18]
9 40 ms 32 ms 34 ms ae13.r01.ord01.icn.netarch.akamai.com [23.207.231.38]
10 68 ms 59 ms 60 ms ae3.r02.yto01.icn.netarch.akamai.com [23.32.63.111]
11 60 ms 89 ms 76 ms ae2.r01.yto01.ien.netarch.akamai.com [23.203.148.37]
12 56 ms 123 ms 96 ms ae2.torix-yto.netarch.akamai.com [23.203.148.129]
13 75 ms 57 ms 53 ms a72-247-170-32.deploy.static.akamaitechnologies.com [72.247.170.32]

[miX_]

@dietpepsirocks 

Upload - 3.3 Mbps
Down - 319Mbps
Latency - 42ms
Packet Loss - 0.0%
Jitter - 0.7ms

[mdk]

@miX_ -- it seems that the DNS-servers for Microsoft give "regional" results.

So, for me:

$ tracert  www.microsoft.com

Tracing route to e13678.dscb.akamaiedge.net [23.11.242.9]

  4    11 ms  rc1bb-be20.vc.shawcable.net [66.163.75.245] -- Vancouver
  5    17 ms  rc3ar-tge0-6-0-16.ed.shawcable.net [66.163.76.42] -- Edmonton
  6     9 ms  a23-11-242-9.deploy.static.akamaitechnologies.com [23.11.242.9] -- presumably Edmonton

For you:

Tracing route to e13678.dscb.akamaiedge.net [72.247.170.32]

 1  1 ms 10.0.0.1 -- your BlueCurve
 2 11 ms 70.64.64.1 -- Shaw router in your city
 3 14 ms rd4ha-be103-1.ss.shawcable.net [64.59.181.37] -- Shaw Saskatoon
 4 16 ms rd3ha-be1.ss.shawcable.net [66.163.73.21] -- Shaw Saskatoon
 5 20 ms rc3sc-be7.wp.shawcable.net [66.163.73.209] -- Shaw Winnipeg
 6 34 ms rc4ec-be25-1.il.shawcable.net [66.163.75.134] -- Shaw cross-over in ILLINOIS
 7 34 ms ae18.cr9-chi1.ip4.gtt.net [209.120.141.213] -- GTT in Chicago
 8 33 ms ip4.gtt.net [98.124.183.18] --
 9 34 ms ae13.r01.ord01.icn.netarch.akamai.com [23.207.231.38] -- ORD (Chicago airport)
10 60 ms ae3.r02.yto01.icn.netarch.akamai.com [23.32.63.111] --
11 76 ms ae2.r01.yto01.ien.netarch.akamai.com [23.203.148.37] --
12 56 ms 123 ms 96 ms ae2.torix-yto.netarch.akamai.com [23.203.148.129] -- Toronto Internet Exchange ?
13 75 ms 57 ms 53 ms a72-247-170-32.deploy.static.akamaitechnologies.com [72.247.170.32] -- Microsoft's collocated server

Those are OK response-times for each router in the path. Obvioiusly, there is a lot of traffic between Winnipeg and Illinois -- Shaw only has a few "cross-border" paths.

Could you try: TRACERT 23.11.242.9 

That should route from Saskatoon to Edmonton, but, unfortunately, it won't give any useful information to explain your "slow" speeds:

Upload - 3.3 Mbps
Down - 319 Mbps

I presume that you have an Ethernet cable between your computer and your cable-modem, that is you are not measuring using WiFi to connect to your cable-modem.

Try the Shaw Speed Test to get a good measurement of the "best" speed in-and-out of your cable-modem to a "local-to-you" Shaw server.

I recommend that you contact Shaw, and get the Shaw Agent to remotely logon to your BlueCurve, to view the "signal strength" reaching your cable-modem, and other values. Something is not right, and I doubt that the problem is your computer, or your Ethernet cable. It is also unlikely that it is a problem with your BlueCurve, but, to be sure, disconnect the electrical power from the BlueCurve, wait a few seconds, and reconnect the power, and let it fully restart. Then, rerun the Shaw Speed Test.

[dietpepsirocks]

Big surprise.

I have argued with these Network guys before about the speed tests they send me to, not being reflective of reality.  The one I sent you accurately diagnosed my real world upload just like it did for you right now.

But these guys dont learn.  I believe it was "mdk" here arguing with me in the past about this.

Well here you go, more evidence that other speed tests are more accurate in real world situations than others.  Maybe you should begin believing me on this huh mdk?

[dietpepsirocks]

mix_

Google inspector Twitch TV, follow the guidelines on how to connect to a test server and let it run for a 24 hour period, if you cant do that let it go for a few hours at least and collect data on the upload to that particular server.  There are other ways you can also connect to many other server(s) across the country, and even in other countries to rule out that its not a problem with a specific server.

Heres the problem I'm having over a ~22 hour period so far, we can see at what times its worse than others and with this type of information an engineer at Shaw should be able to look into the node to see whats going on around these times

The red lines are the times where its REALLY bad.  Where you see the "fuzzy lines" it doesn't look so bad on the graph, but when you translate it into how it works in reality on a live stream, its actually pretty bad.  Where it isn't fuzzy, its pretty good.

Just 2 weeks ago, this graph was literally about 500% worse before the engineer I was in contact with found a problem within the node (yet again) but its still not fixed.  Its better than it was, but still not fixed.

[miX_]

I've done the Shaw Speed Test, testmy.net/upload, speedof.me, and the one linked by @dietpepsirocks . The Shaw one fluctuates with results between 8megabits and 18megabits. Testmy.net/upload shows 1.5megabits pretty consistantly, and speedof.me shows somewhere around 3 - 4megabits..

Here's the tracert you asked for;

Tracing route to a23-11-242-9.deploy.static.akamaitechnologies.com [23.11.242.9]
over a maximum of 30 hops:

1 1 ms <1 ms 1 ms 10.0.0.1
2 14 ms 14 ms 10 ms 70.64.64.1
3 13 ms 12 ms 12 ms rd4ha-be103-1.ss.shawcable.net [64.59.181.37]
4 19 ms 17 ms 17 ms rc2ar-be50.ed.shawcable.net [66.163.73.30]
5 17 ms 18 ms 19 ms rc2we-be7.ed.shawcable.net [66.163.70.129]
6 24 ms 20 ms 18 ms rc3no-be6.cg.shawcable.net [66.163.64.69]
7 38 ms 33 ms 31 ms rc1st-be11-1.vc.shawcable.net [66.163.72.70]
8 40 ms 39 ms 45 ms rc1bb-be25.vc.shawcable.net [66.163.69.197]
9 43 ms 43 ms 42 ms rc3ar-tge0-6-0-16.ed.shawcable.net [66.163.76.42]
10 37 ms 37 ms 37 ms a23-11-242-9.deploy.static.akamaitechnologies.com [23.11.242.9]

[miX_]

@dietpepsirocks Thanks, I'll try running that overnight. Very good looking tool. I'm jealous of your average, my peak is your minimum.

[dietpepsirocks]

My "average" makes no difference right now.  Its stability is garbage, the stream lags constantly regardless.  There is a problem in the node for you, I'm sure of it.  Its just like mine, theres something wrong with the node, it always seems to be the issue.  There are too many people that dont understand how many different problems can arise in the node and its ignored way too often.  I'm yet again, for the 4th time trying to convince Shaw theres a problem with their internet.

If it gets fixed again and gets bad again, I'm so done with Shaw forever.  Problem is Bell wont have their high speed here for probably another year in my area.