December
Each host displays a node and from each node they'll need to route you from point A which is your ISP to point b then to point c (point b can be a representation of how many nodes it will take to reach point c which is us). It appears that you're getting network issues at the following host:
GTD-THMN-R2.bb.telus.com - This is where you lost connection overall.
This is the so called issue, I've talked with supports for the said server (League of legends) and they are telling me the issue is on telus's side or my home network and that I'd need to call support but I don't know how to explain the issue I also have WinMTR logs that could help understand.
December
What is the actual issue you are experiencing? No connection to the game server? Latency issues? Please provide more specific details and post the WinMTR results.
December
192.168.1.254 - 0 | 129 | 129 | 0 | 0 | 9 | 1 |
| 10.145.114.1 - 0 | 129 | 129 | 1 | 2 | 29 | 2 |
| GTD-THMN-R2.bb.telus.com - 0 | 129 | 129 | 26 | 27 | 43 | 27 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 26 | 0 | 0 | 0 | 0 | 0 |
those are the results and I am experiencing latency issues
December
What is the server IP you are trying to connect to? The response from the last Telus hop shows normal latency. Additionally, the various hops along the path that do not show a ping response are normal. That's how most connections will look. It does not mean that the connection just stops at the last hop showing a ping response.
Are you connecting through wifi or ethernet? Wifi can introduce additional latency, especially if there are environmental factors in your home that cause interference.
Here's my MTR to LoL US server (IP: 104.160.131.3):
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| 192.168.1.254 - 0 | 20 | 20 | 0 | 1 | 3 | 1 |
| 10.137.48.1 - 0 | 20 | 20 | 1 | 3 | 7 | 3 |
| 154.11.15.196 - 0 | 20 | 20 | 26 | 27 | 29 | 26 |
| six1.riotgames.com - 0 | 20 | 20 | 23 | 24 | 26 | 23 |
| hu-0-0-0-4.er01.pdx03.riotdirect.net - 0 | 20 | 20 | 50 | 52 | 59 | 59 |
| ae1.er02.pdx03.riotdirect.net - 0 | 20 | 20 | 47 | 48 | 51 | 48 |
| hu-0-0-0-8.er02.sjc01.riotdirect.net - 0 | 20 | 20 | 51 | 52 | 54 | 51 |
| ae1.er01.sjc01.riotdirect.net - 0 | 20 | 20 | 51 | 52 | 54 | 51 |
| ae2.er01.lax01.riotdirect.net - 0 | 20 | 20 | 50 | 51 | 53 | 51 |
| 104.160.141.51 - 0 | 20 | 20 | 47 | 48 | 50 | 48 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 4 | 0 | 0 | 0 | 0 | 0 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2
December
192.64.173.51 is the server I'm trying to connect to
I'm connected wired
December
That server is in California. That IP comes up having issues with AT&T and Comcast users also, though it is not a common IP that appears. Which game are you playing? Riot's had ongoing issues for quite some time. They seem to be obscuring the path to that IP no matter which ISP I test from in Canada or the US.
December
League of legends, I've contacted their supports and they assured me their servers had no issue and my ISP would be my best bet
December
Also may I add that some of my friends which are with telus aswell in canada are having the same issue as me? All started about 2 months ago around 10 october