Tracert to NA server

Hostee · April 2018

Can someone help me decipher these tracert results to the NA server? I’ve been having more than usual lag in PvE content. Thank you!

Log by iNetTools - Best Network Diagnose Tools on iPhone and iPad.

traceroute to 198.20.198.110 (198.20.198.110) , 5 relative hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 8.818 ms 13.573 ms 14.543 ms
2 10.159.128.1 (10.159.128.1) 9.493 ms 13.356 ms 14.491 ms
3 172.30.4.45 (172.30.4.45) 9.378 ms 16.623 ms 21.197 ms
4 po20.demia001cr1.mchsi.com (68.66.72.101) 21.988 ms 47.645 ms 49.417 ms
5 po11.stlmo001cr1.mchsi.com (68.66.72.61) 22.289 ms 46.841 ms 47.921 ms
6 po10.stlmo001er1.mchsi.com (68.66.73.105) 21.783 ms 45.964 ms 46.996 ms
7 stlo-b1-link.telia.net (213.248.85.84) 21.572 ms 47.278 ms 49.508 ms
8 kanc-b1-link.telia.net (62.115.113.179) 27.155 ms 940.492 ms 943.562 ms
9 sjo-b21-link.telia.net (213.155.132.180) 65.854 ms 225.482 ms 231.110 ms
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

Elsonso · April 2018

Hostee wrote: »

Can someone help me decipher these tracert results to the NA server? I’ve been having more than usual lag in PvE content. Thank you!

traceroute to 198.20.198.110 (198.20.198.110) , 5 relative hops max, 52 byte packets
1 192.168.1.1 (192.168.1.1) 8.818 ms 13.573 ms 14.543 ms <---- YOU
2 10.159.128.1 (10.159.128.1) 9.493 ms 13.356 ms 14.491 ms <---- PRIVATE NETWORK
3 172.30.4.45 (172.30.4.45) 9.378 ms 16.623 ms 21.197 ms <---- PRIVATE NETWORK
4 po20.demia001cr1.mchsi.com (68.66.72.101) 21.988 ms 47.645 ms 49.417 ms <---- Des Moines? MediaCom
5 po11.stlmo001cr1.mchsi.com (68.66.72.61) 22.289 ms 46.841 ms 47.921 ms <---- St Louis MediaCom
6 po10.stlmo001er1.mchsi.com (68.66.73.105) 21.783 ms 45.964 ms 46.996 ms <---- St Louis MediaCom
7 stlo-b1-link.telia.net (213.248.85.84) 21.572 ms 47.278 ms 49.508 ms <---- St Louis TeliaNet
8 kanc-b1-link.telia.net (62.115.113.179) 27.155 ms 940.492 ms 943.562 ms <---- Kansas City TeliaNet
9 sjo-b21-link.telia.net (213.155.132.180) 65.854 ms 225.482 ms 231.110 ms <---- St Joseph? TeliaNet
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *

At Step 9, I am guessing that this is St Joseph MO, based on the proximity to Kansas City and the likelyhood that it is passing to a different provider.

At Step 10, the nodes on the route stop responding to the trace route. The route has passed into a network provider that does not supply this information.

At Step 7->8 you are getting some wildly long ping times. If I had to guess, I would say that one of those two nodes on the internet is congested and not up to the traffic demands, is failing, or the cable between them is not large enough for the traffic.

In general, I am also not pleased with how well MediaCom is passing your traffic through Iowa and into Missouri.

I would say the main problem is TeliaNet.

Hostee · April 2018

Thank you very much for the detailed explanation and the time it took to write this up. It’s very much appreciated. Mediacom is not the best isp by far but unfortunately it’s the only option I have for a high speed connection. The only other option is DSL and that just won’t cut it.
You answered all the questions I had, as to whether the lag was something on my end or a routing issue with the traffic itself. There’s pretty much nothing I can do about that servers congestion or mediacom’s routing. I could call mediacom but I’m sure we both know how far that will get me.