![]() ![]() "Sucks I have to run a home Server over Wifi and using another program to allow me to combine both the connections coming in" ![]() seems to Route the connection differently and I can finally stream again. THE ONLY "FIX" I found is Modem in bridge mode "Residential Gateway". I got the Text this morning with "Ill be honest, im not sure theres much else we can do for you in the house but it will let me verify for the it" Nothing you can do! 40 calls in, 3 Calls with the Office of President. Is anyone else out there experiencing these types of issues uploading to twitch via rogers? Advice on how I can escalate this to an appropriate resource within the support team who will look at it seriously? They just want to replace a modem or close my ticket the next day without any feedback/consent or resolution. Calling front line support doesn't seem to get me anywhere. I'm at the point where I think I'm going to need to change providers. As expected I immediately started to lose frames/packets intermittently through the broadcast, due to insufficient network when I disabled the VPN. Ater a few months of solid streaming through the VPN, I tested again without it. I've been running with the VPN for some time now as a workaround, but it's an additional cost of course, and one I shouldn't need to incur. Without the VPN, I would get frame/packet loss, but with the VPN on, I would have no issue. I streamed my feed to restream.io ( which also uses RTMP) to rule out a rule specific to twitch completely. ( testing to Toronto, NY, Chicago ingests primarily) I can push the Twitch cap of 6000 bps without issue with the VPN enabled. When I use a VPN, and test to any of the ingest servers I had issues with, I get no packet loss or dropped frames to Twitch. This is when I realized, that Rogers may in fact be throttling my RTMP uploads by payload. The issue persists across multiple machines/cables and every Twitch ingest server that I can reasonably test location wise.Īt some point, someone suggested I encapsulate my data by testing with a VPN to the local cities of the ingest servers I was testing. Techs have come and replaced wire and tested to the curb etc. I've been troubleshooting the connection issues streaming to twitch, for almost a year now with support. I get 250 down / 20 up consistently and my upload to Twitch will start to drop frames/packets if I exceed around 3000 bps, which is not even a 1/4 of my upload. I'm curious if any other Twitch broadcasters are experiencing this issue with Rogers. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |