Forum Discussion

Zino's avatar
Zino
New Contributor

Tracert

Anyone know why Cox takes me from San Diego to Pensacola to the Netherlands and then to San Jose, CA?

 9 hops - at hop 6 for the NA West we leave the united states and go to the Netherlands and then come back to the U.S at Hop 8

62.213.61.82
Date/Time: 2/16/2017 7:51:21 AM - 2/16/2017 8:01:21 AM
Hop Sent PL% Min Max Avg Host Name /
1 205 0 6.60 14.45 8.23 10.131.0.1 [10.131.0.1]
2 205 0 7.15 15.20 8.82 pwy1hbrc01-gex0321.sd.sd.cox.net [68.6.11.82]
3 205 0 7.50 21.82 9.32 elcnsysc02-get0106.sd.sd.cox.net [68.6.8.244]
4 205 0 38.08 58.68 40.19 dalsbprj02-ae2.0.rd.dl.cox.net [68.1.2.121]

5 205 0 39.00 57.18 41.72 ip70-167-150-167.at.at.cox.net [70.167.150.167]

IP address 70.167.150.167
70.167.150.167 or ip70-167-150-167.at.at.cox.net is an IPv4 address owned by Cox Communications Inc. and located in Pensacola, United States

6 205 0 95.01 110.76 99.35 ae03.edge01.sjo02.us.as5580.net [78.152.44.232]

IP address 78.152.44.232
78.152.44.232 or ae03.edge01.sjo02.us.as5580.net is an IPv4 address owned by Atratoip and located in Schiphol-Rijk, Netherlands

7 205 0 96.42 104.94 98.89 78.152.53.154 [78.152.53.154]

IP address 78.152.53.154
78.152.53.154 is an IPv4 address owned by Atratoip and located in Schiphol-Rijk, Netherlands



8 205 0 99.27 173.57 102.44 92.223.120.163 [92.223.120.163]

92.223.120.163 Server Details
IP address 92.223.120.163
92.223.120.163 is an IPv4 address owned by Gcl and located in San Jose (North San Jose), United States

9 205 0 98.00 105.55 100.73 162.213.61.82 [162.213.61.82]

IP address 162.213.61.82
162.213.61.82 or sv4-sl-b82.fe.core.pw is an IPv4 address owned by Wargaming America Inc. and located in San Francisco (Financial District), United States

3 Replies

Replies have been turned off for this discussion
  • ChrisL's avatar
    ChrisL
    Former Moderator
    @Zino

    It may be worth reaching out to the technical contact for the host you're trying to reach and see if they're experiencing any problems with their Internet connection. It's possible there's a problem with their provider causing a peering issue necessitating the unusual route. Note however that the location information obtained should not be considered accurate.

  • Zino's avatar
    Zino
    New Contributor

    i did reach out and the are not ...

    and what???

    "Note however that the location information obtained should not be considered accurate."

  • ChrisL's avatar
    ChrisL
    Former Moderator
    @Zino

    IP ownership info is easily to lookup however there is no IP to location association beyond that. For example, the hop you're thinking is Pensacola is actually Atlanta. I tried to reach this destination from my connection on the east coast and get taken along the same route. Problem is I don't know what the route should look like. Maybe they can try tracing back to you and see what they get.