That strange issue with the internet that took three years to fix
That strange issue with the internet that took three years to fix
Yes, when you are testing an upload problem while streaming, this step helps rule out whether it's the computer or router/modem that is broken. Lowering the stream resolution (like going from 720p to something lower) was just a way to check how fast your network handles the data. This isn't meant to force you to use those low settings permanently; instead, it acts like background traffic along with ping tests to add load to your devices and see which one slows down first or drops out at what speed. As a side experiment for fun, what does speedtest.net say about your internet speeds?
I told you, this upload trouble shows up on lots of places like twitch, testmy.net, OBS, and other tools. I tried switching servers but the same glitch kept happening. How can everyone blame all these different apps instead of fixing it? You say Shaw used to block us for a year because of spikes, then they found the problem and fixed it, making sure 90% of issues were gone. Now it happens again. When we upload to testmy.net, it says 7 Mbps now but back when this started it averaged 35+ Mbps before even getting slow on my big 100 Mbps connection.
speedtest.net shows my speeds as normal. I am shocked because anyone who does tech stuff uses this site. Ookla software eats up 30% of your slowest speeds and uses multithreading to open a second pipe to make internet speed look better while hiding problems in the main line. You connect to local servers that are often sponsored by Ookla and the ISP you use, so they get priority access to these servers. It is the biggest gimmick of a tool you could possibly find on the internet; it is nothing but garbage that actually hides internet problems instead of solving them.
So I will put my idiot ISP hat on now. Please prove that the data that is received by all these programs was actually sent out of your machine correctly. Ie how do you prove that the data was not already damaged before it was even sent out the ethernet port of your machine. Now if there is some kind of test server you could setup in your house that could receive the stream and analyze the data format it would be pretty easy to say see there is no frame loss in the house and this is the same data I am sending outside the house. Until you find someway to basically prove some kind of problem the ISP can correctly say "it is a application issue". Even your own testing shows you only see issues with this one application every test tool you run shows no issues. So me not having use OBS I can't say much. Are there any fake test "streams" where you could play some kind of pre encoded video file so you are not use OBS on live data. In effect you would be uploading a data file just using the transport part of the software rather than the complex encoding. What I would suspect if this is a real network issue it is some kind of hardware/firmware issue in the ISP equipment. This would be similar to the intel PUMA issue years ago in cable modems. There was a bug that pretty much only certain game traffic would hit. No other traffic was affected. There were many more gamers than you have streamers so it was simpler to isolate it to certain models of modems. In this case if the problem is really equipment related it is likely some hardware revision of some board in the ISP equipment where only certain units are affected. I still think your first step is to find a way to confirm that the data is actually correct as it leaves your machine. Then you need to find a way to help the ISP find this. I mean lets say you have 100% access to the ISP equipment what would you check. Just like you know nothing about their equipment they know nothing about data streaming and it really appears it is only that kind of traffic being affected.
so even though it feels like junk software, my results match what testmy.net says. When you use multithreading instead of just one thread at a time, that's not a problem—it just helps find the true speed limit your connection allows, not what you usually get with just one thread. A difference here might mean there are problems on your computer or router that slow things down. By default, it connects to servers right next door. You can pick from a list of places like them too, or search anywhere in the world. My results were the same whether I connected locally or used servers all over Europe and the US, even Shaw in Canada. My goal was to make sure you checked these things: how much data lost when streaming on Twitch with heavy loads versus light ones, to find out your real upload speed, and to figure out the maximum speed your connection can handle. This will also help rule out your computer and router, which are easy places to blame if the internet is slow. But since I know nothing, that's where I'll stop here.