thank you. it's very frustrating when i'm trying to stream, i pay for the best package they offer and i'm constantly hearing "everything looks good on our end" or "you're expereincing issues due to covid and people working from home" but my internet prices are the same and it's not working for what i'm trying to do. it's starting to sound more like an excuse and it's never getting fixed.
Yes, that's because they have ICMP traffic ignored.
that will not give you any usefull data. Since ICMP is dropped at the destination you can't tell if the routers on the way simply depriorize ICMP or if there is real packetloss. Also since async routing is the norm today you would have to do that from twitch to your homerouter too at the same time. So this complete test helps nothing.
That's incorrect. Pingplotter tracks the ping to each individual node in the route path, not just to the final node itself. You absolutely can and will see packet loss to each node, as well as a ping timing spread that can heavily suggest which hop in the route is having a problem, if it's an issue somewhere in your routing path to the destination.
Yes please do so to you.
I was a network engineer for 10 years, working on-site deployments, troubleshooting, and in NOCs.
Again, this is NOT USING TRACEROUTE. I'd recommended a separate tool called Pingplotter, which pings each host in the route individually, tracking response time spread and packet loss of the traffic to/from each individual node over time, NOT only to the endpoint. This allows rough-identifying a problem node on a routing chain, even if the final hop has ICMP traffic black-holed, as intermediary links with issues will generally show problems with returning signaling responses, as well as routing traffic.
Not your fault at all, man. Don't worry about it. :)
Man what do you thing traceroute does? Excatly the same without doing it over time.
It does not
Yes it makes it very clear that YOU don't have any knowledge of the topic and try to shutup others so your lack of knowledge doesn't get exposed.
Exactly. Traceroute does it three times per hop. It does not aggregate data on each node over time, which is what makes PP useful as a diagnostic tool separate from traceroute, and is exactly the thing that can point out a problem node. It's why Pingplotter exists, and why network professionals use it instead of just whacking traceroute at the problem.
Did you run Pingplotter as advised? Do you have a screenshot of it from your connection? Again, that's the first step, seeing where the problem is actually occurring in the chain.
