Discussion de forum
High ping / packet loss after 4pm
Hi, I've been experiencing really bad ping times and packet loss recently. But the thing is it only happens around 4pm. (When people in my neighborhood start using the internet.) I ran a few WinMTR t...
I see no real packet loss on your first screenshot. The 4th router does not answer to all the ping requests probably because it prioritizes the normal packets over the ping requests so it chooses not to answer your pings. If there was a problem there we would also see packet loss and constant high ping averages to all the other routers after it.
The second one however is very weird once you get to the Riot games network. We see the same routers many times in the route like they are going back and forth with your packets : er01, er02, er01, er02.... It looks like a routing problem on thier side.
I'm having issues with the "modem.cable" ip, which I'm guessing is my neighborhood's node. During the day it's absolutely fine but during the evening it gets super laggy and I can't play online games without constantly lagging.
So what you're saying is, the node isn't answering to my ICMP requests because it's overloaded?
That's exactly my point, if my node is overloaded can't it be upgraded or something?
Bell just installed Fiber Optic in my neighborhood anyways so I probably will switch to Bell if I can't get this issue resolved.
I just want to be able to play Call Of Duty without rubber banding all over the **blip** place.
However, even if you modem had a ping under 20 ms, that would not fix the problem with the riotgames routers. I seem to have the same weird routing with riotgames as you. I'm not sure if Videotron can do anything about that since it's far outside the Videotron network.
Here's my traceroute to 104.160.131.1 :
WinMTR statistics
Host Loss % Sent Recv Best Avrg Wrst Last 10.0.0.1 0 53 53 1 2 8 2 modemcable000.000-000.000.mc.videotron.ca 0 53 53 9 14 22 17 10.170.193.82 0 53 53 10 16 25 18 216.113.126.234 0 53 53 17 23 32 18 riotgames.torontointernetxchange.net 67 15 5 28 35 41 28 ae1.er01.chi01.riotdirect.net 50 18 9 0 32 41 28 ae1.er02.chi01.riotdirect.net 72 14 4 0 34 35 35 ae1.er01.chi01.riotdirect.net 67 15 5 34 36 39 39 No response from host 100 11 0 0 0 0 0 ae1.er01.chi01.riotdirect.net 60 15 6 0 36 41 36 ae1.er02.chi01.riotdirect.net 84 12 2 0 36 37 37 ae1.er01.chi01.riotdirect.net 50 18 9 0 34 38 37 ae1.er02.chi01.riotdirect.net 60 15 6 0 32 36 36 ae1.er01.chi01.riotdirect.net 57 16 7 0 33 39 27 ae1.er02.chi01.riotdirect.net 67 15 5 0 33 37 28 ae1.er01.chi01.riotdirect.net 67 15 5 28 32 36 29 ae1.er02.chi01.riotdirect.net 84 12 2 0 32 35 35 ae1.er01.chi01.riotdirect.net 50 18 9 0 34 43 37 ae1.er02.chi01.riotdirect.net 91 11 1 0 34 34 34 ae1.er01.chi01.riotdirect.net 72 14 4 0 31 37 37 ae1.er02.chi01.riotdirect.net 84 12 2 35 35 36 35 ae1.er01.chi01.riotdirect.net 67 15 5 0 34 38 35 ae1.er02.chi01.riotdirect.net 72 14 4 0 37 43 36 ae1.er01.chi01.riotdirect.net 53 17 8 0 32 39 34 ae1.er02.chi01.riotdirect.net 84 12 2 36 39 43 43 ae1.er01.chi01.riotdirect.net 72 14 4 0 35 37 37 ae1.er02.chi01.riotdirect.net 57 16 7 0 32 43 35 ae1.er01.chi01.riotdirect.net 72 14 4 0 32 36 35 ae1.er02.chi01.riotdirect.net 77 13 3 0 35 37 35 ae1.er01.chi01.riotdirect.net 91 11 1 0 34 34 34
