The first screenshot cut off the target, and just had the last responding host.
Yes, again, Twitch ingests have ICMP traffic disabled. They will never respond to a ping or traceroute, though the servers in between will.
Here's one from my system to the ingest I use daily, with 100 Quality:
View attachment 55518
If you have 0 Quality, or anything below 80, your connection and/or ISP has a problem.
You can use a tool like PingPlotter to suggest where the issue is occurring. It will still time out at the final hops due to the ICMP traffic disable on Twitch's end, but if you see a node with a lot of packet loss or variance, chances are good it's causing the issue. But with almost everything sitting at 0 Quality, it's a fair bet that it's your local ISP node, or your connection to that node having the problem.
this is a test with my friend, he has the same provider, the loss goes to live-hou.twitch.tv as I understand the provider has nothing to do with it, or I'm wrongAnswers that. You have almost 50% packet loss on your first hop. That's why your quality is zero. It's your connection to your ISP. That 10.81.0.1 hop or your local LAN on the first at 192.168.0.1
The second screenshot is even worse, at over 70% packet loss. Try rebooting your networking gear (any hubs/switches, your PC, your modem/router) and see if it improves. Otherwise, it's time to yell at your ISP because the connection from the 192.168.0.1 to 10.81.0.1 is where all your problems seem to be coming from, and that's the very first link... as in from your home to your ISP.
The 100% packet loss from your friend's test is reaching the Twitch edge-point where ICMP traffic (pings) are not responded to. Resulting in 100% packet loss at that point. That's expected and totally normal, and will work normally. That's the Twitch servers ignoring ping traffic and not responding to it, as Twitch has set them up.this is a test with my friend, he has the same provider, the loss goes to live-hou.twitch.tv as I understand the provider has nothing to do with it, or I'm wrong
The 100% packet loss from your friend's test is reaching the Twitch edge-point where ICMP traffic (pings) are not responded to. Resulting in 100% packet loss at that point. That's expected and totally normal, and will work normally. That's the Twitch servers ignoring ping traffic and not responding to it, as Twitch has set them up.
On YOUR test, you have between 50-70% packet loss on the first hop. As in, your home connection to your ISP is dropping more than half of the packets it tries to send. Your connection to your ISP is hosed. Whether that's your own hardware, the modem/router, or the line from the modem/router to the ISP's local concentrator node, the problem is with your connection to your ISP. You need to contact your ISP and tell them that you're seeing between 50-70% packet loss on the first hop. They NEED to fix that.
Packet loss on the first hop isn't really a problem if it doesn't continue beyond that. What's your actual upload speed supposed to be? If it's 6mbps then your results look fine, the 0 quality on TwitchTest probably means something interfered with the collecting of stats.