Shaws connection to Twitch Servers is terrible!

[shaw-tony]

 ah, that is frustrating. I haven't heard of any other reports of issues with Twitch at this time. We do work with them to ensure there are no routing problems. It may just be a limitation set from Twitch depending on the user.

[s2celerity]

There related post below this that have had the issue for years and I have as well since 2017 when I moved into a house with Shaw internet

why would twitch limit specific users bitrates? Especially even ones who are direct partners of them, I’ve seen twitch partners posting on twitter not 1 month ago on a Shaw post from 2015 about issues with Shaw to twitch servers saying they still are having these issues

People are probably tired of reporting it over and over again or switched ISP after so many years of this issue is why you haven’t heard anything most likely 

I have 15-20mbps upload I should get at least 6-8k bitrate to twitch

i don’t understand how this is such a big deal to sort out 

[s2celerity]

Any response from twitch on your end? Please contact them or get a higher up to, this is still a daily thing happening

You say you guys deal with twitch directly but have seen no improvement in speed to the servers, same thing every day

ive been the only one home this whole week and can tell you that there is nothing else using the upload speed

i would like at least 10mbps connection to twitch so it can be at a decent quality (6-8k bitrate) 

this is utterly ridiculous going on 5 years now since I’ve seen complaints and nothing getting resolved 

[shaw-tony]

s2celerity I haven't received any updates yet. Please run and report a WinMTR to the twitch server you connect to along with the Twitch analyzer data.

[s2celerity]

so this is the main server i use, seattle, wa

Tracing route to live-sea.twitch.tv [52.223.228.14]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 27 ms 10 ms 8 ms 70.75.64.1
3 17 ms 17 ms 14 ms rc3no-tge0-11-0-35-1.cg.shawcable.net [64.59.132.77]
4 32 ms 30 ms 30 ms rc2wt-be100.wa.shawcable.net [66.163.75.233]
5 reserved.justin.tv [192.16.68.164] reports: Destination net unreachable.

Here is the bitrate test currently, as you can see its poop even tho this is by far the best server available to me

This is just a test with the other servers as well, Portland is usually my second go to if seattle is down

These are my multi and single threaded speeds at the time as well

[shaw-tony]

 thanks for the info, I've passed the details along.

[s2celerity]

C:\Users\commo>ping live-sea.twitch.tv

Pinging live-sea.twitch.tv [52.223.228.14] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 52.223.228.14:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

C:\Users\commo>ping live.twitch.tv

Pinging live-pdx.twitch.tv [52.223.225.161] with 32 bytes of data:
Reply from 192.16.68.164: Destination net unreachable.
Request timed out.
Request timed out.
Reply from 192.16.68.164: Destination net unreachable.

Ping statistics for 52.223.225.161:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

Seems to be some packet loss as well when i try to ping these servers, hope this helps

[s2celerity]

This is running a hotspot from my phone which yielded better results....

[s2celerity]

Hey just wondering if there was any word back yet on these issues

[shaw-tony]

Hey @s2celerity, no word back yet. I've reached out to our engineer for an update.