ping

Need help?
Post Reply
User avatar
Mali Mrav
Member
Posts: 296
Joined: Fri Jan 02, 2015 1:53 pm
Contact:
Croatia

ping

Post by Mali Mrav » Sun Oct 09, 2016 5:40 pm

yo trench how to make that treceroute
Silent Assassin

User avatar
Trench
Admin
Admin
Posts: 1570
Joined: Tue May 22, 2012 3:19 am
Location: Dallas / Fort Worth
Contact:
United States of America

Re: ping

Post by Trench » Sun Oct 09, 2016 5:45 pm

Yeah, if your ping is good right now, take a trace route and save the results, so that you can compare it against any worse results in the future, to see if and where a change occurred. On Windows, to invoke a trace route to the EA117 server enter the following command in a Comment Prompt:

tracert.exe 8.12.64.130

If you are currently seeing a high ping, taking a trace route what the problem is happening /might/ show you where the issue is, but you can't really say for sure without having a "good" trace route to compare against. Meaning you might see one or more hops where the ping increases by a significant amount, but you won't know whether that's "normal" or not until you can compare it against a trace route taken when your ping is better.

-Trench

User avatar
Mali Mrav
Member
Posts: 296
Joined: Fri Jan 02, 2015 1:53 pm
Contact:
Croatia

Re: ping

Post by Mali Mrav » Mon Oct 10, 2016 10:08 am

last night was normal 160 to 170


this is trace route

Tracing route to 8.12.64.130 over a maximum of 30 hops

1 2 ms 3 ms 3 ms 192.168.1.1 [192.168.1.1]
2 * * * Request timed out.
3 18 ms 17 ms 18 ms 172.29.33.97 [172.29.33.97]
4 24 ms 28 ms 23 ms gtr11-mzg-dr-10.ip.t-com.hr [195.29.3.46]
5 37 ms 42 ms 42 ms 87.128.238.81
6 43 ms 38 ms 45 ms 217.239.39.254
7 46 ms * * 87.190.232.158
8 41 ms 37 ms 40 ms ffm-bb3-link.telia.net [62.115.141.238]
9 184 ms 127 ms 137 ms nyk-bb2-link.telia.net [213.155.135.63]
10 201 ms 205 ms 200 ms dls-b21-link.telia.net [62.115.137.51]
11 209 ms 167 ms 167 ms vultr-ic-318447-dls-b22.c.telia.net [62.115.149.
45]
12 167 ms 168 ms 169 ms vultr-ic-318447-dls-b22.c.telia.net [62.115.149.
45]
13 175 ms 175 ms 176 ms 8.12.64.130
Silent Assassin

User avatar
Mali Mrav
Member
Posts: 296
Joined: Fri Jan 02, 2015 1:53 pm
Contact:
Croatia

Re: ping

Post by Mali Mrav » Mon Oct 10, 2016 10:15 am

is this good?
do we know where are there going
Silent Assassin

User avatar
Trench
Admin
Admin
Posts: 1570
Joined: Tue May 22, 2012 3:19 am
Location: Dallas / Fort Worth
Contact:
United States of America

Re: ping

Post by Trench » Mon Oct 10, 2016 10:27 pm

My results pinging your IP address last night certainly look the same as yours. Note I'm not coming "from the server", and am in a different geographic location and ISP than the server. But both your result sand my results suggest around ~170ms as the round trip time:
tracert 93.142.166.235 wrote:Tracing route to 93-142-166-235.adsl.net.t-com.hr [93.142.166.235]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms FIOS_Quantum_Gateway.fios-router.home [192.168.1.1]
2 3 ms 4 ms 7 ms xx.xx.xx.xx
3 5 ms 6 ms 6 ms xx.xx.xx.xx
4 3 ms 4 ms 4 ms ae8---0.scr02.dlls.tx.frontiernet.net [74.40.3.25]
5 5 ms 4 ms 7 ms ae1---0.cbr01.dlls.tx.frontiernet.net [74.40.1.82]
6 * * * Request timed out.
7 81 ms 24 ms 24 ms ae-2-3601.edge4.Chicago3.Level3.net [4.69.203.230]
8 26 ms 27 ms 26 ms dtag [4.68.62.222]
9 150 ms 139 ms 139 ms 217.239.48.102
10 154 ms 154 ms 154 ms 87.128.238.102
11 154 ms 196 ms 154 ms mzg-dr-10-gtr11.ip.t-com.hr [195.29.3.45]
12 158 ms 191 ms 164 ms mst-vi-10-mzg-dr-10-2.ip.t-com.hr [195.29.241.246]
So yes, if that was "a good day" for you, I don't see any reason to dispute that. It looks like the ping did hit up closer to 200ms during the traceroute even though it came back down to 170ms before the traceroute finished, so that might be something you're experiencing in play too.

The interesting thing now will be that on a day things seem worse than today, run a traceroute again and see if & where it differs. Meaning do you see some increase in your local hops before even reaching telia.net routers; do you see that the trans-Atlantic hop within the telia.net network simply takes longer, or does the increase not occur until somewhere closer to the final destination.

-Trench

User avatar
Mali Mrav
Member
Posts: 296
Joined: Fri Jan 02, 2015 1:53 pm
Contact:
Croatia

Re: ping

Post by Mali Mrav » Tue Oct 11, 2016 3:14 am

tnx trench will do that when i have big ping
Silent Assassin

User avatar
fromage
Member
Posts: 453
Joined: Sat Nov 26, 2011 3:43 pm

Re: ping

Post by fromage » Sat Oct 15, 2016 11:07 pm

Mali Mrav wrote:tnx trench will do that when i have big ping
Keep your big ping away from Trench. He's not that kind of guy.

User avatar
Mali Mrav
Member
Posts: 296
Joined: Fri Jan 02, 2015 1:53 pm
Contact:
Croatia

Re: ping

Post by Mali Mrav » Wed Nov 02, 2016 9:11 pm

this is from tonight ping 200
no 1 on my internet just pc

1 1 ms 3 ms 1 ms 192.168.1.1 [192.168.1.1]
2 * * * Request timed out.
3 18 ms 16 ms 16 ms 172.29.33.97 [172.29.33.97]
4 24 ms 22 ms 21 ms gdr10-mzg-dr-10.ip.t-com.hr [195.29.241.114]
5 24 ms 23 ms 22 ms te0-7-0-7.rcr21.zag01.atlas.cogentco.com [149.6.
30.17]
6 32 ms 32 ms 32 ms be2594.ccr21.vie01.atlas.cogentco.com [130.117.3
.169]
7 82 ms 31 ms 31 ms ae2.vie20.ip4.gtt.net [141.136.101.237]
8 164 ms 164 ms 164 ms xe-2-0-0.dal20.ip4.gtt.net [141.136.111.58]
9 202 ms 202 ms 201 ms ip4.gtt.net [173.205.43.82]
10 203 ms 204 ms 200 ms 8.12.64.130
Silent Assassin

User avatar
Trench
Admin
Admin
Posts: 1570
Joined: Tue May 22, 2012 3:19 am
Location: Dallas / Fort Worth
Contact:
United States of America

Re: ping

Post by Trench » Wed Nov 02, 2016 10:14 pm

That's interesting. I would say trace it again once you think the ping is "back to normal", and let's see if it has gone back to using telia.net to cross the Atlantic. That's what seems to be primarily different about your current "slow" traceroute, is that even though you're still using your same ISP, the route took you out through a local "cogentco.com" network there in Croatia, and ultimately a gtt.net network to cross the Atlantic.

As opposed to before when the ping was "faster", where you're ISP went out through some unidentified network and ultimately telia.net to cross the Atlantic. It might be "entirely intentional", and your ISP had to use a different route due to overload or other dynamic metrics on the "faster" route we saw earlier that they normally use.

But if once your ping is "faster" again, you take a new traceroute and see that it's back to using telia.net again, you can at least call and ask your ISP if there is anything they know about why that is happening & if they can prevent using the slower cogentco.com route or not.

It's usually a hard conversation to have productively with an ISP, because you're talking to a bunch of front line guys who don't really know or care about the implications. Only after getting back to one of their network engineers is there a chance of any meaningful answers, let alone any meaningful action. There is a decent chance that even after talking to them, nothing changes.

But the traceroute at least confirms that it's nothing "at your end." Meaning that when your ping increased, there was no difference in the hops from your computer out to t-com.hr. The difference in latency all happened after the packets got forwarded out of t-com.hr to the next level network. There is nothing you can directly do about that, other than change ISPs and see whether things are the same or different when using someone else.

-Trench

User avatar
Mali Mrav
Member
Posts: 296
Joined: Fri Jan 02, 2015 1:53 pm
Contact:
Croatia

Re: ping

Post by Mali Mrav » Thu Nov 03, 2016 6:08 pm

tnx trench i will call them tomorow to see what they can do about it
tnx for ur time
:D
Silent Assassin

User avatar
Mali Mrav
Member
Posts: 296
Joined: Fri Jan 02, 2015 1:53 pm
Contact:
Croatia

Re: ping

Post by Mali Mrav » Fri Nov 04, 2016 5:59 pm

minute ago

Tracing route to 8.12.64.130 over a maximum of 30 hops

1 1 ms 2 ms 1 ms 192.168.1.1 [192.168.1.1]
2 * * * Request timed out.
3 26 ms 17 ms 17 ms 172.29.33.93 [172.29.33.93]
4 29 ms 22 ms 21 ms mzg-tr-10-mst-po-10-2.ip.t-com.hr [195.29.241.24
9]
5 22 ms 23 ms 28 ms gtr11-mzg-tr-10.ip.t-com.hr [195.29.110.146]
6 38 ms 37 ms 37 ms 87.128.238.117
7 42 ms 43 ms 39 ms 217.239.44.142
8 39 ms 38 ms 45 ms 80.157.204.66
9 159 ms 161 ms 158 ms xe-1-1-0.dal20.ip4.gtt.net [141.136.111.5]
10 165 ms 158 ms 164 ms ip4.gtt.net [173.205.43.82]
11 165 ms 163 ms 168 ms 8.12.64.130
Silent Assassin

User avatar
HairyRussianDude
Member
Posts: 76
Joined: Tue Sep 06, 2016 9:58 am
Canada

Re: ping

Post by HairyRussianDude » Sun Jan 15, 2017 3:40 pm

What is all this?
I've been getting the boot lately because of my ping bouncing all over the place. I can accept this on the european servers, but I'm surprised about getting booted trying to talk to a server in Texas. Maybe the Texas server is offended by all the gay jokes I make and my lack of worshiping baby Jesus?
How do I help my ping? I'm not overly educated on computers but not completely stupid with them. I know basic stuff like shut down any pc programs I dont need running while playing, keep off netflix and such. What else can I do to get a better connection?
Thanks!

User avatar
Trench
Admin
Admin
Posts: 1570
Joined: Tue May 22, 2012 3:19 am
Location: Dallas / Fort Worth
Contact:
United States of America

Re: ping

Post by Trench » Sun Jan 15, 2017 6:10 pm

Software and configurations on your local computer /can/ potentially be the source of an additional reason for your communication to have higher latency than necessary. (i.e. Higher ping response times.)

But even if your computer is 100% optimized, you still cannot communicate any faster or with any less latency than the sum total of all the networks that exist between your computer and the host you're ultimately trying to communicate with. (EA117's game server, in this case.)

And that's a lot of variables. Because that includes the network between your house and your ISP. (Internet service provider; e.g. Comcast, Verizon, Time Warner, etc.) It includes the networks that exist internally within your ISP. In includes the networks involved in your ISP handing off the traffic to a national or international backbone carrier (Level3, GTT, etc.). It includes the networks involved in one national or international backbone carrier handing off the traffic to another national or international backbone carrier. It includes the networks involved in the national carrier handing off the traffic to the ISP used by whomever operates the host you're ultimately trying to communicate with. It includes the networks that exist internally within this ISP. It includes the network between the ISP and the host you're ultimately trying to communicate with.

And finally, just like the latency could have been increased by software or configurations internally within your own computer, it can also be increased by the configurations or load on the host you're ultimately trying to communicate with (i.e. the EA117 server itself).


I don't have a real good analogy, but it's a bit like "What if you're hearing static on your phone call?" It might be the phone at your end, or it might be the phone at the other end. Or it might be the wiring, connections and switching equipment at any of the dozen or more voice network transitions the call has to make to get from point A to point B. You can't just say "My phone is brand new and works fine, so why is there static?" Your phone isn't the only thing involved, and every single transition between you and the person you're calling miles away could potentially be the source.


So these "traceroute 8.12.64.130" outputs you're seeing here are trying to establish a map of "when my ping is slow, where were the slowdowns at all these various network-to-network transitions ("hops") during that time period?" And then also, "when my ping returned to being faster later, at which hop(s), if any, did the latency time significantly change and become faster?"

e.g. If even the very first hop shows a significant change, this suggests the issue is inside your computer. If the latency showed by the traceroute stays the same all the way up to the very last hop and then gets higher/lower, then it's suggesting an issue at the destination host end. (i.e. The EA117 server end.)

More commonly, you'll see that one or more of the hops in the middle of the route changes latency. And/or you will see that an entirely different router (the IP address associated with each hop) was used. These are variables you cannot control, and were decisions made by the owning ISP and/or the load balancing / route costing mechanisms which decided a different (and potentially slower or longer) route needed to be taken.

So the traceroute will not necessarily give you information about something you can actually change. But it is a place to start in order to understand "when the latency changes, where is it changing." Since you might get "lucky" and find that the latency is with your own computer, or possibly with your ISP (which is at least someone you can have a conversation with, even if they ultimately won't do anything about it).

-Trench

User avatar
HairyRussianDude
Member
Posts: 76
Joined: Tue Sep 06, 2016 9:58 am
Canada

Re: ping

Post by HairyRussianDude » Sat Jan 21, 2017 3:00 pm

Thank you for the explanation Trench.
I ran the trace route, and ended up with a final number of 100ms. This is the number I see when things are good in game. I will keep trying this every so often and if I end up with mixed results I will consult you lol.

Post Reply