-- There is a black coaxial cable that comes in a hole in...

[mdk]

@dietpepsirocks -- There is a black coaxial cable that comes in a hole in my wall, and I think it goes outside. 

Yikes! What a sloppy installation!  The technician who did that installation should have terminated that coaxial-cable with one of those wall-plates.

Since you do have a technician coming to your home, get they to trace the other end of the coaxial-cable, which should terminate at the Shaw "demarcation box". They can unlock the box, chop-off a few centimeters of the cable, and then put a new connector onto that cable, and reconnect the cable. Then, unscrew your end of the coaxial-cable from your cable-modem, and push the cable through the hole, to the outside wall. Then, the technician can replace the connector, and push it back through the hole, so that you can reconnect it to your cable-modem.  The technician does not need to enter your residence -- maintaining physical separation.

Also, while the technician is "inside" the demarcation-box, they can replace any coaxial-splitter, under the assumption that a different splitter might improve your connection.

Or, a more-drastic attempt would be for the technician to totally replace that "outside" coaxial-cable, in case there is something wrong (kinked, frayed) somewhere on the length of that coaxial-cable.

You've replaced the cable-modem. So, you can rule-out the possibility that the problem is associated with either cable-modem.

To repeat, hold-down the "Windows" key (bottom left of your keyboard). Touch/release the "R" key. Release the Windows key. Into the small box that has opened, type CMD and press Enter. A black-background window will open. As @shaw-tony suggested, type TRACERT TWITCH.TV and press Enter. The output will show the number of milli-seconds it takes to get to each router on the "path" from your computer to Twitch, as well as displaying the IP-address of each router. In this case, the "timing" values are more important than the IP-addresses. Sample output:

$ tracert twitch.tv

Tracing route to twitch.tv [151.101.130.167] over a maximum of 30 hops:

  5    22 ms    11 ms    13 ms  rc1wt-be40.wa.shawcable.net [66.163.68.18]
  6     *        *        *                  Request timed out.
  7    11 ms    11 ms    10 ms  151.101.130.167

There are 3 attempts to get each router to respond. For me, the values are "tiny" -- almost no delay going from BC to Washington State.  What are your values?

[mdk]

@dietpepsirocks -- I can watch streams on Twitch.tv  .... even though the download is slower ...

If you are watching a "live" stream, not downloading all of it for later offline viewing, even one of the "great-grandfathered" Shaw Internet packages, such as "Internet 10" (yes, "ten") will be fast-enough to watch a "live" stream.  So, if you have "Internet 600" or "Fibre+ Gig", then only a few percentage-points of the potential speed will be sufficient for your viewing.

[dietpepsirocks]

Let me just post this here for you its from Ookla and I did some Single Test server results to close locations, a few were ok but look at these ones

[dietpepsirocks]

here

[dietpepsirocks]

What I'm saying is...

OK, so it seems my upload is screwed in more places than just twitch, like give me a real world situation where I upload and I think it will do the same thing as Twitch.

And yes, I understand I'm downloading to watch live and I only need like 10 download to watch.  I'm saying will these tracert things show a problem with upload or just download if theres an issue?

Also, on my Streamlabs OBS, I have tried other servers in the US and in Canada to connect to while uploading my stream.  I'll take a picture to show you, but all the servers I tried had the same uploading problem.

[dietpepsirocks]

two more tracerts

[dietpepsirocks]

Here, in this pic you can see the server I'm streaming to, to test my stream...

[dietpepsirocks]

I have got some new information.

Some IT guy suggested I compare my Upstream in the Shaw Network Modem to someone elses on the Shaw network, because he said my Up stream numbers look suspiciously low and outdated, compared to my upload ones.  He says he thinks they are pushing the wrong profile to my modem.

[mdk]

@dietpepsirocks -- those 3 "traceroute" reports show slightly-large numbers for the "hop" between Winnipeg and Calgary, but there is nothing that you can do about it -- it is something for Shaw Engineering to investigate.

Here is trace "from west to east" to Winnipeg:

  4    16 ms    11 ms    10 ms  rc1bb-be20.vc.shawcable.net [66.163.75.245]
  5    13 ms    21 ms    16 ms  rc1st-be25.vc.shawcable.net [66.163.69.198]
  6    26 ms    26 ms    25 ms  rc3no-be11-1.cg.shawcable.net [66.163.72.69]
  7    43 ms    44 ms    41 ms  rc2nr-be108-1.wp.shawcable.net [64.59.180.109]

Again, just "slightly" large timings between Calgary & Winnipeg.

>  He says he thinks they are pushing the wrong profile to my modem.

You could ask Shaw to "reprovision" your modem.

What does a test using Shaw Speed Test show for download/upload speeds, before you ask Shaw, and later, after Shaw has reprovisioned it?

Do you have any other active coaxial-cables coming into your home?  If so, connect your cable-modem to that cable, and your computer (and its Ethernet cable) to your cable-modem, and repeat the Shaw Speed Test.

Do you have a friend who uses Shaw? Can you connect your computer to their cable-modem, via your Ethernet cable, and repeat the Shaw Speed Test? Same numbers?

Can you connect your computer to their cable-modem, via their Ethernet cable, and repeat the Shaw Speed Test? Same numbers?

[rstra]

@dietpepsirocks Your signal levels are fine.