Community Forum

WEIRD Tracert

Xfinity Forum Archive
About the archive project

Xfinity Forum Archive...

This is an archived section of the community.

Content in this area has been identified as outdated or irrelevant.

This change was done in an effort to make the forum easier to use and to keep only the most helpful and recent content active.

Post your questions in the Xfinity Community

Frequent Visitor

Re: WEIRD Tracert

That would be great. 

Official Employee

Re: WEIRD Tracert

Either way my ping SHOULDNT be 170 so there is some kinda problem between me and the server.  :/   Others arent having this problem with the server.  Not sure what I can do if anything.  

 

Drabmatic, there could also be some T3 timeouts or signal issues causing the high ping values. I can take a look if you like. 

 

KenF

Frequent Visitor

Re: WEIRD Tracert

Either way my ping SHOULDNT be 170 so there is some kinda problem between me and the server.  :/   Others arent having this problem with the server.  Not sure what I can do if anything.  

Diamond Problem Solver

Re: WEIRD Tracert


@unixwizzard wrote:

 

What "sites" are you talking about? The info I posted is from the ARIN Whois-RWS..


Couldn't see that you got it straight from ARIN. 

Contributor

Re: WEIRD Tracert


@EG wrote:
Nah... IP ranges geolocation data at those sites can be meaningless.


What "sites" are you talking about? The info I posted is from the ARIN Whois-RWS..

 

ARIN is the registrar for Internet number assignments, they keep the master list of who is assigned what IP blocks, IP Geoloation has nothing to do with any of this.

 

 



@EG  .ru is .ru. The hop before is a edge router. That is a trans-atlantic link.


While you are correct, 64.20.32.5 is an edge router for AS19318 NJIIX-1.

 

However, it is not going TO Russia, it is a Russian server hosted in NJ: https://translate.google.com/translate?hl=en&sl=ru&u=http://www.reserver.ru/&prev=search  (under Dedicated server, click on the Server in the USA link)

 

 

Contributor

Re: WEIRD Tracert

 

Could be either an incorrect reverse DNS entry, or someone is just trying to be funny with the .ru domain host.

 

IP range 64.20.32.0 - 64.20.63.255 belongs to a company in New Jersey. As for the "high" ping, if the destination is a high traffic server or router, ICMP PING traffic is handled with a lower priority, so if the device is under load it would either respond slower to PING or just drop those packets outright.

 

screenshot-whois.arin.net-2018-03-11-19-48-35.png

Frequent Visitor

Re: WEIRD Tracert

Haha... its a game server, but any idea on a solution?

Expert

Re: WEIRD Tracert

Looks like the Russians are attempting to influence the pen market in America. Smiley Wink 

 

But yes, that's weird. 


I am not a Comcast employee, just a moderator. Pls observe Wheaton's Law.
Frequent Visitor

Re: WEIRD Tracert

I get that Robert, but the server location is in New York.   

Frequent Visitor

Re: WEIRD Tracert

That is the part that doesnt make sense.. because the server is in new york.  For whatever reason for that one single server its being directed like its in russia.  

Diamond Problem Solver

Re: WEIRD Tracert


@Drabmatic wrote:

Notice the .ru???   Russian ip????    My ping should be around 60 and its fluctiating being 160-190.  

 


20 165 ms 156 ms 161 ms reverse55-162.reserver.ru [64.20.55.162]

Trace complete.

 


The latency / RTT (Round Trip Time) does indeed jibe with the distance to Russia.

Silver Problem Solver

Re: WEIRD Tracert

That is the IP address for UniBall.


I am not a Comcast employee; I am just a customer, volunteering my time to help other customers here in the Forums.
Frequent Visitor

WEIRD Tracert

This is the only server/ip that i know is being effected and its not everyone on the server.  Only maybe 2 out of 50 people have this problem with the route.  I'm in SC and the server is in NY.       Notice the .ru???   Russian ip????    My ping should be around 60 and its fluctiating being 160-190.  

 

tracert uniballhq.com

Tracing route to uniballhq.com [64.20.55.162]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 8 ms 10 ms 8 ms 96.120.3.85
3 15 ms 8 ms 8 ms 68.86.131.37
4 13 ms 20 ms 13 ms 68.86.130.186
5 10 ms 9 ms 9 ms 96.108.171.166
6 10 ms 8 ms 9 ms 68.86.130.145
7 11 ms 11 ms 9 ms be-60-ar04.charleston.sc.chrlstn.comcast.net [68.86.130.149]
8 30 ms 45 ms 30 ms ae-30-ar02.westside.fl.jacksvil.comcast.net [69.139.222.213]
9 46 ms 47 ms 44 ms be-33489-cr02.56marietta.ga.ibone.comcast.net [68.86.95.49]
10 52 ms 43 ms 42 ms be-11440-pe01.56marietta.ga.ibone.comcast.net [68.86.85.246]
11 44 ms 43 ms 45 ms 50.242.148.190
12 44 ms 44 ms 44 ms be2848.ccr42.atl01.atlas.cogentco.com [154.54.6.117]
13 62 ms 62 ms 62 ms be2113.ccr42.dca01.atlas.cogentco.com [154.54.24.221]
14 62 ms 62 ms 68 ms be2807.ccr42.jfk02.atlas.cogentco.com [154.54.40.109]
15 64 ms 65 ms 61 ms be2897.rcr24.jfk01.atlas.cogentco.com [154.54.84.214]
16 65 ms 65 ms 65 ms te0-0-2-3.nr11.b017536-1.jfk01.atlas.cogentco.com [154.24.36.198]
17 90 ms 123 ms 82 ms 38.122.117.162
18 62 ms 62 ms 71 ms 64.20.32.147
19 65 ms 63 ms 70 ms edge-04-teb1.us.as19318.net [64.20.32.5]
20 165 ms 156 ms 161 ms reverse55-162.reserver.ru [64.20.55.162]

Trace complete.