Skip to Content

It is possible to validate routing of last mile, using the command “tracert” to identify the route that is used to connect to the Akamai server and with this understand if the network packages are traveling to other regions or countries which could be adding overhead and might require closer look of the network administrators or ISP. By example:

  • Use the tracert command to get IP for each of the hoops or routers involved in the routing

LastMile1.png

  • Once we have the IPs we can use  any of the IP geolocation services mentioned here to get the location and use information from the tracert to look into the latency

IP

Locations

Latency (ms)

  1. 192.168.1.1

Private

2

  1. 10.0.0.1

Private

6

Unknown

  1. 68.85.251.1

Houston

18

  1. 68.85.244.173

Houston

15

  1. 68.85.87.197

Houston

27

  1. 68.86.92.61

Dallas

36

  1. 68.86.89.250

Stemmons

23

  1. 50.242.150.138

Chicago

25

  1. 23.203.61.191

Cambridge

27

It is important to mention that different tools use different geo database and results could be different due to outdated database, it is recommended to get geo location information from different sources.

To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

  1. Henry Xu

    Hi Zareh,

    May I ask you a question? I used the command “tracert” to identify the route of an internal system. The result is weird, because many entries show ‘Request timed out’ and the character of ‘*’. I have made a screenshot, you can see it from the attached image.
    Do you know why I have this result? I was in office when did this trace with the corporate network. Is it due to the firewall?

    Best regards,
    Henry

    (0) 

Leave a Reply